=== iGama [n=xtreme@bl6-27-28.dsl.telepac.pt] has joined #launchpad === Ubugtu [n=bugbot@ubuntu/bot/ubugtu] has joined #launchpad === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad === marcin_ant [n=marcin@194.114.146.122] has joined #launchpad === mpt_ [n=mpt@203-118-186-15.bliink.ihug.co.nz] has joined #launchpad [01:46] anyone know how to change the importance of a bug? [01:53] sharms its not you that decide [01:53] ;) [01:54] iGama: so if I file a bug, and leave it as untriaged, I cannot go back later and change it? [01:54] Doesn't make much sense that I can confirm it fixed but not change priority [01:54] maybe i can be wrong [01:55] you're probably right [01:55] because I have searched high and low for it === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === rpedro_ [n=rpedro@87-196-103-207.net.novis.pt] has joined #launchpad [02:22] sharms: so priority is assigned by the folk that work on the bug [02:22] sharms: because they have the 'global view' === thierryn [n=thierry@modemcable251.69-131-66.mc.videotron.ca] has joined #launchpad [03:11] lifeless: have any luck getting the company voip stuff set up at your end? === stub [n=stub@ppp-58.8.3.15.revip2.asianet.co.th] has joined #launchpad [05:01] Goooooooooooooooooooood afternoon Launchpadders! [05:03] Yo [05:15] Feeling better, stub? [05:32] 40C fever broke last night taking most of the symptoms with it. Just left with a sore throat and aches after medication. [06:19] yay, another spurious PQM failure === mpt__ [n=mpt@203-173-177-223.bliink.ihug.co.nz] has joined #launchpad === jamesh [n=james@203-59-208-190.dyn.iinet.net.au] has joined #launchpad === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === Fujitsu [n=Fujitsu@c211-28-181-26.eburwd7.vic.optusnet.com.au] has joined #launchpad === mpt_ [n=mpt@203-173-177-223.bliink.ihug.co.nz] has joined #launchpad === mpt [n=mpt@203-173-177-223.bliink.ihug.co.nz] has joined #launchpad === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad [09:02] morning [09:03] yo === carlos [n=carlos@20.Red-83-33-194.dynamicIP.rima-tde.net] has joined #launchpad [09:04] morning [09:11] Hello. [09:15] spiv: Got a review for me yet? [09:16] stub: it's about half done by lines of diff, although I think probably the second half will be less interesting (the changes to the tests are less interesting than the infrastructure) [09:17] Yup. Mostly noise. [09:17] It isn't a complete overhaul, but I think it is a step or two in the right direction. === cprov [n=cprov@monga.dorianet.com.br] has joined #launchpad [09:18] BjornT_: ping [09:18] hi cprov [09:19] BjornT_: hi dude, about the testBrowse hint you gave me. [09:20] BjornT_: the 500 exception appeared, however the contents is empty ans screams [09:20] line 185, in contents [09:20] old_location = response.tell() [09:20] AttributeError: 'NoneType' object has no attribute 'tell' [09:22] morning [09:22] sivang: morning [09:24] cprov: oh, that's not good. i was quite sure that you could look at the error page, but maybe you can't. i'd say that's a bug, though. [09:25] BjornT_: can you check this soon for us ? I don't realy need to check the pages contents, the fact it is a 500 is enough [09:29] cprov: sure, i'll take a look at it today. although i'd think that the UFD part is the important one, so i'd rather check for the UFD exception rather than checking for a 500 page. [09:31] BjornT_: I can't get the UFD in the pagetest :( [09:31] cprov: what exeption do you get if you set browser.handleErrors = False? [09:32] BjornT_: ohh, indeed, it's UFD [09:34] BjornT_: back on the former topic, I cannot use this approach for POST vars, can I ? === Fujitsu [n=Fujitsu@c211-28-181-26.eburwd7.vic.optusnet.com.au] has joined #launchpad [09:36] cprov: well, it depends. for some you can, but for some you can't. [09:39] BjornT_: how do you mean ? can you give some example, or better can you check the bad-usage in soyuz/26... ? === mpt [n=mpt@203-173-177-223.bliink.ihug.co.nz] has joined #launchpad [09:47] cprov: for the http() calls in 26-queue-pages.txt it'd be hard to convert them to new-style tests. it would be possible to do it (without modifying testbrowser), but i don't think it's worth the effort. [09:51] BjornT_: uhm, so the limitant factor is that they use POST ? [09:53] cprov: actually, you might be able to do it. try passing the POST variables as a dict to browser.open(), like >>> browser.open('http://...', data={'QUEUE_ID': '1', 'Accept': 'Accept'}) [09:54] BjornT_: let me check === malcc [n=malcolm@host86-135-139-100.range86-135.btcentralplus.com] has joined #launchpad [10:01] BjornT_: see https://chinstrap.ubuntu.com/~dsilvers/paste/filenHwIoU.html [10:01] BjornT_: it failed [10:04] cprov, elmo: two Friday uploads: fontconfig (unsigned, but didn't get any mail), libxt-java (signed, I do have an upload file, but it's not in the archive). any hints? [10:05] doko: will check, do you remember the time you uploaded them ? [10:07] cprov: libxt-java: 15:30:29 UTC -2, just did overwrite the fontconfig .upload file [10:07] cprov: ok, so the data should be a string. passing in data='QUEUE_ID=1&Accept=Accept' could work then, but you might have to set the Content-Type header as well, and i don't see a way of doing that. (i'm also not sure if it will be a GET or POST request) === lifeless_ [n=robertc@dsl-28.7.240.220.rns01-kent-syd.dsl.comindico.com.au] has joined #launchpad [10:09] BjornT_: let's give up for a while, bug #52487 will remember us later. [10:09] Malone bug 52487 in soyuz "Current pagetest environment doesn't support hand-made URLs" [Medium,Confirmed] http://launchpad.net/bugs/52487 [10:09] cprov: sounds good === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad === glatzor [n=sebi@ppp-82-135-83-247.dynamic.mnet-online.de] has joined #launchpad [10:16] doko: libxt-java_0.20050823-2ubuntu1_source.changes -> 'edgy.' (the ending DOT !!) REJECTED [10:17] doko: the fontconfig was "nearby" the last ? [10:18] jamesh: ping [10:18] ddaa: pong [10:18] are you aware that the branch scanner is currently broken? [10:19] ddaa: yes. I have a branch waiting for review to fix it [10:19] jamesh, spiv, stub [10:19] conf call time! [10:19] ddaa: there were some differences between the test environment and production so an error slipped by [10:19] ddaa: my branch fixes those env differences and the problem (plus makes some other cleanups) [10:19] as soon as stub has explained to me how to drive it [10:19] jamesh: fantastic, thank you [10:20] cprov: "nearby": don't know exactly, the changes file is from 10:00 -2. [10:20] ddaa: I moved the bzrsync.py code to lib/canonical/launchpad/scripts as part of the cleanups [10:20] cprov: I didn't get the rejected message ... [10:20] ddaa: and it now gets run by the main zope test runner [10:21] jamesh: great! I had already done some preparatory work for that [10:21] I'm very happy to hear that you completed the move :) [10:21] doko: nevermind .. let's check at 10 [10:22] cprov: yes, fontconfig was unsigned, that should be the reason [10:25] doko: alright, upload them again now, we can check for anything weird, but yes, unsigned changes do not generate any email. [10:26] We appear to have lost James and Steve. [10:26] Straight after a machine gun sound [10:27] i can hear all three of you [10:27] but you cannot hear me [10:27] maybe it is my NAT flavour [10:27] i had this with ekiga before on stun === SteveA checks settings [10:30] I'm here [10:30] You can't here me? [10:30] stub: no. [10:30] stub: turn off STUN and NAT Traversal in the prefs [10:32] doko: fontconfig and libxt-java were accepted, did you get emails ? [10:33] I feel all alone [10:34] everything's gone choppy [10:34] and you can't hear me [10:34] ... [10:35] Declare SIP a failure for the time being? [10:35] yeah [10:36] I prefer IRC meetings anyway :) === Keybuk [n=scott@quest.netsplit.com] has joined #launchpad === doko [n=doko@dslb-088-073-108-073.pools.arcor-ip.net] has joined #launchpad === fabbione [i=fabbione@gordian.fabbione.net] has joined #launchpad [11:09] jamesh: no, wanted to chat with you about local asterisks - I get -crap- audio via either a local asterisk or siproxd to the loopback service @ canonical, and with a local asterisk to the local asterisk [11:10] ddaa: what time is our bzr meeting ? [11:10] mh [11:10] as in, hours from now [11:10] thanks for reminding me [11:10] I think last time we discussed times, it was UTC 1200, that is 170 mins from now [11:11] no way [11:11] 1000 perhaps [11:11] it was before the review meeting [11:11] hu [11:11] and the review meeting is 1100 [11:11] right [11:11] so, in 50 minutes, cool [11:11] as you can see, my meeting muscle is a bit rusty [11:13] gah... a day of meetings again! [11:13] at least ddaa and lifeless know how to keep them brief :-) [11:13] SteveA: lifeless: if you guys do not mind, I'm happy to skip it [11:13] ddaa: after EP, it's important to get things back on track [11:13] I have a very short week, and I'd like to get some actual productive work out of it. [11:14] i think 45 mins for a meeting will make little difference [11:14] even including 15 mins to stick a summary of action items and decisions on a mailing list === ddaa supresses argument [11:15] okay, I'll start preparing the agenda === lifeless agrees [11:49] https://launchpad.net/products/launchpad/+bug/50743 [11:49] Malone bug 50743 in launchpad "sqlobject SelectResults.__contains__ generates bad SQL for some conditions" [Untriaged,Fix released] [11:49] https://launchpad.net/products/launchpad/+bug/39814 [11:49] Malone bug 39814 in launchpad "Misleading login hint" [Medium,Fix released] === mpt_ [n=mpt@203-173-177-223.bliink.ihug.co.nz] has joined #launchpad [12:08] Hi carlos. Rosetta seems to completely ignore me. I cannot upload any po files nor request them. [12:08] glatzor: hi [12:08] URL? [12:09] https://launchpad.net/distros/ubuntu/dapper/+source/nautilus/+pots/nautilus/de/+export [12:10] or https://launchpad.net/distros/ubuntu/dapper/+source/kdebluetooth/+pots/kbtobexclient/de/+upload [12:11] The uploaded translations do not appear in Rosetta and I don't get any confirmation e-mail. [12:11] glatzor: but you got the confirmation email, right? [12:12] When I request a po file, Rosetta says that I will receive it by email, but this doesn't happen [12:12] carlos: No not even the confirmation e-mail. [12:12] no, I'm talking about the confirmation after the upload [12:12] I checked my spam folders twice [12:12] what you get in our Web UI [12:13] All looks fine in the web interface [12:13] ok [12:20] stub: hi, could you check if Rosetta's scripts are enable on production ? === mholthaus [n=mholthau@johnny33.dersbach.ch] has joined #launchpad [12:31] oops. I remember disabling them for some maintenance. [12:31] carlos: Fixed. [12:32] Who wants to review or approve https://launchpad.net/products/launchpad/+spec/stop-spurious-test-failures ? [12:32] stub: ok, thanks [12:32] glatzor: you should get the email soon, seems like we had the scripts to do the imports disabled [12:32] thanks a lot, carlos [12:35] stub: "eternal libraries." ? [12:36] spelling optional [12:36] stub: looks good, but the spec should state what the 2-way deps are === WaterSevenUb [n=WaterSev@195-23-238-171.nr.ip.pt] has joined #launchpad === carlos [n=carlos@114.Red-88-15-196.dynamicIP.rima-tde.net] has joined #launchpad [12:43] SteveA: I don't know what they are. That is why the spec explicitly states the initial rule will be the current minus the two that are failing. [12:44] which two are failing? [12:44] cscvs and bzr [12:44] cscvs and bzr currently both have issues due to the time issues. [12:45] I think it wouldn't be hard to figure out the dependencies though. [12:45] okay. i'm happy with it. i'd like lifeless to say whether he is happy about it. [12:46] Lots of them are obvious: sqlobject, twisted, zope are all clearly not dependent on launchpad. [12:48] I'd like a wiki page that describes all the branches and what the depend on [12:48] then I'd like a proposed consistent way of managing the tests-to-run-for-each-branch [12:48] i.e. 'sqlobject: run all', 'launchpad: run X,Y,Z' etc [12:49] and at that point I'll say whether I'm happy, or if not, what it will take ot make me happy [12:50] I'd like a solution we can turn on now. [12:50] last time we did this we shot ourselves in the foot. [12:50] That works for us and meets our goals. [12:50] I'm in anothe rmeeting right now. [12:51] but what I'm suggesting is really no more than the bare minimum: we have to analyse our branches and decide [12:51] Why? [12:51] It doesn't address our immediate concerns any better [12:52] lifeless: we're concerned only about merges into the launchpad branch right now [12:53] the rest can proceed as they currently do [12:53] If you define our immmediate concerns as "don't run cscvs or bzr tests on launchpad merges", then stub's right ;) [12:53] SteveA: in which case, someone needs to analyze all the branches from the p.o.v. of 'can break by lp changing' [12:54] no [12:54] that's overdoing things up front [12:54] we first need a mechanism for running only the tests we want [12:54] then we can make the choice incrementally as we go along [12:54] starting with "run it all" [12:54] then analysing each one in turn as we need to [12:54] the two we want to analyze first are bzr and cscvs [12:55] We know cscvs and bzr are one way dependancies, so the spec explicitly states they are the only things that get turned off initially. === stub adds that to assumptions [12:55] there really is no need to have either a perfect technological solution or to analyze all the cases before making this initial improvement [12:56] stub: Lots of them are obvious: sqlobject, twisted, zope are all clearly not dependent on launchpad. [12:56] is there a spec now ? [12:56] link me up [12:56] SteveA: the second point I made was to have a mechanism for doing it. [12:56] stub: So, changing check_merge isn't trivial -- the extra tests are run from a seperate makefile. [12:56] (17:32:11) stub: Who wants to review or approve https://launchpad.net/products/launchpad/+spec/stop-spurious-test-failures ? [12:56] stub has proposed a mechanism [12:57] stub: take a look at sourcecode/Makefile [12:57] spiv: Sure - you need to add a new rule to the sourcecode/Makefile too. [12:57] Ok. I didn't see any mention of that in the spec. [12:57] I would have assumed it was obvious to anyone attempting to implement it [12:58] Added Makefiles for dummies to code changes [12:59] Ta :) [12:59] review meeting in 1 minute === spiv takes a breath between meetings [12:59] stub: +1 [12:59] that looks fine to me, tell me when the new target is present, I'll update pqm.conf [12:59] or you can [01:00] Ok. I mentioned the idea to kiko so he might have already started. I'll point him at the spec and get him to assign an implementer [01:00] may I suggest spiv [01:00] as he has done Makefile tweaking there already [01:01] Fine by me. I suck at Makefiles ;) [01:01] stub: So do I, just no-one has noticed yet ;) [01:02] But sure, I can do this, it looks straightforward. [01:02] who is here for the review meeting ? [01:02] * agena [01:02] * next meeting [01:02] me [01:02] * queue status [01:02] me [01:03] all these strange people whose names start with "* " [01:03] i am here [01:03] me [01:03] next meeting - 17th Jul, same time & place ? [01:04] i may or may not be here, depending what's going on at the management meetings [01:04] sure [01:04] SteveA: please add an apology as appropriate when you know [01:04] ok, queue status [01:04] spiv: whats up with 9 days ? [01:05] lifeless: it's big. [01:05] I'm nearly done. [01:05] ok [01:05] I see you have another big on [01:05] *one* [01:05] I'll be interested to see the time it takes [01:05] I'm wondering if its non-linear to review big branches [01:05] I think I may punt salgado/launchpad/real-karma-context back to rejected, I'll take a look and decide very soon. [01:06] I'll make sure to include the review time, I haven't added it up yet (it's been done over several sessions). [01:06] it may be helpful for the author of the code to summarize their changes at a higher level [01:06] sort of do a self-review first [01:06] this could help a reviewer get the idea of what's going on quicker [01:06] by "back to rejected", I mean rejected from my queue, rather than rejecting the code... [01:07] that was definitely useful when I was reviewing the mega-soyuz branch back in London [01:07] particularly if there is a higher-level pattern of refactoring that is implemented in a bunch of changes === mholthaus [n=mholthau@johnny33.dersbach.ch] has left #launchpad ["Konversation] [01:07] ok [01:07] SteveA: You mean more than the one or two sentences people add to PendingReviews? [01:07] other than that its in good shape [01:07] Kinnison and cprov were able to give an overview and suggest an order to review the parts of the patch in [01:07] spiv: not really [01:08] I find the descriptions on PendingReviews help my understanding quite a lot. [01:08] spiv: I mean for the author to take a diff and reply to it, like in an email, like reviewers do [01:08] with > + whatever [01:08] at the start of lines [01:08] btw, lifeless, I find reviews easier to read when they have email-style indenting "> + whatever" rather than just "+ whatever" [01:08] I think all the reviewers use the former style except you [01:09] spiv: I'm moving malc's branch to jamesh if thats ok, as its at 5 days [01:09] SteveA: interesting. I find the > gets in the way of reading the code. [01:09] as I'm using to looking at normal diffs on my screen. [01:09] I find its absence gets in the way of reading the comments [01:09] jamesh: Yeah, I often wish the diff was in a slightly better order -- e.g. doctests for a feature before the code implementing the feature. Although the "added files first" heuristic bzr has is a good approximation of that. [01:09] lifeless: ok === BjornT_ agrees with SteveA [01:09] I agree with SteveA. [01:09] also, its presence reflects the review as a conversation that starts with the code diff [01:10] and is followed by a reply / comments [01:10] in which case, jamesh - can you make pending-reviews spit it out in that format please ? [01:10] and is followed by more replies to the comments === danilos [n=danilo@147.91.15.54] has joined #launchpad [01:10] i wouldn't like pending-reviews to automatically indent it, though [01:10] I actually asked for the following a while ago... [01:10] lifeless: oh no, you'll break my "copy, paste, highlight, quote" muscle memory! [01:10] BjornT_: why not ? [01:10] - a link on the pending reviews page that serves up the diff [01:10] - indented appropriately [01:11] spiv: I think the added files, removed files, changed files ordering is just an artefact of the way it generates a diff [01:11] BjornT_: actually, I've given pagetest-tweaks to you to review. [01:11] - with a custom mime-type x-code-to-review [01:11] jamesh: it might be an accident, but it's a good one [01:11] this would allow me to register a helper app to handle the review with a single click [01:11] hi SteveA [01:11] SteveA: I'm +1 on the rest, but not the mimetype. I'd prefer it stays text/something [01:11] when i review i find it easier to read the real diff. but in a review email, it's easier to read if the diff is indented, since it makes it easy to see what the comments are. [01:11] I'd prefer to have the ordering semantically meaningful like: changed interfaces, changed tests, changed code [01:11] SteveA: if you mean text/x-code-to-review, then thats fine by me [01:12] lifeless: yes [01:12] lifeless: I think I agree with Bjorn -- for reading a straight diff, indentation/">"-quoting is pointless. "> " helps if you're reading comments on a diff. [01:12] I want to keep the links to diffs as plain diffs, as they are now [01:12] hi danilos [01:13] spiv: I do the review in an editor window, so I'm reading the plain diff - thats how I find it easiest to review. [01:13] spiv: which is why my comment is about reading the code. [01:13] moving on, as there is a clear route forward [01:14] Actions from the last meeting: * stevea to add note about operator.attrgetter being better than trivial lambdas to lp coding guidelines [01:14] SteveA: did you do that ? [01:14] yes [01:14] lifeless: Ah, I keep it in the browser, so I can refer back to code I've elided from the review, and possibly re-include it if I realise due to later code I have a comment on iot. [01:14] i'll also note that guido said at EP [01:14] and at PyCon [01:14] that lambda is staying for python 3 [01:14] spiv: I find that awefully cumbersome. Still, I'm going to change to be like the rest of the boys [01:14] spiv: I do similar. [01:15] browser + editor [01:15] lifeless: it's not ideal, but it's the best system I've found for me. [01:15] works well with two monitors :) [01:16] carlos: ping [01:16] lifeless: you ought to be able to just post-process your review === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad [01:16] lifeless: to use sed or awk to insert the quoting [01:16] for me it works quite well to use only an editor, >-indenting the part that i comment on in a first run. then the second run i delete what's not needed. [01:16] SteveA: sure, its just cumbersome - its an extra tool. [01:17] rather than brower + email, its browser + vim + email. [01:17] lifeless: vim is my email ;) [01:17] set up procmail to filter it ;-) [01:17] shoo [01:17] meeting over in 3 [01:17] ah [01:17] i have a point [01:17] meeting countup on hold [01:17] lifeless: there's a spec somewhere about better messages from pqm [01:18] and tied into that, the bzr httpd running on the place we keep our branches [01:18] so that we can do things like have links to see what's in a [trivial] patch [01:18] what do we need to do to make it happen? [01:18] (1. find the spec) [01:19] https://launchpad.net/products/launchpad/+spec/pqm-commit-messages [01:19] find the spec, let me review it by the next meeting [01:19] then assign it to a team or person [01:19] it's rated "low" by mark/kiko [01:20] that one I have read, so, I will review in detail for next meeting. [01:20] but I think it is important to make incremental improvements in that direction [01:20] particularly as we're getting non-trivial trivials landing [01:20] one thing we can do right now is setup bzr webserve [01:20] that will allow click-through analyse of the commits with no code changes [01:20] lifeless: that's a great idea [01:20] so is a cheap win [01:21] great. please. [01:21] ok [01:21] also also, when do we move to the new box? [01:21] stub: ^^^^ ? [01:21] I don't know who is involved [01:21] anything else for this meeting ? [01:22] but I heard the new dev box to replace launchpad team use of chinstrap is ready [01:22] 2 [01:23] 1 [01:23] lifeless: I believe you have something to do with the new box, and moving all old branches to knit format on it. [01:23] maybe tell me what's happening after this meeting [01:23] nothing to do with getting onto the new box [01:24] probably I need to be involved, but am not at the moment [01:24] ok [01:26] SteveA: as part of the review fixes for one of my branches, I needed to expose the SQLObject syncUpdate() operation. I did it by adding a new canonical.launchpad.interfaces.ISQLObjectSyncable interface [01:26] SteveA: spiv was okay with it but wanted another reviewer's opinion on the naming. Does it sound okay to you? [01:27] works for me [01:27] I think any sqlobject should by syncable by the application code. [01:28] But also, this API isn't really about the content objects. [01:28] So, I have two things to suggest: [01:28] (The original issue is that foo.syncUpdate() often more appropriate than flush_database_updates(), but security proxies tend to disallow that at the moment) [01:29] hmm [01:29] 1. Check to see if an object is an instance of the base sqlobject class we use, in the security policy, and allow that method for all of them. [01:29] or [01:29] adding the method to canonical.database.interfaces.ISQLBase would probably be cleaner [01:29] 2. have a function that you apply to an instance, removing its security proxy and calling that method [01:29] (since sync() and syncUpdate() can't be destructive) [01:29] the function is used for just that [01:30] SteveA: If you mean a new box for bzr hosting Launchpad code, I have not been involved. [01:30] because of the way security works today, adding this to an interface isn't really involved in making that call available [01:31] so, it would be more just for documentation [01:31] stub: okay. so, who is involved, I wonder... [01:31] replacement chinstrap for us AFAIK [01:31] lifeless will have to be involved for ensuring our place for branches is correct [01:31] spiv on running a smartserver on there, eventually [01:32] someone for setting up the bzr web server on there [01:32] jamesh to set up pending reviews etc. [01:32] moving error reports rsyncing over... [01:32] So will smartserver and pqm coexist, or will smartserver supersede the PQM functionality we use? [01:32] coexist [01:32] they're different [01:32] SteveA: how would (1) be done? [01:33] jamesh: there's a module inside webapp... authorization.py I think [01:33] inside there, the security policy code needs a check added to say [01:33] if name == 'syncUpdate' and isinstance(obj, SQLBaseWhatever): [01:33] return True [01:34] this code, being some of the oldest in Launchpad, probably isn't properly tested [01:34] at least, not explicitly [01:34] (I missed the earlier discussion, but I would have thought we could just make SQLBase implement an interface defining that method and make it available to logged in users.) [01:35] not really [01:35] SteveA: thanks. I'll look at doing that then. [01:35] because of how the security system works with interfaces [01:35] that's roughly how things will work in the future [01:36] there's some zope stuff to change first, and that's a new-webapp thing [01:36] stub: would security declarations for SQLBase apply to the subclasses though? === SteveA thinks about lunch [01:36] stub: (for reference, SQLBase does implement an ISQLBase class) [01:37] jamesh: the adaption wouldn't work out right [01:37] SteveA: that's what I thought. === jd_ [n=jd@wikipedia/Meanos] has joined #launchpad [01:37] the interface would apply on subclasses, but most likely the right adapter would not be chosen [01:37] carlos: thanks. I just received my emails from Rosetta. [01:37] glatzor: cool [01:38] so, stick it in the global security policy, and we'll refactor later on === SteveA --> lunch === spiv --> dinner === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad === mdke [n=matt@ubuntu/member/mdke] has joined #launchpad === glatzor [n=sebi@ppp-82-135-83-247.dynamic.mnet-online.de] has joined #launchpad [02:02] My fever is returning so I'm off for the evening. [02:02] (no - not disco fever) === matsubara [n=matsubar@200-171-140-32.dsl.telesp.net.br] has joined #launchpad === salgado [n=salgado@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [02:11] Are we supposed to arrive the Saturday or the Sunday before our sprint? === danilos [n=danilo@147.91.15.54] has joined #launchpad [02:21] danilos: hi [02:21] hi carlos === glatzor [n=sebi@ppp-82-135-83-247.dynamic.mnet-online.de] has joined #launchpad === immortalxak [n=immortal@195.252.127.130] has joined #launchpad === jd_ is now known as jd_miam === lincao [n=lincoln@200-171-140-32.dsl.telesp.net.br] has joined #launchpad === bradb_ [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad === niemeyer [n=niemeyer@200-193-168-145.ctame7043.dsl.brasiltelecom.net.br] has joined #launchpad === flacoste [n=francis@modemcable207.210-200-24.mc.videotron.ca] has joined #launchpad === niemeyer [n=niemeyer@200-193-168-145.ctame7043.dsl.brasiltelecom.net.br] has joined #launchpad [03:21] SteveA, around? === jinty [n=jinty@213-156-52-99.fastres.net] has joined #launchpad === jd_miam is now known as jd_ [03:42] or BjornT? === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [03:42] hi salgado [03:44] hi BjornT. can you help me with some vhosting issues? [03:44] sure [03:48] in shipit, all browser:url declarations are meant to work only when using a setup similar to the production one. that is, it assumes the root url is /shipit-ubuntu [03:49] this means that, if you access shipit through launchpad.dev/shipit-ubuntu/something, you'll get some broken links pointing to launchpad.dev/something-else [03:50] this is a problem when I use getLink('foo').click() on new pagetests [03:51] I was wondering if it'd be possible to configure a new rootsite that would allow me to test this properly, without breaking it in production === jd_ is now known as cadavre === cadavre is now known as jd_ [03:54] salgado: i think it's better for SteveA to answer that question, i'm not sure how shipit is setup in production. [03:56] we use some apache RewriteRules there [03:58] morning [04:04] morning kiko! [04:04] how are you francis? [04:05] g'morning kiko :) [04:05] fine for a monday morning :-) [04:05] danilos! [04:06] good to see you around [04:06]