[00:03] wgrant: mumble? [00:10] Project windmill-devel build #111: STILL FAILING in 46 min: https://lpci.wedontsleep.org/job/windmill-devel/111/ === wallyworld changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: wallyworld* (jtv) | https://code.launchpad.net/launchpad-project/+activereviews | Critical bugs:210 - 0:[######=_]:256 [00:33] * wallyworld shakes fist at unity. check email shortcut has stopped working :-( [00:37] :( [00:38] Ah! thumper! [00:38] Why does my launcher not auto-hide now? [00:38] And then when I start mumble the launcher goes into the background :( [00:39] It's all your fault. [00:39] * thumper shrugs [01:02] Project windmill-devel build #112: STILL FAILING in 46 min: https://lpci.wedontsleep.org/job/windmill-devel/112/ === huwshimi_ is now known as huwshimi [01:10] wallyworld: Are you going to be able to do the ML QA? [01:11] wgrant: sinzui said he was but it's probably past his EOD now. is the rev on staging yet? that's what the holdup was [01:13] Ah, a good point. [01:13] staging is mid-update. [01:18] so how do you delete a blueprint ? [01:18] Lalala [01:18] ah [01:19] definition obsolete [01:20] man, [01:20] some go back a -long- way https://blueprints.launchpad.net/launchpad/+spec/record-bzr-branch [01:24] Should we garden or just disable the feature for LP? [01:24] ok I'm officially blind [01:24] https://blueprints.launchpad.net/launchpad/+spec/ui-roadmap [01:24] I don't have a particular opinion [01:24] we're not using it for planning [01:24] Ahaha [01:24] LEP + bugs seem to serve us well [01:25] And that spec is only for Code... [01:25] create a blueprint to remove blueprints? [01:26] noooo === huwshimi_ is now known as huwshimi [03:22] anyone know if it's possible to dynamically enable/disable the lp rss feed embedded as " I'm not sure it's possible. [03:25] And it's not going to be relevant for very long. [03:25] ? [03:25] No modern browser has the button any more. [03:25] ff4 does [03:25] and so does chrome [03:26] Which Chrome? [03:26] My Chromium doesn't. [03:26] i'm running the latest google chrome beta [03:26] why you running chromium and not chrome? [03:26] I also don't see it in Firefox 3. [03:27] Why would one run Chrome? [03:27] s/Firefox 3/Firefox 4/ [03:27] it may not be visible by default but you can drag the button to your toolbar [03:27] What benefits does Chrome provide, besides proprietariness and spying? [03:27] And a PDF reader. [03:27] Which I have a perfect good implementation of already. [03:27] h.264 i think [03:27] That's in chromium [03:27] My Chromium does H.264. [03:28] i read a while ago what the differences were but have forgotten [03:28] i thought chrome offered something significant but am not sure now [03:28] Chrome offers Android support, and chromium doesn't, but that's reaching a bit. [03:29] i think chrome's pdf viewer in inline? [03:29] is [03:29] I don't understand why you'd want to run the proprietary variant from a company known to be information-hungry, without knowing about significant benefits :( [03:29] It is, yes. Chrome has a proprietary inline PDF plugin. [03:29] But I consider that a misfeature. [03:29] that is important to me [03:30] Oh, heh. In January Chrome decided to drop H.264 [03:30] if i'm browsing, i hate external apps popping up [03:30] I like my window manager to manage my windows. [03:30] Rather than this stupid tabs thing. [03:30] Chrome also has it's own built-in implementation of flash. [03:30] you don't like tabbed browsing? i can't live without it [03:31] wallyworld_: Tabbed applications are a workaround for inadequate window managers. [03:31] It reminds me of IE embedding in Acrobat Reader, which just makes me twitch. [03:31] (but I do use browser tabs) [03:31] (because most contemporary window managers are inadequate) [03:31] we'll have to have a pub discussion about that wgrant. i can't use a browser without tabs :-) [03:31] most? [03:32] Tomorrow, wgrant switches to twm [03:32] wallyworld_: http://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoogleChrome [03:32] * wallyworld_ looks [03:32] wallyworld_, This is mostly because you don't have a window manager that makes it easy enough to track things that you don't need to have in-application implementations of window management to be able to cope. [03:32] Right. If my applications have to manage their own windows, my window manager is not doing it sjob. [03:32] persia: perhaps :-) but i sorta like all my web sessions together in the one window frame [03:33] wgrant, On a completely different note, I was pointed to you last week to ask what was required to happen to sbuild in oneiric to not need a separate Soyuz implementation come Querelous Quahog (or whatever) [03:33] persia: For multiarch? [03:34] Or just in general? [03:34] wallyworld_, Yes, one of the issues with current window managers is that they fail to track whether multiple windows come from the same application and sort it sensibly. [03:34] wgrant, In general. [03:34] yes. that applies to more than web browsing too of course [03:35] Indeed, which is why there are N implementations of "tabbing" for N applications (which is "doing it wrong") [03:35] sooo, with the rss stuff, i sadly fear i will have to force a page refresh whenever the user using inline ajax widget to change bug or branch privacy values :-( [03:35] persia: Two hacks are still required: the one to copy DDEBs to ~/public_html (which we can possibly externalise if primary archive ddeb support doesn't get finished by a maintenance squad in the next few months), and the one to return extended status info (depwait/chrootwait/etc.) [03:35] wallyworld_: That sounds like a major inconvenience for users for such a minor issue. [03:36] So the first is easy with a post-build script. [03:36] Right. [03:36] The second required something like a 10 line patch. [03:36] That I've just somewhere along the line. [03:36] just lost. [03:36] wgrant: yes, agreed :-( but without doing that, the bug is not considered fixed [03:36] wallyworld_: Why not? [03:37] wallyworld_: It's little worse than someone having a page open, someone else privatising the bug, and then the first person adding the RSS feed without refreshing. [03:37] wgrant, And those should be sufficient? What was your concern about multiarch? [03:37] because curtis said so :-) plus it's possible to get an rss feed of a private bug if the page was loaded when the bug was public and the privacy changed inline [03:38] persia: Well, once we have non-closed architectures through multiarch, I suspect we'll need to use an sbuild that has a multiarch-capable resolver. [03:38] persia: Around a year ago I ported launchpad-buildd to then-current Ubuntu sbuild, and that was all that was required. [03:38] distro sbuild (at least in oneiric) no longer uses the internal resolver by default: it defaults to apt. Would we expect this to be sufficient? [03:38] But then exams happened, and it bitrotted. [03:38] I suspect so. [03:39] Cool. How large was the launchpad-buildd porting patch? [03:43] * persia found the bitrotten branch and investigates [03:43] Thanks a lot for the pointers, and the prior work :) [03:43] wgrant: i've figured out another solution - if they hit the rss button (because it is enabled when it shouldn't be) i'll just redirect back to the bug/branch page and display a notification. that will suffice [03:45] wallyworld_: How can you know that? [03:45] Does it request the feed? [03:45] wgrant: yes, it makes a request to feeds.lp.net [03:45] Hopefully it handles an error/redirect sanely. [03:45] well i'm about to find out [03:46] i don't know if it will work but it seems like the best thing to try and do [03:46] persia: Apart from deleting sbuild, the diff isn't that bad... let's see. [03:47] wgrant, I'm looking at http://bazaar.launchpad.net/~wgrant/launchpad/use-system-sbuild/revision/11151 now : looks smallish. Needs forward-porting, of course, but it shouldn't be too bad. [03:47] launchpad-buildd doesn't change much. [03:47] I wonder if I still have that sbuild diff around somewhere. [03:47] Otherwise I might try to write it again. It's pretty small. [03:48] Just returning a different exit code depending on the failure stage. [03:48] You left it on LP: http://bazaar.launchpad.net/~wgrant/ubuntu/lucid/sbuild/extended-result/revision/26 [03:48] Hm, the LP diff is only like 140 lines. [03:48] Oh! [03:48] I had completely forgotten about that. [03:48] Thankyou for finding it. [03:48] That makes things a bit easier. [03:49] Yes. We use distributed version control so that we don't need to use our brains. [03:49] I was sure I must have had a diff somewhere. [03:49] The goal is to acheive productive senescence. [03:49] Since I had clearly deleted it at some point. [03:49] I didn't consider I would have pushed a branch. [03:49] wgrant: some users will use chrome though [03:50] (or, to misquote someone, real men don't make backups: they just upload to the internet and other people mirror their code) [03:53] wallyworld_: there is something I don't understand [03:53] wallyworld_: why are you worried about the rss feed link; surely the problem is on the feeds page? [03:54] wallyworld_: or perhaps I misunderstand whats going on here [03:55] persia: So, I think it all works now except for ddebs. [03:55] Which should be easy enough. [04:04] Huh. [04:04] test_handleStatus_OK_successful_upload just failed on lucid_db_lp too ;( [04:04] :( [04:04] Curse you, Twisted. [04:07] wallyworld_: Looks like staging shoudl have your rev now. [04:08] wgrant: ok. will quickly finish the mp i'm on first [04:10] wallyworld_: Thanks. [04:20] wgrant, You mean "all works now, with the identified patches" or "everything was merged while I wasn't looking except this bit"? [04:22] persia: Neither of those branches are merged. [04:22] They both must be. [04:22] OK. I am now unconfused :) [04:28] mwhudson: what was the confusing bit about team participation / directory service ? [04:46] hi wallyworld_—I'm a bit late today [04:47] jtv: hi, no reviews yet anyway [04:47] but i'm about to finish a mp myself [04:47] then I'll take that [04:47] :-) [04:48] And you can mentor me. :) [04:48] Whoo, looks like I landed 3 branches overnight. [04:57] We do have a long-running buildbot failure though. [04:57] https://lpbuildbot.canonical.com/builders/lucid_db_lp/builds/966/steps/shell_6/logs/summary [04:58] good morning [05:00] hello nigelb [05:01] jcsacket was supposed to re-land this last night, can someone check if its done running through the tests? https://code.launchpad.net/~nigelbabu/launchpad/203478-meeting-sort/+merge/61623 [05:05] If it isn't marked as Merged, it either failed ec2 or failed PQM [05:05] StevenK: It failed once. I fixed and he said he'd reland [05:07] mwhudson: I've tweaked, see if its helpful ? [05:07] nigelb: Did you get a mail from an ec2 instance? [05:08] StevenK: Not yet. But I'm not sure its 4 hours yet. [05:08] (Darn, I've had too less sleep :\) [05:12] Right. Sadly, we can't check [05:13] StevenK: Ah. [05:15] sigh [05:15] for attendance in self.context.attendances: [05:15] if attendance.attendee == self.user: [05:15] whats wrong with this code [05:15] Heh [05:16] yes, you can break a sprint by having too many attendees [05:16] but it will self limit: once we can't late evaluate in the signup form, it won't get worse [05:19] ah, I lie. that is eager loaded, but still - should be a direct probe. [05:19] that looks like somewhere around code I touched. [05:20] Sprint.checkAuthenticated also makes me want to cry. [05:20] I wonder if thats where the python time really is going [05:20] * lifeless hopes not [05:21] Also I'm not quite sure how that makes sense. [05:21] qastaging is down ? [05:21] Working for me... [05:22] Bwaha [05:22] Perl 5.14 is out, and Debian/Ubuntu have yet to finish the 5.12 transition. [05:22] Yup. [05:25] armel caught up! [05:25] The build queues are empty for the first time in two months :) [05:26] Gasp! [05:26] Already! That's fairly early in the cycle. [05:26] wgrant: check SprintMeetingExportView . initialize [05:26] wgrant: and the cunning combination of passing domain filters in and in-python filtering. [05:26] wgrant: I think we have lots of opportunities to make things better here [05:27] lifeless: Oh, that is looooovely. [05:28] (note that priority is not-null) [05:28] priority = EnumCol(schema=SpecificationPriority, notNull=True [05:28] Blueprints are slated to go away in the distant future right? Would sprints go away with them? [05:32] no [05:32] the functionality is to be kept [05:32] but the hard to justify split between blueprints and bugs is to go [05:33] ah, okay. [05:33] Blueprints and bugs turn into 'issues' [05:33] Launchpad has issues [05:33] * StevenK smirks [05:33] Yes. [05:34] Launchpad has *lots* of issues :p [05:36] hmm, I think we have two 'reload' helpers >< [05:37] Probably. [05:47] bulk has one [05:47] and I think someone added one to testing [05:47] (a broken one) === almaisan-away is now known as al-maisan [06:38] can has revue ? [06:40] lifeless: wallyworld_'s on call. [06:41] wallyworld_: oh hai - https://code.launchpad.net/~lifeless/launchpad/bug-784988/+merge/61697 === lifeless changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: wallyworld* (jtv) | https://code.launchpad.net/launchpad-project/+activereviews | Critical bugs:222 - 0:[######=_]:256 [06:45] lifeless: Lies. [06:45] lifeless: Lots of those are escalated. [06:45] Freshly. [06:45] SO they do not count for the goal that matters :) [06:46] What was it before? [06:46] the previous figure was 210 [06:46] wgrant is about to close a bunch [06:46] and I'll update it then [06:47] Indeed. [06:47] Was just opening the page. [06:48] Fail. [06:49] Whole lot criticals landed on qastaging half an hour ago :( [06:49] well, thats my critical for the day up for review [06:50] see you all monday [06:50] Night lifeless. [06:54] by lifeless! [06:54] *bye [06:55] StevenK, wgrant: is "<" a total ordering on debversions? [06:56] In other words, if not (x < y) and not (y < x), does that mean they're equal? [06:56] No. [06:56] There are some equivalent versions :( [06:56] well. [06:57] Equivalent ain't so bad I guess; it's unordered version pairs that I'm worried about. [06:57] Those equivalent debversions will compare identically, but the string representations differ. [06:57] wgrant: I don't think what you just said has any bearing on the question, come to think of it. [06:57] jtv: Two different versions compare identically. [06:58] Yes, but I'm asking about the case where two versions do not compare as x < y or y < x. [06:58] It depends what you mean by equal. [06:58] True. [06:58] They will be equal, but not the same. [06:59] So does this imply that it _is_ possible to have an unresolved DSD where the versions are "equal"? === wgrant changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: wallyworld* (jtv) | https://code.launchpad.net/launchpad-project/+activereviews | Critical bugs: 217 - 0:[######=_]:256 (-5 non-pie-critical) [07:00] Or are the equivalent versions considered equal for all intents and purposes? [07:00] It depends how the versions are compared. [07:00] Some parts of Soyuz treat them the same. [07:00] Some don't. [07:00] Awww, only 217 [07:00] This worries me somewhat. [07:00] Fortunately such versions are rare. [07:00] Yes. [07:00] It causes non-deterministic domination. [07:00] Which is rather unfortunate, quite unobvious, and entirely unhelpful. === wgrant changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: wallyworld* (jtv) | https://code.launchpad.net/launchpad-project/+activereviews | Critical bugs: 212 - 0:[######=_]:256 (+5 non-pie-critical) [07:01] wgrant: You know how the versions are compared for DSDs, since we wrote The Plan [07:01] StevenK: I don't. [07:01] I know how the base version is calculated. [07:01] I don't know how you compare the versions. [07:03] if self.source_version == self.parent_source_version: [07:03] What are they? [07:03] debversions or strs? [07:03] s/strs/unicodes/ [07:04] They are both debversions [07:04] In Python? [07:04] Do we have a clear definition of the comparison operators for those? [07:05] wgrant: No, the postgres type [07:05] Bug #654878, for reference. [07:05] <_mup_> Bug #654878: Should reject uploads with equivalent versions

