/srv/irclogs.ubuntu.com/2011/11/18/#launchpad-dev.txt

wallyworld_poolie: as you say in your comment, your change will make tests less random. isn't that a bad thing? don't we want tests to pass with unpredictable input?00:00
pooliethis is a bit philosophical00:02
StevenKiamfuzz: O hai!00:02
iamfuzzStevenK, o/00:02
pooliei think you should test stuff intentionally, not count on randomness00:02
poolietests that happen to run before this one will get one type of input and tests that happen to run after it will get a different prng00:02
iamfuzzStevenK, thanks for the help btw.  Trying to get this up to evaluate as the tool for our build farm here00:02
poolieit's hard to see how that's helpful00:02
iamfuzzStevenK, easy peasy getting it running but can't import keys.  It looks like I may have screwed something up irt the bazaar rewrite rule or something perhaps00:03
* wgrant is scared now00:03
iamfuzzStevenK, when attempting to import a key, it looks like it tries to hit this URL based on the logs:  https://bazaar.launchpad.dev/pks/lookup?search=0xD69FC46438D3A33619E5577D39BE3335F26A3797&op=get00:04
iamfuzzwhich if I hit directly, gives more the "Lost something?" 404 page with broken images00:04
wgrantiamfuzz: Hmm, it should be keyserver.launchpad.dev, not bazaar.launchpad.dev.00:04
wgrantHave you changed the configs at all?00:04
iamfuzzhowever, hitting bazaar.launchpad.dev directly does properly redirect to launchpad.dev00:05
wallyworld_poolie: isn't the whole point of using a rng to provide different input each time?00:05
iamfuzzwgrant, the apache config, yes00:06
wgrantiamfuzz: The Apache config shouldn't matter here.00:06
StevenKwallyworld_: Are you still reviewing poolie's branch?00:06
wgrantiamfuzz: The test keyserver doesn't go through apache00:06
wgrantit's keyserver.launchpad.net:1137100:06
wgrants/net/dev/00:06
pooliewallyworld_, so, generally, my experience is that using a rng in tests is a bad idea00:07
poolieif there are some random values that catch a bug, which is possible00:07
pooliethere are two problems00:07
poolieone is, the particular values are likely to come up only very rarely, so the bug may be latent for a long time00:07
pooliesecondly, it will be hard to reproduce it, so perhaps hard to understand why it's failing00:08
poolieoh, and also, it may fail at inconvenient times00:08
pooliefor example on buildbot but not ec2 etc00:08
iamfuzzwgrant, https://keyserver.launchpad.dev:11371/pks/lookup?search=0xD69FC46438D3A33619E5577D39BE3335F26A3797&op=get  just hangs on me00:08
iamfuzzyep, timed out00:08
wgrantiamfuzz: http, not https00:08
iamfuzzah there we go00:08
iamfuzzmuch better00:09
iamfuzzError handling request: No keys found00:09
wallyworld_StevenK: yes00:09
pooliewallyworld_, so this particular test is testing code that itself uses the rng, so i think it has a valid reason to touch it00:09
pooliebut it should isoltae itself00:09
iamfuzzwgrant, what is it attempting to parse for its pgp key info to not be finding any keys? or is there a utilities/ script I need to run?00:09
wgrantiamfuzz: gpg --keyserver keyserver.launchpad.dev --send-keys SOMEKEYID00:10
wallyworld_poolie: that all makes sense. thanks for explaining00:10
wgrantiamfuzz: The dev keyserver doesn't know about any keys by default.00:10
iamfuzzwgrant, ah doh, sorry bout that.  I had assumed it would sync with the ubuntu keyserver00:11
wgrantiamfuzz: No, that would take a looooooooooong time :)00:11
iamfuzzpoint taken :-)00:11
wgrantYou can point your local LP at the Ubuntu keyserver, but that gets problematic when you want signing keys for your PPAs, as it will upload them to the real keyserver where they can never be deleted.00:12
iamfuzzwgrant, worked like a charm, many thanks.  Now I just have to get email working on here and should be golden00:12
wgrantiamfuzz: Email from the webapp is generally redirected to root@localhost.00:13
iamfuzzeven better00:13
wgrantOr you can grab the token with "SELECT * FROM logintoken"00:13
wgrantThen https://launchpad.dev/token/SOMETOKENVALUE00:13
wgrantIf you are lazy and don't want to decrypt the email.00:14
iamfuzzwgrant, I'm not *that* lazy ;-)00:14
iamfuzzyou guys have made it far easier than I expected00:14
wallyworld_StevenK: r=me. you've put the egg in download-cache i'm sure? :-)00:14
* iamfuzz crosses fingers soyuz works out as well :-)00:14
StevenKwallyworld_: I have, and there are two branches00:15
wallyworld_StevenK: already reviewed the other one :-)00:15
wgrantiamfuzz: I spent the two days after the code was released working out and documenting how to make Soyuz work. https://dev.launchpad.net/Soyuz/HowToUseSoyuzLocally should be adequate.00:15
wgrantAlthough I guess you've already seen that, if you have the keyserver running.00:16
pooliewallyworld_,  should i put that on the mp maybe00:16
wallyworld_poolie: i think that would be great00:18
wallyworld_poolie: also so that the original branch author etc can see why the change was made00:18
pooliewallyworld_,  thanks for asking00:20
wallyworld_poolie: np. i was being a bit cautious just to make sure i didn't approve something that would fuck things up because i didn't appreciate the reason for the change00:21
pooliesure00:24
pooliei would like to make people appreciate randomness in tests is not a feature00:24
mwhudsonpoolie: of course, you don't always get to choose -- i remember a test failure that turned out to be assuming the email packages way of generating message ids was collision resistant00:25
wallyworld_poolie: i don't think i've ever used a rng in any tests but made the mistake here of assuming that because it was used, a requirement was to have as much randomness as possible00:25
mwhudsonbut sadly it just uses second level timestamp + randint(100000)00:26
StevenKwallyworld_: You do, by side effect00:26
wallyworld_i guess if are a writing a comms protocol test or something like that you need one00:26
* StevenK sighs at our Makefile00:27
* wallyworld_ off to get some medicine from the doctor. back soon hopefully00:27
* StevenK fixes rm to be $(RM)00:27
jelmerStevenK: is there a particular reason for that?00:32
StevenKjelmer: For which, sorry?00:32
jelmerStevenK: $(RM), it surprised me too00:32
jelmerthe last project I encountered that substituted RM did it because of broken rm implementations00:33
StevenKjelmer: It's cross-platform, which isn't really a concern for us, but I'm a pedant like that.00:33
jelmerah, ok00:33
jelmerlaunchpad on windows ? :-)00:33
StevenKBwahaha00:33
StevenKWe need POSIX00:33
StevenKLaunchpad on OS X could be possible, which is a scary prospect00:34
mwhudsoni've contemplated it, but funnily enough always found better things to do00:35
wgrantThe most difficult bit would be porting python-apt, I expect00:35
wgrantThe most adventurous thing I've done is running it on kfreebsd.00:36
rick_h_python-macports00:36
rick_h_I can see it now00:36
StevenKmwhudson: Haha00:36
mwhudsoni think jamesh said he did it once in the early days, or thought about it?00:37
mwhudsonanyway, talking of better things to do --> lunch00:37
pooliewallyworld_, https://bugs.launchpad.net/launchpad/+bug/1734 is arguably fixed by hiding bug comments00:51
_mup_Bug #1734: Bug discussion is append-only and cannot be gardened <feature> <lp-bugs> <Launchpad itself:Triaged> < https://launchpad.net/bugs/1734 >00:51
pooliepht01:18
pooliewgrant, so what's next?01:19
pooliei guess i will get rid of the runtime master-client dependency01:19
wgrantpoolie: RIght, just remove that one import.01:20
wgrantpoolie: Replace it with the string, like the rest of the file uses already.01:21
wgrantThen check that the appserver runs without python-lpbuildd installed, and reland.01:21
pooliek on it01:21
wgrantThanks.01:23
wallyworld_poolie: that does look like it could be regarded as a dup of 885672 but when the branch lands, it's going to be quite limited to who we expose it to (at least initially)01:33
pooliethere are bunch of not-quite dupes01:33
poolieit may be worth tearing them apart01:33
wgrantI think it's pretty different.01:34
wgrantThis isn't for gardening.01:34
wgrantThis is for spam and emergencies.01:34
wgrantGardening is very different.01:34
wgrantAh, jelmer is still awake!01:35
wallyworld_wgrant: sure, but the solution is the same even though the problem descriptions are different01:36
wgrantwallyworld_: Is it?01:36
wallyworld_wgrant: or StevenK: could you +1 this. it looks ok but i'm not confident that i understand the implications enough https://code.launchpad.net/~jelmer/launchpad-buildd/dpkg-buildpackage-sa/+merge/8262301:36
wgrantwallyworld_: I'm doing that right now.01:36
wallyworld_ok thanks01:36
wallyworld_wgrant: allowing the user to hide their own comments is a form or gardening i think01:37
wgrantErmmmmm01:37
wgrantpoolie: Why does ~launchpad-dev own lp:launchpad-buildd.01:37
wgrant?01:37
* wgrant fixes.01:37
nigelbwgrant: wow.01:38
nigelbI wwas about to ask that.01:38
nigelb(because of the MP requests coming on the m/l)01:38
pooliewgrant, oh was that the list?01:40
pooliethe short answer is that trusted pickers aren't used everywhere01:40
wgrantIt's the list, yes.01:40
wgrantWhich is an open team.01:40
wgranthttps://dev.launchpad.net/CreatingNewProjects01:40
pooliesorry01:40
wgrantWe should really abolish open teams.01:41
dobeyemancipation is key01:41
pooliei do think teams need some kind of superclass split01:41
pooliePersonGroup, Team(PersonGroup), MailingList(PersonGroup)01:42
pooliesomething ilke that01:42
pooliethey are too overused01:42
lifelessmmm01:42
lifelessmaybe01:42
poolieand being able to use the same team for many different purposes is not necessarily beneficial01:42
pooliemaybe not01:42
poolieanyhow01:43
poolieit's kind of stupid that it's possible to make this mistake01:43
poolieeven if i am stupid for making it01:44
lifelesswell, the instructions could do with automation01:44
wgrantSadly some people do like having open branches.01:44
lifelessthere are lots of groups which could be chosen01:44
lifelessthere is only one answer per that page01:44
wgrantBut we should probably add <blink>YOU ARE PROBABLY STUPID</blink> to branches owned by open teams.01:44
nigelbheh01:45
nigelbwgrant: <marquee>01:45
poolie...01:46
pooliedon't people have to sign a coc or something to use ppas?01:46
poolieseems like this should be required for auto built branches01:46
pooliebut01:46
lifelessI think jml removed that01:46
wgrantpoolie: I think that requirement was waived.01:46
lifelessor planned to01:46
poolieyeah, that's probably better01:46
poolieamhnews :)01:46
lifelesswow buildbot is in bad shape02:22
wgrantOh?02:26
wgrantHmm, even more.02:26
wgrantExcellent.02:26
wgrantAh.02:26
wgrantIt was restarted but not cleaned.02:26
wgrantLOSA ping: please clean and restart pigeonpea02:27
lifeless6 fails in a row02:27
lifeless7 when the current one falls over entirely02:27
hloeungwgrant: ok02:27
hloeungwgrant: done02:30
wgranthloeung: Thanks.02:31
pooliewgrant, like this: https://code.launchpad.net/~mbp/launchpad/800295-protocol/+merge/8262902:56
StevenKDear buildbot, please DIALCF. No love, all of us.02:56
StevenKDear PQM, you're next. No love, me.02:57
nigelbheh.02:57
StevenKRight, I think that's all of the 127 test failures fixed.03:02
StevenKlifeless: So, do you have eight MPs for me to review? I'm feeling dangerously productive. :-P03:02
lifelessStevenK: TGIF03:03
StevenK+1,00003:04
huwshimiugh, there appears to be quite a bit of our CSS that just isn't used anymore03:20
* mwhudson fails to be surprised03:21
huwshimimwhudson: Yeah, but it makes me nervous03:21
mwhudsonhuwshimi: you get to delete code! bonus03:22
huwshimimwhudson: Yeah03:22
huwshimimwhudson: But I worry that I've missed something :)03:22
huwshimimwhudson: Even when my search of the whole codebase comes back with nothing03:22
mwhudsonyeah, i guess it's hard to write automated tests for css03:22
mwhudsonwe certainly construct class names from enums, which doesn't help grep...03:23
jtvwgrant: the dogfood builds yesterday worked, but I do see some errors in the log: CannotFetchFile, seemingly with empty URL & info.  Any idea what that might mean?03:31
mwhudsonStevenK: (from #-ops) ah, i see  https://bugs.launchpad.net/launchpad/+bug/704080 now03:32
_mup_Bug #704080: If there is only one recipe, it should redirect right to the recipe <confusing-ui> <qa-ok> <recipe> <Launchpad itself:Fix Released by stevenk> < https://launchpad.net/bugs/704080 >03:32
StevenKIndeed03:32
mwhudsonthat bug was about the list on a branch page, which says _1 recipe uses this branch_03:32
wgrantjtv: Well, possibly that it couldn't fetch the file. I've not seen them before, AFAICR.03:32
mwhudsonwhen the link says "View source package recipes" it's more confusing03:33
jtvwgrant: but then there ought to be a URL in the exception message, no?03:33
jtvIt looks as if it's getting no URL at all, and hence the error.03:33
wgrantjtv: No idea.03:33
wgrantHmm03:33
wgrantThat's not helpful.03:33
* mwhudson files https://bugs.launchpad.net/launchpad/+bug/89191803:35
_mup_Bug #891918: redirect from /~/+recipes to recipe when only one recipe can be confusing <confusing-ui> <Launchpad itself:New> < https://launchpad.net/bugs/891918 >03:35
StevenKmwhudson: So perhaps we should just hijack that link on Person:+index when they only have 1 recipe.03:38
mwhudsonStevenK: that would certainly work03:38
mwhudsonit's not a very important bug i guess03:39
* StevenK glares at mwhudson for not triaging :-P03:39
mwhudsonah yeah03:40
StevenKmwhudson: I'ved fixed it anyway03:40
mwhudsonta03:40
huwshimiIf I want to make modifications the CSS files that are loaded I assume I modify "buildout-templates/bin/combine-css.in"04:11
huwshimiAnd then how to I get that rebuilt into /bin so that it gets run with "make css_combine"?04:12
StevenKhuwshimi: Change the template and then 'make clean && make'04:12
huwshimiStevenK: ah ha04:13
wgrantYou can possibly also just bin/buildout04:13
StevenKPersonally, I like to make sure, but that requires sitting through buildmailman04:13
huwshimiawesome, bin/buildout worked04:14
StevenKRARGH, conflicts.04:14
* StevenK smash.04:14
lifelessStevenK: question04:14
lifelessStevenK: did you consider just telling owners etc to be members of the bugsupervisor team ?04:14
StevenKWhy should they? They *own* the pillar.04:15
lifelessdelegation04:15
StevenKSure, but they should also have the permission.04:16
lifelesswhy?04:16
StevenKCan I say a cop out and reply 'Because Curtis says so' ?04:16
lifelessif you must04:16
lifelessthe UI and help will need changing too04:17
StevenKadmins can do everything. owners delegate planning and bug responsibilities to drivers and bug supervisors. Drivers work with release planing, which encompasses bugs and specs, Bug supervisors can work bugs.04:17
lifelessgiven there are now 4 teams that can grant the permissions04:17
lifelessStevenK: yes, sure, so owners, drivers can be members of bug supervisors, and get those bits directly.04:17
lifelessStevenK: which will drop to 25% the number of teams that need examining by the DB when querying04:18
lifelesssince supervisor no long implies notification, there shouldn't be an issue with mail receipt etc04:18
StevenKlifeless: So, it's a Friday afternoon. I wanted to get this reviewed and landed before EOW. Not argue about it. :-(04:18
wgrantIt does imply it.04:19
wgrantUnless you really know what you're doing.04:19
lifelesswhat you're doing is inconsistent with the observer design, which will be an absolute list04:19
lifelessits more than a little surprising04:19
lifelessStevenK: I don't want to argue about it either.04:19
lifelessStevenK: I've mailed the bug.04:23
StevenKhttp://pastebin.ubuntu.com/741893/ Uhhhhh?04:23
lifelessStevenK: I think the change to check permissions rather than checking teams is good and important; I thin the changes to the security model are questionable.04:23
wgrantmake04:23
StevenKAh04:23
lifelessstrictly bin/buildout04:24
lifelessneed newer timeline04:24
wgrantUhoh04:24
wgrantSomething is wrong04:24
wgrantbuildbot hasn't failed again yet...04:24
lifeless?04:24
lifelessheh04:24
StevenKHah04:24
wgrantOne of the last eight builds has passed...04:24
lifelessspwaking of ROW04:28
lifelessbah04:28
lifelessEOW04:28
lifelessnight all04:28
wallyworld_lifeless: good night. but i bet you come back on later :-)04:29
wallyworld_StevenK: my first look at the diff - i think you can replace self.context.userHasPrivileges with self.userHasPrivileges in the view code04:29
StevenKwallyworld_: I hadn't pinged you yet because I was fixing the conflict.04:30
StevenKwallyworld_: Which line of the diff?04:30
wallyworld_StevenK: there's a few eg 85/8604:30
wallyworld_there's a mixin but the method it provides isn't used it appears04:31
StevenKAh, right04:31
wallyworld_since you are fixing something else anyway..... :-)04:32
StevenKwallyworld_: I was pushing the conflict change as I replied. Use of the property in the view fixed.04:34
wallyworld_thanks04:34
StevenKwallyworld_: Anything else, or you're still reading?04:36
wallyworld_StevenK: still reading. just groking the various permission consolidations04:37
wallyworld_StevenK: just saw that you could use roles.isBugSupervisor(self.pillar) instead of doing it yourself04:38
StevenKwallyworld_: Oh, has that landed on devel?04:39
StevenKI wasn't sure, so I left it.04:39
wallyworld_ah, stupid me, no sorry, not landed yet. but close i think. let me check04:39
wallyworld_StevenK: my ec2 run failed with 7 TestPoppy errors04:40
wallyworld_othereise it would have landed04:40
wallyworld_i think these are spurious?04:40
StevenKlp-land it, and I'll re-merge04:40
wallyworld_thanks, doing it now04:40
wallyworld_StevenK: in now04:44
StevenKwallyworld_: Thanks, merging.04:46
wallyworld_StevenK: also, i think you need a few unit tests to explicitly check that a person of each role type has privileges04:47
StevenKlifeless: Oh, and you know most of the code paths I'm changing were doing these checks anyway? I've just pulled them all together into one method.04:47
StevenKwallyworld_: I think the bug code is well enough tested, TBH.04:47
StevenKwallyworld_: But I can if you insist.04:48
lifelessStevenK: just carry on, I'll discuss with sinzui04:48
StevenKlifeless: So land it?04:48
wallyworld_it is well tested but this branch introduces behaviour which allows additional users/roles to do things and we are not explicitly testing for that04:48
wallyworld_the existing tests are great for regression testing but we need new tests for progression tests04:49
lifelessStevenK: Up to you - I'm not blocking it04:49
StevenKwallyworld_: I think the only change is admins, TBH.04:49
wallyworld_and people in project roles, no?04:49
StevenKwallyworld_: Most of that code was already there.04:50
StevenKI trusted the existing test suite while developing this.04:51
wallyworld_if it were me, i'd do a test case called TestUserHasPriviliges04:51
wallyworld_to explicitly test the new method in isolation04:51
StevenKwallyworld_: Like I say, happy to do so, if you insist.04:52
StevenKI'm happy with this branch since it removes more code than it adds.04:52
wallyworld_StevenK: that would be great if you could. it's a compromise because i'm not asking for additional tests on the view methods :-)04:52
wallyworld_and it won't take long just for one new test case :-)04:53
StevenKwallyworld_: One?04:53
wallyworld_one test case but several tests04:53
StevenKThere are 4 celebrities to test and 6 pillar tests04:53
wallyworld_yes, but these will be 10 tests foe the one test case04:54
wallyworld_StevenK: off to get kid from school. will check your mp again when  i get back04:58
pooliehuwshimi, hi?05:00
huwshimipoolie: Hi05:00
poolieit's after lunch and not yet eod :)05:00
huwshimipoolie: Ah right, sorry about that. I'm just trying to finish quite a large refactor05:01
poolienp i sympathize05:01
poolieperhaps i will start drafting something and then we can talk05:01
huwshimipoolie: yeah that sounds great05:02
huwshimipoolie: Feel free to shoot questions at me05:02
sinzuiwgrant, do you have time to mumble?05:04
wgrantsinzui: Sure05:05
StevenKsinzui: lifeless has concerns with my bug. But he's cooking.05:05
wgrantAlthough I make it 5 past midnight, so am tempted to object so you go to sleep.05:05
wgrantBut let me find my headset.05:05
sinzuiI replied. We want fix the root problem with launchpad, not make project contributors more angry with convoluted nested teams that require them to get spam05:06
StevenKsinzui: Thank you.05:06
huwshimiRefactoring anything (in this case CSS) is nerve-wracking without tests of any kind.05:20
StevenKwallyworld_: Are you back?05:23
huwshimiA review for someone if they're kind enough: https://code.launchpad.net/~huwshimi/launchpad/css-file-split-891896/+merge/8263605:44
wallyworld_StevenK: back now. bloody traffic really bad today :-(05:45
wallyworld_huwshimi: looking in a sec05:46
StevenKwallyworld_: I've pushed the test05:46
huwshimiwallyworld_: Cheers :)05:46
huwshimiwallyworld_: Just to warn you: "4855 lines (+2306/-2391) 20 files modified"05:46
StevenKCrumbs05:46
huwshimiStevenK: Yeah, I was deleting Soyuz05:47
nigelbhuwshimi: Good job!05:47
StevenKNot large enough.05:47
huwshimiStevenK: I wasn't fond of the name, so thought, "Why not!"05:47
nigelbYou have too many pluses for deletion.05:47
huwshiminigelb: Shhh :P05:47
nigelbheh.05:48
nigelbSoyuz is sweat and blood, not code.05:48
StevenKwallyworld_ is a bad person. My branch removed more than it added, and then he wanted tests.05:48
nigelbOh and probably curses.05:48
StevenKnigelb: Bailing wire and gaffa tape, too05:48
StevenKProbably some pitch too05:48
nigelbTo hold it all together? Nice idea.05:48
wallyworld_i am not bad, i'm just drawn that way (says me channel Roger Rabbit)05:52
wallyworld_channeling05:52
wallyworld_huwshimi: so the files which include import.css won't pick up the stuff in components but the two cases of that it doesn't seem to matter05:58
huwshimiwallyworld_: Yeah, that was my intention. That should just import the base layer of our styles05:58
huwshimiwallyworld_: Sorry I should have explained on the MP05:59
wallyworld_np. and you don't see a case where somthing will need to import the base layer and additional compoent styles?05:59
huwshimiwallyworld_: There may be, but I suspect for testing you'd want to include them specifically. In the future we may want to provide a case for that, but for this initial commit I let it be06:00
wallyworld_sure, just checking :-)06:00
huwshimiwallyworld_: There may be a base set of components that are generic enough for that case06:00
huwshimiwallyworld_: np06:01
wallyworld_huwshimi: and apart from that, all the red/green is just cut'n'paste essentially?06:01
wallyworld_you've also run combine-css manually and checked the output?06:02
huwshimiwallyworld_: Yes, just splitting it between the files. I deleted 3 styles I think when I couldn't find any instances of them in the entire codebase (references to old yui 2 styles)06:02
huwshimiwallyworld_: Yeah the combine works and everything renders fine on the pages I checked06:03
wallyworld_and you checked pages that use something from components?06:03
huwshimiwallyworld_: Yes, for example there are components on the sidebar, and tables and stuff which all render fine06:04
wallyworld_cool. sounds good, thanks06:05
huwshimiwallyworld_: NO, thank you06:06
huwshimierm that no was a little forceful :)06:06
wallyworld_huwshimi: np. r=me06:07
huwshimiwallyworld_: Thankyou!06:07
huwshimiwallyworld_: unfortunately for you it's all smoke and mirrors :P06:08
wallyworld_huwshimi: ?06:08
huwshimiwallyworld_: I was trying to making a joke about smoke testing. I'll be about my business.06:09
wallyworld_huwshimi: it's been a long week, too long for bad puns :-)06:09
huwshimiwallyworld_: haha, I know you feel. Too long to be attempting puns too it appears06:10
=== wallyworld_ changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: - | Critical bugtasks: 287
* wallyworld_ off to have dinner with bigjools :-)06:41
wgrantDammit, it's been hotter down here today06:49
wgrantThan it was in Brisbane.06:49
wgrant33 vs 2606:49
wgrantYou're not doing a very good job of discouraging bigjools, .au :(06:50
jtvI thought it was supposed to be summer over there.06:55
jtvWhy is it colder than over here?06:55
=== wgrant changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: - | Critical bugtasks: 289
jtvwgrant: the errors in the buildmaster are all on rhenium — seemingly lost connections.06:56
wgrantjtv: rhenium is not infamous. But if it's only that one, perhaps it is special.06:56
jtvWhat really pains me at the moment is that the biggest remaining worry is code paths that violate read-only database policy (and thus need explicit exemptions).  Which means we ought to try each kind of upload.06:58
jtvThe most likely failure resulting from my branch is “read-only transaction” errors.06:58
jtvWhat kinds of build-farm jobs do we have?  I tried package builds, and I can try TTBJs, but everything else is a mystery to me.07:00
wgrantRecipe builds.07:00
wgrantWhich are easily QA'd on staging07:00
wgrantYou may wish to cowboy it there.07:00
jtvHow is staging's buildfarm set up?07:01
wgrantWhat do you mean?07:01
wgrantwallyworld_: Aw07:02
wgrantwallyworld_: I just noticed that the whole squad except for you is arriving in Budapest on the same flight.07:03
jtvwgrant: where does staging get its builders?07:03
wgrantjtv: clementine/concordia belong to it07:04
jtvSo it's got its own?07:04
wgrantBut it may also have access to the donated production builders07:04
wgrantRight.07:04
wgrantLike dogfood's ferraz/rubidium07:04
wgrantThey both have access to all four.07:04
adeuringgood morning07:04
jtvmorning adeuring!07:04
wgrantMorning adeuring.07:04
adeuringhi jtv!07:04
adeuringhi wgrant!07:05
jtvwgrant: if my feeling about the most likely failures is correct, we don't really need 4 builders any more.  One or two should be enough to trigger the errors I'm looking for, and half a dozen probably isn't enough to trigger the ones we're ultimately after.07:05
wgrantjtv: I except so07:06
jtv*expect?07:06
wgrantThat's the one.07:06
jtvrestecp07:06
jtvAnd staging has its own codehosting too, right?07:07
wgrantRight.07:07
wgrantWhich dogfood lacks.07:07
wgrantYou *can* test recipes on dogfood.07:07
wgrantOr at least could a year ago07:07
wgrantBecause it sort of uses production's codehosting.07:07
jtvI think it's time to hand back those builders I borrowed, and continue with staging.07:09
wgrantAgreed.07:09
wgrantThey'll need to be upgraded before they're sent back.07:09
jtvWould've been good to stress-test against hordes of builders, but that doesn't seem to be in the cards.  And at least we'll have eliminated a good portion of these bugs.07:09
jtvwgrant: what kind of upgrading do we need to do?07:14
wgrantjtv: The production builders have all been upgraded a few times since yours were donated.07:15
wgrantIf we just send them back to production, they'll be running different code to the rest.07:15
wgrantWhich would be bad.07:15
jtvHow do we go about upgrading them?07:16
wgrantPoke a LOSA or lamont.07:16
wgrantWe'll probably do a new upgrade on Monday.07:16
wgrantOr maybe tonight.07:16
wgrantBecause we like to live dangerously.07:16
jtvFriday night?07:16
wgrantRight, dangerously.07:17
hloeungjtv: I could upgrade the builders so that they're running the same as the others if you like07:17
wgrant(and the changes are tiny and limited to a regression fix and a tiny bit of extra debug info)07:17
jtvhloeung: that'd be great—and then I'd like to get them back into the production buildfarm as soon as possible.07:17
hloeungjtv: which ones are we talking about btw?07:18
jtv(Make sure they don't fall behind again etc.)07:18
* jtv digs up the RT07:18
jtvSee RT 4898107:18
jtvwgrant: looks like your aalib build broke rhenium.07:19
wgrantOh?07:19
jtvThat one's so old, I wouldn't be surprised if some essential file had flushed out of the librarian or something.07:20
hloeungjtv: thanks07:20
wgrantThat's possible.07:20
jtvAlthough apparently the build did suceed.07:20
jtvhttps://librarian.dogfood.launchpad.net/80686189/buildlog_ubuntu-oneiric-amd64.aalib_1.4p5-38build1_BUILDING.txt.gz07:20
adeuringlifeless: could you have a look this MP: https://code.launchpad.net/~adeuring/launchpad/bug-sorting-by-attachment-age/+merge/82315 ?07:35
poolievila, what do you mean "there's no feedback" about rejected mail08:37
poolieif lp doesn't like it, it will say so08:37
vilapoolie: not in my case, never08:37
poolieyou may be acclimatised to ignore it08:37
vilaIIRC it happens when I reply to merge proposals and forget to sign08:38
poolieit does send mail08:39
poolieit is either a bug or perhaps it's getting lost somewhere08:39
vilaha, lost somewhere rings a bell :-} My ISP have been dropping pqm failure emails until recently08:40
vilaspammers defeating the store-and-forward robustness of mail transport is the main reason I hate them :-/08:41
burgergaHello, I have a small question: on the page of launchpad itself on launchpad it says that feature requests are handled in the wiki, however in the wiki I cannot immediately see where I should do this, can anyone point me in the right direction08:44
pooliewhat's the request?08:44
pooliei suspect actually contrary to that text we really want people floating requests by irc, mail or bugs-08:45
burgergaah oke08:45
burgergaI would like to save a bug report as draft08:45
burgergasince often I have to start all over when I'm writing a lenghty one and have to go ;)08:46
pooliei suspect there is a bug for it08:46
pooliei will look08:46
burgergathink i found it08:48
burgergahttps://bugs.launchpad.net/launchpad/+bug/32772808:48
_mup_Bug #327728: Create tasks <feature> <lp-registry> <Launchpad itself:Triaged> < https://launchpad.net/bugs/327728 >08:48
burgergathanks08:49
burgerga:)08:49
pooliehm08:49
pooliei think that's a bit different08:49
burgergayes it covers more08:50
pooliesmaller bugs are more likely to be fixed :)08:50
poolieas long as they're not too small08:50
burgergayes, I think they changed the bug report to "create tasks" and then marked it as duplicate of another bug08:51
burgergaso I think I should change it back to "save drafts"08:52
poolieand undupe it08:55
burgergaok will do, thanks for the help08:55
pooliei just got a failure in  lp.translations.tests.test_rosetta_branches_script.TestRosettaBranchesScript.test_rosetta_branches_script_oops for the second time running08:55
pooliejtv, halp?08:55
jtvHi poolie08:56
poolieactually the smart thing here is for me to just leave these alone and someone else will solve it over the weekend08:56
poolieso i will do that08:56
jtvpoolie: did you check out the imports thing?08:57
jtvpoolie: I emailed about it the other day… “import lp.codehosting” has side effects.  Removing it (because it looks redundant) or putting it in its regular alphabetical place may break things.08:59
jtvAnd we have a maintenance script that may do either.08:59
poolie:/08:59
pooliethis is bug 89081609:00
poolie?09:00
_mup_Bug #890816: Intermittent test failures: TestPullerMasterIntegration.test_mirror <Launchpad itself:Triaged> < https://launchpad.net/bugs/890816 >09:00
=== adeuring changed the topic of #launchpad-dev to: #launchpad-dev ist: https://dev.launchpad.net/ | On call reviewer: adeuring | Critical bugtasks: 289
pooliejtv i have only one revision and it doesn't mention that09:01
pooliedoesn't mention lp.codehosting09:01
pooliecould it really be related?09:01
jtvLet me just try again to load up that bug page09:02
jtvpoolie: ah no…  this is twisted trouble.  :(09:03
pooliemy branch is https://code.launchpad.net/~mbp/launchpad/800295-protocol/+merge/8262909:04
poolieo/ mrevell09:06
mrevellHello09:06
danhgMorning all09:11
mrevellhey danhg09:12
pooliemrevell, i sent a mail about markdown09:13
mrevellpoolie, Oh cool /me looks09:14
pooliewe could talk if you want09:15
mrevellpoolie, Sure. Skype took a dislike to my mic yesterday, let me see if that's still a problem.09:16
pooliemaybe just here09:18
poolieam still fighting the buildd gorilla09:18
mrevellpoolie, Oh yeah. This came up in the stakeholder meeting yesterday09:18
pooliebuildds, or markup?09:18
mrevellpoolie, Bryce put forward a request for some form of mark-up in descriptions etc09:19
poolieyeah i saw, so i thought i would finally write it down09:19
pooliekind of sketchy but its a start09:19
mrevellpoolie, Do you have any idea how long it'd take to get to your proposed first step? (markdown for project descriptions, behind a ff)09:30
=== almaisan-away is now known as al-maisan
pooliein the best case a day?09:32
pooliein the worst case, forever09:32
pooliei think hooking it up will be cheap but deploying stuff is a pain in the butt09:33
pooliebut after the last couple of weeks my butt is a bit tougher09:33
poolieother people could probably estimate it better09:33
poolieif i took those steps would it be accepted?09:33
mrevellpoolie, From a product PoV, absolutely.09:37
poolienice09:37
poolieobviously robert and the more experienced developers can have their say too09:38
nigelbomg unicorns and ponnies if you can pull it off though :)09:38
mrevellheh09:38
nigelbThis inline commenting blog post worries me. We should have it in LP :|09:39
pooliewe should09:39
pooliethat needs someone with more ajax than me09:39
poolienigelb, i suspect that too, like this, may not be infeasible if we just decide to do it09:41
mrevellnigelb, poolie: It's something that's been on my roadmap from day one and we discussed it in the stakeholder meeting yesterday. Basically, I want it in Launchpad; lots of people want it in Launchpad. Today, I get to take all the requests from the stakeholder meeting, combine them with our own desires for LP and then see what we can fit into roughly 18 months.09:41
pooliemrevell, i guess the reason i ask "will it be accepted"09:41
nigelbWe can also bend those "things that can fit in 18 months" with outside help :)09:41
poolieis because it's been blocked by a kind of perfectionism a bit before09:41
poolieso i'm proposing a pretty grungy stepwise approach09:42
pooliebut i think we have mostly put that perfectionism behind us09:42
mrevellpoolie, Yeah, perfectionism has left us with a remarkably imperfect product.09:43
nigelbheh09:43
mrevellpoolie, fwiw, what you propose to do looks like just the sort of small, realistic, incremental change that I want us to do more of in LP.09:44
poolie\heart09:44
nigelb:)09:44
poolielet's see09:44
wgrantThis seems like a pretty unobjectionable incremental change.09:45
nigelbWhich one? Markdown or inline commenting?09:45
wgrantMarkdown.09:45
wgrantInline commenting is not small.09:45
wgrantAt all.09:45
nigelbYeah.09:45
wgrantBecause we have dynamic diffs.09:45
nigelbAh. Right.09:45
nigelb#win.09:46
nigelbWe should be able to do some sort of metadata on that diff somewhere, shouldn't we?09:46
mrevellYeah, in-line commenting has a budget of 8 weeks in my proposed roadmap (the revised version coming soon to a -dev list near you) and I'm probably being optimistic.09:46
wgrantOoh, we have a roadmap?09:47
wgrantIt's really hard to get any kind of estimate.09:48
wgrantIt would probably require a major rework of the MP system.09:48
wgrantIt's not at all clear how it would work.09:48
poolieso09:48
poolieif i was going to look for a small thing09:48
pooliei would do some kind of js that just quotes lines from the diff in to the edit window09:48
pooliemaybe with text next to them09:49
pooliesomething like that09:49
poolieit may be a bit of a detour but it is not scary in size09:49
poolieit would improve it09:49
pooliebut all the comments are still just text blocks; you don't need a comment of attachments that float around as the diff changes09:49
pooliemaybe that's too small of a win though09:49
lifelessStevenK: would this -  https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-4a5b9cd9bd803fdc1960fbd685d6871d#statementlog have been easier to work on , for that bug nomination thing you needed backtraces of ?09:52
lifelessStevenK: its pretty crudely rendered ATM; I think making the sql format not do those crazy long lines would be another good incremental improvement09:52
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
rvbaadeuring: Hi, could you please have a look at https://code.launchpad.net/~rvb/launchpad/activereviews-bug-867941-hugequery/+merge/82650 ?10:42
adeuringrvba: sure10:42
rvbaThank you.10:42
jtvcjwatson: do you ever have the problem that approving uploads on DistroSeries:+queue pages is too slow?11:08
adeuringrvba: vrey nice work, r=me11:09
rvbaadeuring: thanks for the review!  We will see how this improves the performance of the page in question.11:10
adeuringrvba: right, it's hard to predict. Might be worth to try the query on staging11:11
rvbaadeuring: I've had the query run on production a few times and it improved things quite a lot.11:12
adeuringrvba: even better11:12
rvba4.5s → 2s11:12
rvbaThis is still not ideal but that's a start.11:12
adeuringrvba: right, but 2 seconds is uite good for such a complex query. There might be other parts of the code that could be improved11:13
jtvIt's quite a lot, from the sound of it.11:13
rvbaadeuring: one the runs: https://pastebin.canonical.com/55946/11:14
cjwatsonjtv: frankly, most of the time I don't use +queue because every time I do it times out so much that I regret it.  (Even though I know I should use +queue in preference to privileged shell commands if possible.)11:16
cjwatsonThe last time I tried to use +queue it timed out even displaying the queue.11:17
cjwatsonIt's working at the moment - for now11:17
jtvcjwatson: I found a 0.8s query in there that was repeated several times, that I got down to 0.2—0.3ms.  I just Q/A'ed it, so it should be on production soon.  I'd like to ask you to try it again, and please please keep a very critical eye on it both in terms of performance and correctness.11:18
jtvThat's when submitting the form; I don't think it'll help page display.11:18
jtvI do know that query is used in a few other places though, so hopefully you'll feel improvements in several places.11:18
cjwatsonjtv: OK, that's good, I'll go back to trying to use it from time to time11:19
cjwatson(+queue still has several other awkwardnesses that block me from using it for everything, though.)11:19
jtvcjwatson: thanks.  Given how important and complex the code is, the sooner you can give it the third degree the better!11:19
cjwatsonNotably https://bugs.launchpad.net/launchpad/+bug/828649.11:20
_mup_Bug #828649: queue UI: apparently no way to override individual binaries <derivation> <queue-page> <Launchpad itself:Triaged> < https://launchpad.net/bugs/828649 >11:20
jtvWell, one step at a time!  I'm particularly concerned that this should be correct, and it seems the same query pops up in other places as well.11:21
cjwatsonI've also passed your request on to others; for example I think pitti uses +queue more than I do, for stable release managemnt11:21
cjwatson+e11:21
jtvThanks!11:22
=== al-maisan is now known as almaisan-away
=== matsubara-afk is now known as matsubara
rick_h_morning12:12
rvbamorning rick_h_12:18
deryckMorning, folks.12:33
rick_h_morning12:34
rick_h_http://blog.labix.org/2011/11/17/launchpad-rietveld-happycodereviews is crazy. I was complaining to jcastro that lp needed to integrate reviewboard for years and then there's this hah12:34
=== salgado is now known as salgado-brb
=== almaisan-away is now known as al-maisan
=== salgado-brb is now known as salgado
=== bac changed the topic of #launchpad-dev to: ist: https://dev.launchpad.net/ | On call reviewer: adeuring, bac | Critical bugtasks: 289
mrevellrick_h_, dev.launchpad.net/Projects/CustomBugListings14:32
=== Guest10379 is now known as benji
gary_posteradeuring or bac, when/if you get a chance could you please review https://code.launchpad.net/~gary/launchpad/bug724609/+merge/82689?15:02
bacgary_poster: i will15:02
gary_posterthanks bac15:02
gary_posterthanks for tackling buildbot allenap. I was just about to start, and am still willing to, but if you are happy with fixing it, that's great by me15:05
gary_posterI'll go do some more CHR :-P15:05
allenapgary_poster: I'm happy to do it.15:09
gary_postercool thanks again allenap15:09
allenapNo worries :)15:11
=== al-maisan is now known as almaisan-away
jcsackettadeuring or bac: can i add https://code.launchpad.net/~jcsackett/launchpad/private-bugs-open-teams-and-delegate-teams-oh-my/+merge/82703 to your review work today?16:22
bacjcsackett: i will take it now16:22
jcsackettthanks, bac.16:22
sinzuijcsackett,  I want to run this in production to clean up the data to match the rules in production: http://pastebin.ubuntu.com/742379/16:22
jcsackettsinzui: taking a look now.16:23
jcsackettsinzui: this looks fine to me.16:29
jcsackettdo our new rules require maintainer roles to be exclusive? that must have drifted pass me in the email masses.16:30
sinzuijcsackett, yes. they do. The maintainer automatically get access to all private and security issues in a project.16:31
jcsackettsinzui: oh right. that makes sense.16:31
* jcsackett is not completely with it yet, today.16:31
timrcis there anyway updates to staging can be done in the background and then brought to the foreground as soon as they are done to cause minimal disruption of service? or was I completely crazy to use staging for testing purposes?16:35
=== adeuring changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: bac | Critical bugtasks: 289
=== matsubara is now known as matsubara-lunch
jcsackettbac: thanks for the review.16:36
allenapbac: Up for a short review? https://code.launchpad.net/~allenap/launchpad/a-moment-ago-1/+merge/8270616:36
=== salgado is now known as salgado-lunch
timrcand why are we doing updates on a Friday? that seems dubious at best16:41
sinzuitimrc, staging's DB has not been updated on 7 weeks16:41
timrcso maybe it's just my luck :)?16:42
sinzuiIt is so stale that its data does not match the rules in production code16:42
timrcit seems that whenever I need to run these unit tests (which work against staging), there's a disruption of service16:42
sinzuitimrc, staging should update on our saturdays. It has a long history of irregularity. I think it updated only 26 times last year16:42
sinzuitimrc It does get code updates several times a day. It has been unavailable more than usual because of the failed DB restores I think16:44
timrcsinzui, is there any reason why we can't have two copies of staging? while one is getting updated, the other is serving requests?16:44
sinzuitimrc, we do. qastaging16:44
timrcah okay, so I should write my tests to try one and then default to the other?16:44
sinzuiits data is really ancient16:45
timrcsinzui, the data matters not to me, as long as the api is consistent16:45
sinzuitimrc, it is. I often switch by scripts between staging and qastaging based on availability.16:46
timrcsinzui, awesome16:46
timrcI had it in my head that qastaging was something that was for internal use by the LP team16:46
jcsacketttimrc: we will do horrible things to qastaging's data in the pursuit of qa. if you don't care about that, meh, no worries. :-)16:47
jcsackettsinzui: you want/have time to mumble?16:47
timrcjcsackett, nah, I just need to be able to file bugs against a certain project and then verify things are set correctly...16:48
jcsackettsounds like an excellent use of qastaging, then. :-)16:48
timrcjcsackett, sinzui: thanks for your assistance / guidance16:49
bacallenap: sure16:51
allenapThanks.16:52
allenapThanks Brad.16:57
=== beuno is now known as beuno-lunch
sinzuijcsackett, yes17:30
jmlI find myself missing buildout.17:33
jmlWhat's wrong with me?17:33
=== matsubara-lunch is now known as matsubara
=== salgado-lunch is now known as salgado
* deryck must have been too loud in the coffee shop call with rick_h_ 17:59
deryckpeople are staring at me oddly17:59
deryckjml, I like buildout.18:03
deryckmaybe something's wrong with me though ;)18:04
jmlderyck: I find it compares favourably to pip+virtualenv18:04
* jml has to go18:04
jmlcrap. am late18:04
derycklater!18:04
rick_h_deryck: so the two bugs that have pqm success messages I can move the cards to "deployment ready"?18:12
deryckrick_h_, ah, no, not yet... :)18:13
rick_h_ok cool18:13
deryckrick_h_, they need to play in buildnot for anywhere from 4-72 hours depending on how much buildnot hates you....18:13
rick_h_ok, makes sense. wasn't sure what level was "ready" and "done"18:13
deryckrick_h_, whenever it does merge to "stable" from "devel" which happens after the rarely succesful buildnot run....18:14
deryckrick_h_, you'll get an email that the bug was updated with "qa-needstesting" tag...18:14
deryckrick_h_, and then you'll need to manually qa your change on our qastaging server.18:14
* deryck looks for a wiki page18:14
deryckrick_h_, https://dev.launchpad.net/QA/QAForContinuousRollouts18:15
rick_h_ty18:15
deryckrick_h_, that should explain how to qa and how to tag the bugs.18:15
deryckrick_h_, if you have questions when you get to it, just grab one of us on irc.18:16
rick_h_will do18:16
deryckrick_h_, and of course the "rarely successful build" stuff was me joking.  ... mostly. ;)18:16
=== beuno-lunch is now known as beuno
timrcsinzui, does LP reap bugs marked as 'invalid' on staging and qastaging or do they persist?18:28
abentleytimrc: I'd be surprised if they have special handling.  Everything gets wiped when we do a full restore.18:44
abentleybac: could you please review https://code.launchpad.net/~abentley/launchpad/pre-cache-batches/+merge/82716 ?18:46
deryckok, I'm out.  Later on, everyone!19:02
bacabentley: at line 214 of your MP are the args in the right order?19:48
abentleybac: looks right to me.19:49
abentleyY.bind takes function, this, and then optional function parameters.19:50
abentleybac: So the output of load_model will be the third parameter to update_from_new_model19:51
sinzuitimrc, abentley is correct. We lets the odd data accumulate because we expect a db restore to happen on Saturdays. And I do expect one tomorrow since the slony update was successful in production19:52
bacabentley: the signature is:  update_from_new_model: function(query, fetch_only, model){19:54
bacabentley: and the bind is:19:54
bac+                success: Y.bind(19:54
bac214+                    this.update_from_new_model, this, query, fetch_only),19:54
bacabentley: ok, nm, i see where i was misreading it19:54
abentleybac: I hate non-bound instance methods with a fiery passion, if that makes you feel any better.19:55
bacabentley: it is confusing.  but in my head i saw query and fetch_only reversed19:56
abentleybac: ah.19:58
abentleybac: thanks for the reivew.20:08
rick_h_http://www.youtube.com/watch?v=wCexiX_eUJA&feature=youtu.be&hd=1 YUI MVC yay20:08
sinzuijcsackett, Can you look at the revised SQL to update production? https://pastebin.canonical.com/56052/ We are certain that the script does not need to check for open teams in open teams.20:26
sinzui^ bac can you look at the SQL I want to run in production?20:33
* bac looks20:34
benjithe Fedora Board is asking us what should be done with https://launchpad.net/fedora (at https://launchpad.net/fedora).  If anyone has things I should tell them (or would like to say yourself), let me know.20:34
sinzuibenji, We cannot delete it or deactivate it without a code change. The data is not valuable. I have long wanted to be able to delete or deactivate distros that mis inform users that they can contribute to fedora using Lp20:36
jcsackettsinzui: looks fine to me, given your assurances.20:37
bacsinzui: the SQL looks good to me.20:37
sinzuijcsackett, thedac confirms the expensive part of my failed query never return exceptions to avoid20:38
jcsackettsinzui: that's very good to know.20:38
benjisinzui: in that case I'll tell them the first bit ("We cannot delete it or deactivate it without a code change.") and leave it at that.  They'll probably loose interest after that.20:40
sinzuibenji, I image two strategies if this becomes important:20:40
sinzuipistol: Update db to obfuscate "fedora"20:41
sinzuiwhip: add active column to schema, update sets/searches to only list active distros; send a 404 when users visit deactivated distros20:42
benjisounds reasonable, thanks sinzui20:44
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
benjibac: heh; I'm glad my CHR is over for today.21:03
rick_h_CHR?21:04
=== matsubara is now known as matsubara-afk
benjirick_h_: two things 1) I am aflicted with cross-channel-itis; which means that I sometimes reply to someone in a different channel than the one in which they were speaking to me, and 2) the maint. teams do things like triage bugs and answer user questions and it's called CHR21:12
rick_h_ok, I see a lot of nicknames/codes flying and try to make sense of them. Couldn't figure out what CHR would stand for21:12
bacrick_h_: Community Help Rotataion -- come on, man, that should be obvious21:13
flacostegary_poster: do you remember the distribute mess?21:45
flacostespecifically, i'm trying to run lazr.restful tests21:45
flacostebut running bootstrap.py it's trying to grab distribute21:45
flacosteand then all hell breaks loose21:45
flacostebecause distribute is worst than freebase21:46
gary_posterflacoste, heh21:49
gary_posterI vaguely remember this.21:49
gary_posterflacoste, I think if you use a clean python, it all works21:50
flacostethat's not the answer i'm looking for :-)21:50
flacosteit's bootstrap.py seems antique compared to lazr.restfulclient21:50
flacostewhich worked fine21:50
flacosteso i'll try to update this first21:50
gary_posterflacoste, I think I tried this and it did not work21:50
flacostegary_poster: seems to have done the trick22:01
flacosteoh, and i added include-site-packages = false in buildout.cfg22:01
flacosteas that's what we want for lazr components22:01
flacosteusually22:01
flacostecloser to what virtualenv gives you22:01
flacostethat's a geat change you made there22:01
flacostesucky that upstream isn't keeping this22:01
gary_posterflacoste, I'm glad it worked for you.  I do think I found a problem with the new stuff when I tried it for lazr.restful.  Maybe it had to do with a dependency?  I'd be happy to review it/try to break it on Monday if you wanted.  If it works, that would be great22:03
flacostehmm, it's now building lxml2...22:04
flacostedo we really need that dependencies22:04
flacostesigh22:04
gary_poster:-)22:04
gary_posterI have to run go pick up kids22:04
gary_posterbye, have a great weekend22:04
=== bac changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: - | Critical bugtasks: 289
rick_h_bac: doh!22:23
sinzuiI am seeing about 10,000 private branches that the project owners cannot access.22:25
sinzuiI think I need to discount merged branches...but I believe that team/person merges, and team/project restructuring easily looses branches22:26
=== jcsackett_ is now known as jcsackett
timrc289 critical bugtasks... what's the prize for reaching 300?22:54
sinzuiseppuku23:02
sinzuiI was tempted last night to delete everything in my local lp branch and propose it for merging with devel because it would 80% of all Lp bugs23:04
wgrantsinzui: +123:08
iamfuzzwgrant, so glad to see you :-)23:24
wgrantUhoh!23:28
wgrantiamfuzz: What broke?23:29
iamfuzzwgrant, Actually went smoother than expected, but I can't get the buildd to kickoff a build23:29
iamfuzzwgrant, I uploaded two packages, and they're both still just sitting there waiting23:29
iamfuzzwgrant, I enabled bob the builder (nice touch)23:29
iamfuzzwgrant, but he seems lazy today23:30
iamfuzzwgrant, and the queue shows nothing23:30
iamfuzzwgrant, I go to my ppa, and there they sit waiting to build23:30
wgrantiamfuzz: bob is a non-virtual builder, PPAs default to virtual.23:31
iamfuzzwgrant, can i lie and just check that box?23:31
wgrantHead over to https://launchpad.dev/builders/bob/+edit, check "Virtual", enter anything at all into the VM host box, and see if that solves it.23:31
wgrantYeah, the command the dev config uses to reset the VM is "echo $vmhost"23:32
wgrantSo it will always succeed.23:32
iamfuzzwgrant, looks like that did the trick!23:34
iamfuzzwgrant, so is it really as simple as installing launchpad-buildd on another box, then entering its details into LP and voila, another builder?23:34
iamfuzzwgrant, I assume remote builders will upload files back to the soyuz host properly?23:34
wgrantiamfuzz: You'll probably need to play around with /etc/hosts and/or DNS to get it to resolve ppa.launchpad.dev/archive.launchpad.dev/launchpad.dev, but yeah, pretty much.23:36
* nigelb waves from a closer timezone!23:57
iamfuzzwgrant, how does one create apt sources for the buildds to pull from?23:58
iamfuzzwgrant, I ran this guy: scripts/ftpmaster-tools/manage-chroot.py -s lucid -a i386 add -f chroot-ubuntu-lucid-i386.tar.bz223:58
iamfuzzwgrant, but get a dependency wait on everything still23:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!