< https://launchpad.net/bugs/654878 > [07:09] And is it possible for two versions to have no conclusive ordering at all? In other words, where not x < y and not y < x but we're also not sure that they're equivalent? [07:09] NAFAIK [07:10] I think equivalence is defined here as !(x < y || y < x) [07:10] Pretty much. [07:18] And people complain about SQL's 3-way logic... it's perfect for this sort of thing! [07:22] Die, foul demon. [07:22] Come on, would you rather have a false certainty than an honest null? Face the chasm, discard your illusions! [07:22] Meanwhile, I forget... did +localpackagediffs also show packages that are missing from, or specific to, the derived series? [07:24] No [07:24] There are seperate smaller pages for those [07:25] Then my check for "don't offer to sync packages that are newer in the child" doesn't need testing for the one-sided DSDTypes. [07:26] Project windmill-devel build #113: STILL FAILING in 46 min: https://lpci.wedontsleep.org/job/windmill-devel/113/ === lifeless changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: wallyworld* (jtv) | https://code.launchpad.net/launchpad-project/+activereviews | Critical bugs:217 - 0:[######=_]:256 [07:41] Project db-devel build #565: FAILURE in 5 hr 13 min: https://lpci.wedontsleep.org/job/db-devel/565/ [07:42] wgrant: Hi! What's not-pie-critical? [07:42] * StevenK smacks lifeless [07:42] Stop that! [07:44] wallyworld_: how's your MP coming? Meanwhile I've got a small one of my own up that you could review (but someone else would have to mentor it, of course): https://code.launchpad.net/~jtv/launchpad/db-bug-783435/+merge/61703 [07:44] lifeless: Such a graph is not of significant value if it can be arbitrarily massively inflated by stakeholders. Newly escalated bugs shouldn't count as part of the tech-debt critical pile, or we will never get anywhere! [07:45] jtv: stupid doc test giving me the shits. i'll look at yours first [07:45] wallyworld_: when in doubt, kill it off. :) [07:45] The doctest that is, not my MP! [07:45] * jtv has seen wallyworld_ with a big scary rifle... [07:45] (seeing the counter go backwards through no fault of ours is rather demotivating) [07:46] jtv: i'm thinking about it [07:46] uh-oh [07:59] jtv: do distro series packages always have numeric version numbers? like 1.0 1.1 etc? [08:00] wallyworld_: no, they're full Debian version strings such as 0.999c-ubuntu9 [08:00] and they have their own comparison operators. [08:00] They may have multiple dots, too. [08:01] eg. 1:1.2-3~beta2+really1.2-2~rc1+git20110223-2.3ubuntu4.5~hardy1+ppa1 [08:01] Which is depressingly not *that* contrived. :/ [08:01] jtv: perhaps the tests could use some version strings other than '1.0' to make that explicitly clear for noobs like me? [08:02] wallyworld_: this seems a bit of an arbitrary place to make that explicit, to be honest—I'd rather that the "oh this one's newer than that one" be instantly clear here. [08:02] jtv: and will a simple < be the correct comparison operator? [08:02] Yes, because it's the most conservative comparison. [08:03] (C++ background helps here :) [08:03] parent_source_version = StringCol(dbName='parent_source_version', [08:03] notNull=False) [08:04] That's not going to work. [08:04] i know how < works in C++ but wasn't sure if the version strings would always start with a perfix that made sense to compare [08:05] They may be debversions with a correct < in the DB, but in Python they are just strings. [08:05] I'm thinking not so much about how < works in C++, but how it is used: the less<> template, and its consistent use as the only comparison operator in ordered containers etc. [08:05] You may want to use apt_pkg.VersionCompare. [08:05] Or cast them to debversions in Python too. [08:05] wgrant: oh, they're not debversions in memory? [08:06] That's worrisome because I cribbed this from other code. [08:06] jtv: No, they're normal stringcols. [08:06] debversion in the DB is very new. [08:06] Or at least, I verified that other code also did straightforward comparisons. [08:06] jtv: Yes, and lots of code is wrong :) [08:06] * jtv trembles with joy [08:07] joy or something else :-) [08:07] wallyworld_: I think I'll try to contrive a test then where a string comparison would give the wrong answer. [08:07] okay, the merge I was talking about earlier did land successfully :) [08:07] nigelb: Great! [08:07] That's 2 bug fixes in a week \o/ [08:08] jtv: that would make me happier since i get the impression there's a lot that could go wrong in this area [08:08] * wallyworld_ knows way too little about debian packaging :-( [08:08] wallyworld_: it seems there is. This is where a C++ background is a bad thing because it instills far too much trust in the type system. :) [08:08] i hear you :-) [08:09] * wallyworld_ reboots. stupid unity :-( [08:09] * jtv ones worked at a project where a compiler upgrade from 4.x to 5.x revealed that the central object cache lookup had been comparing numeric ids to pointers all along [08:09] *once [08:09] Damn, I've gone dyslexic. [08:10] Gone? [08:10] hrm has the topic become stale? I see only 190 critical bugs === al-maisan is now known as almaisan-away [08:11] nigelb: This is over all of launchpad-project. [08:12] And there are a few private bugs. [08:12] I see 196 critical bugs in the launchpad project itself. [08:12] 214 bugs, 217 bugtasks in launchpad-project overall. [08:13] ah [08:13] I see 208 critical bugs now [08:13] I'm curious, why is bug 500015 critcal? [08:13] <_mup_> Bug #500015: IE js error in filebug

< https://launchpad.net/bugs/500015 > [08:14] nigelb: It's a JS exception that would be an OOPS if we had a JS OOPS system. [08:14] Ah. [08:14] So it is an honorary beneficiary of ZOP. [08:14] any more easy critical bugs left? ;) [08:15] You could look for critical bugs tagged easy or trivial. [08:15] wgrant: we don't accept all escalations, so its not arbitrarily inflated [08:15] sinzui tagged a few earlier in the week, but most have since been squashed. [08:15] lifeless: It is uncontrollable reversal of the countdown. [08:15] That is silly. [08:16] anyhow, my issue is much more pragmatic [08:17] We're just about always going to have *something* in the critical queue. I think the burndown should track the backlog. [08:17] I don't have a query to get the 'right' count (whatever that may be defined as - and I don't want to debate it right now - family time) with any reasonable ease [08:17] Or what's the point? [08:17] Perhaps. [08:17] theres a few factors and we should talk about it more on Monday [08:17] gotta run [08:17] Night! [08:18] bye again lifeless [08:20] is it just me or is the wording in bug 659184 complicated? [08:20] <_mup_> Bug #659184: IntegrityError: duplicate key value violates unique constraint "ticketmessage_message_ticket_uniq

< https://launchpad.net/bugs/659184 > [08:20] I can't make head or tail of what's said there. [08:21] It's also a duplicate. [08:21] I understand what's going on there, but is it easier if you read the dupe? [08:21] s/dupe/master/ [08:22] okay [08:23] heh, the master has copy paste of what's said in the dup :p [08:23] Bah. [08:23] Well. [08:24] MessageSet.fromEmail looks up the message ID and content, and checks if there's an existing identical Message in the DB. [08:24] If there is, it just links it in as a comment (with a BugMessage or QuestionMessage) rather than creating a new Message object and linking that. [08:25] But there is a UNIQUE constriant on BugMessage(bug, message) and QuestionMessage(question, message). [08:25] If it receives an identical email twice to the same bug or question, it will try to link the same Message twice, and run afoul of that constraint. [08:25] and the solution is? [08:27] Possibly just ignoring a second attempt to link a message to a bug. [08:29] this needs more read of code that I'm capable right now. [08:29] will read at home. [08:40] good morning [08:41] wgrant: What's fiera used for? [08:41] I can't recall [08:41] wallyworld_: having some lock problems with that branch. Hope to have an updated diff in a few minutes. [08:42] StevenK: It's buildd-manager. [08:42] jtv: ok. i just got my tests passing so will finish the mp. but i may have to cook dinner first [08:42] OK [08:43] Ah [08:44] wgrant: Perhaps it needs to go the way of the lucille DB user :-) [08:44] StevenK: Indeed, but I broke production for a few minutes with that one, so I am a bit more wary now. [08:44] Whee [08:46] wgrant: Wait, with lucille or fiera? [08:46] StevenK: lucille [08:46] wallyworld_: diff has updated. [08:46] wgrant: Clearly she didn't want to die [08:47] Project windmill-devel build #114: STILL FAILING in 46 min: https://lpci.wedontsleep.org/job/windmill-devel/114/ [08:47] jtv: ack. will look after cooking. just typing up mp and will light the bbq after hitting submit :-) [08:47] wallyworld_: by all means don't multitask while lighting stuff on fire. :) [08:48] Unless it's Soyuz code [08:49] No, even then. [08:55]