[00:14] infinity, lp #974750. thanks again [00:14] Launchpad bug 974750 in xdiagnose "Support gathering arbitrary display manager logs" [Wishlist,Triaged] https://launchpad.net/bugs/974750 === bladernr_ is now known as bladernr_afk [02:03] ScottK: I'm rejecting yofel's 4.8.2a uploads, since they are literally identical to their previous 4.8.2 counterparts. If you'd like to sort that out and figure out WTF? [02:03] Sigh. [02:03] infinity: I think there's a reason for it. [02:03] (Like, no upstream changes, and the changelog were the 4.8.2 changelogs with s/2/2a/ [02:03] ) [02:04] I'd like to think that if the version bumped, the orig would at least be different? I dunno. [02:05] Anyhow, one of those conflicted with an upload of yours that had an actual bugfix, so that sealed the deal for me. :P [02:05] OK. [02:05] I didn't check the queue, so I didn't see all of them. [02:05] (after all, I was fixing, not releasing) [02:06] The reason is that it was the a version in our PPA we use for pre-upload testing. [02:06] I'm unconvinced that s/4.8.2/4.8.2a/ debian/changelog && debuild -S qualifies as "releasing"... [02:06] Right, I meant I wasn't doing Ubuntu Release stuff. [02:06] Yeah. [02:06] Someone bumped the versions back down for the initial upload, but then that screwed up upgrades for PPA users. [02:07] We get pre-final tarballs from upstream for packaging and if they have to respin them pre-release then we bump the version. [02:07] So this is artificial version bumps to smooth PPA issues? :/ [02:08] Yes, but it's for people who are our best testers. [02:08] No, not questioning the rationale, just how you got there. [02:08] Since this is the final version for release anyone who installed the PPA packages will never see security updates, etc. [02:08] Surely, you could version the PPA stuff (in future) as 4.8.2~ ? [02:08] Might be a good idea. [02:08] For 4.8.2 we are where we are though. [02:09] Yeah, fair enough. [02:09] Please convey my apologies and have people reupload the no-change version bumps. [02:09] Now that I know what it's about. [02:09] You can accept from rejected. [02:09] Is there a 4.8.3 on the horizon to paper over the oops? :P [02:10] I can for the one that didn't conflict with yours. [02:10] I guess you can reupload kde-workspace. [02:10] I can redo mine. [02:10] Yes, but it'll be a post-release micro-version update. [02:11] Anyhow, un-rejected kdepim-runtime, I leave -workspace to you. [02:11] OK. [02:14] slangasek: Did you want to grab the pvr-omap4 debs and dpkg-deb -I/-c sanity check them/etc to make sure the output matches your source review? [02:17] jbicha: Your libcanberra changelog completely fails to mention one of the two added patches (the -lX11 one). [02:17] slangasek: Unless that's also your fault? I notice his debdiff has one of your old changelog entries magically changing the timestamp by 6 minutes. A case of bzr and archive being skewed? [02:23] infinity: thanks, I'll reupload without that extra patch [02:23] jbicha: Are we sure it's not needed? :) [02:25] ok, I could just add the patch to the changelog then [02:26] jbicha: Well, maybe it's not required. I have no idea. You tell me. :P [02:26] jbicha: If it's fixing a legit bug, please, add it to the changelog. ;) [02:26] I'll reject. [02:30] slangasek: thanks for the hamster-indicator deNEW [02:30] infinity: It should be there now. [02:31] infinity: hmm, here's an old libcanberra bug, wonder why it hasn't been fixed https://bugs.freedesktop.org/show_bug.cgi?id=31454 [02:31] Freedesktop bug 31454 in Unspecified "linking to libcanberra-gtkX fails because of missing -lX11" [Normal,New: ] [02:32] I've been running my patch for 2 months and it's seemed ok, rodrigo's patch is a bit different though [02:32] What was wrong with openchange? [02:33] ScottK: There were three of them. :P [02:33] Ah. OK. [02:34] jelmer was over achieving. [02:34] jelmer might have been sliiiightly impatient. [02:34] ;-) [02:36] jbicha: His is probably more correct, but yours does the same job. [02:36] jbicha: As for why the bug hasn't been addressed upstream, did you check the assignee? :P [02:36] *cough* [02:37] Was that my out loud voice? Hrm. [02:37] well it's his baby http://0pointer.de/lennart/projects/libcanberra/ [02:38] I'm going to avoid extending the metaphor to the ultimate "deadbeat dad" conclusion. [02:38] lol [02:45] I wish we had the manpower to do forced queue reviews all cycle long. [02:46] I do wonder how much saner things would be if we could get away with it without slowing everything to a crawl. [02:52] infinity: but then noone would accept gnome crack a month before release thats still in the middle of implementing new features and we'd be 6 months behind upstream [02:52] haha, true! [02:53] we'd have nothing to occupy our time after beta2 since we wouldn't have so many bugs from last minute packages [02:54] What a shame. We could instead work on features for the next release. That would be awful! [02:54] terrible [02:54] totally [03:01] its totally ok to rewrite how suspend on lid close is handled in gnome to use xrandr that breaks proprietary drivers that fedora who does gnome doesn't care about a month before release after all, that wont cause any regressions [03:01] whoops, some bitterness seeped through there, i'm sorry :) [03:01] I was going to say... [03:02] I believe ScottK has a shipment of tiny violins en route to me, I can share them with you. [03:03] infinity, thanks, please send one each to every nvidia laptop owner [03:04] I'm an nvidia laptop owner. [03:04] But I never close my lid. [03:04] That way lies madness. [03:07] Why would people be implementing new features in randr anyway? They'll just have to tear it out and rewrite it when wayland becomes the new hotness, like, next week. [03:07] infinity, uh huh [03:08] Sorry, I've been hanging out with keithp all week, I'm infected. [03:08] It'll pass. [03:11] infinity: they're making suspend on lid close require randr 1.3 features which proprietary drivers don't implement [03:12] i think thats fixed in a distro patch now anyway though, was just violins :) [03:12] Sarvatt: Brilliant. [03:13] its just fun coming across those things so close to release [03:23] infinity: Yofel, not me. [04:04] infinity: yes, I'm doing the binary new on pvr-omap4 as well [04:08] infinity: libcanberra> I have no clue, honestly... how long ago was that? [04:08] infinity: could be archive v. upload skew, certainly [05:10] jdstrand, Architectures are matching my understanding. [05:11] re: https://wiki.ubuntu.com/SecurityTeam/FAQ#Architectures [05:46] slangasek: I'm heading out, so don't have the time to look more closely, but at first glance, data/package_data_downloader.py looks like an exact copy of data/package-data-downloader? [05:46] (Maybe a symlink, I guess, debdiff doesn't deal well with those) [05:47] * infinity runs out for a zero-hour coffee with the locals. [06:40] Hi. To sponsor bug #949359, I used syncpackage, but nothing happened: is it still possible to sync package in universe? [06:40] Launchpad bug 949359 in bluefish "new upstream bluefish version fixes major bugs: Freeze Exception" [Undecided,In progress] https://launchpad.net/bugs/949359 [07:28] fabrice_sp: 09:05 -queuebot:#ubuntu-release- Unapproved: bluefish (precise-release/universe) [2.2.1-1ubuntu1 => 2.2.2-1] (no packageset) (sync) [07:28] fabrice_sp: https://lists.ubuntu.com/archives/ubuntu-devel/2012-April/035024.html [07:40] tumbleweed, I saw that email, but I thought that the deadline was final Freeze [07:41] and I found my sync request waiting in https://launchpad.net/ubuntu/precise/+queue?queue_state=1 (actually twice as I thought that it wasn't taken into account) [07:42] fabrice_sp: we can't only freeze seeded parts of the archive. It's all or nothing [07:42] oh, ok [07:47] Shall I do something more for the sync or I just have to be patient and it will be processed when somebody will be available? [08:31] fabrice_sp: just wait [09:21] impatience> confusion> (twice in the backscroll) You don't get mail for API syncs that land in unapproved, so it looks from your POV like nothing happened. [09:21] Irritating. [09:22] bug #830614 [09:22] Launchpad bug 830614 in launchpad "Email not immediately sent for copied packages which end up in NEW" [Low,Triaged] https://launchpad.net/bugs/830614 [11:07] skaet: thanks! you may want to double check that https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Architectures is communicating what you want it to. I found it somewhat confusing and probably inaccurate for lpia [11:55] does cdimage not live on antimony anymore (presumably nusakan now)? === bladernr_afk is now known as bladernr_ [12:57] Hello! I have a couple changes to the Unity Greeter that John Lea requested that I was hoping to push in today. Saw Kate's email and thought I'd run them by ya'll first. Especially as they are visual changes (though small) [12:57] Let me dig up URLs [12:58] https://code.launchpad.net/~mterry/unity-greeter/designfixups/+merge/100868 and https://code.launchpad.net/~mterry/light-themes/greeter-white-border/+merge/100856 [12:59] Basically, the changes slightly move the usernames down a bit. Make the password entry box slightly bigger. And make the focus color around buttons white instead of orange. [13:02] jbicha: ^^^ [13:29] mterry: ubuntu-docs doesn't document the greeter so minor tweaks are fine with me [13:30] jbicha, cool. Is that enough to proceed on then? [13:31] I guess so, the Release Team will give their +1/-1 by approving or rejecting the upload, right? [13:32] jbicha, fair enough :) [13:33] I would say that you should document the uife in a bug [13:34] Laney, I didn't file a formal one, wasn't sure it needed it. Do you mean I should file one or just document this IRC conversation? [13:35] both — the person who approves the upload might not necessarily read this conversation [13:36] Laney, right. But you're saying I need a further +1 on a UIFe bug. i.e. this conversation does not represent a UIFe? [13:36] I didn't see any release team member approving the UIFe. [13:36] no, I'm saying it does, just that you should put it onto LP for auditing [13:36] * Laney will. [13:36] Laney, OK [13:37] * jbicha logs out for a few minutes [13:37] Laney, where's the line on what kind of UI changes need a UIFe? Like, anything that would likely impact screenshots? [13:38] https://wiki.ubuntu.com/UserInterfaceFreeze [13:39] Laney, right. So I gather from your response that it's a hardline any-changes-at-all-no-matter-how-small [13:41] mterry: We/I usually don't know what the documentation contains, so defer to the people doing that work for their opinion, as happened here. [13:41] If it's in the default install then any change might impact their work, so it's a courtesy to check that. [13:41] Laney, k. So always ask :) [13:46] * ScottK pokes unseeded Universe stuff out of the queue. [13:48] skaet: other: I apologise for realising this late the missing release mail from Xubuntu, you can find it here: https://lists.ubuntu.com/archives/ubuntu-release/2012-April/001098.html [13:51] OK. Done. [13:51] (but the queue is slow) [14:08] skaet: can i trouble an AA to pocket-copy linux-3.0.0-19.32, linux-backports-modules-3.0.0-3.0.0-19.12 and linux-meta-3.0.0-19.23 to -proposed please [14:47] astraljava, thanks. [14:48] bjf, ack, lets see if slangasek can help when he comes on line. (if it hasn't been done by another AA already ;) ) [14:49] skaet: thanks, -18 was pretty bad and the sooner the better :-) [14:49] gotcha. [14:50] skaet: The pad needs clearing up for release, but I didn't mess with it since I didn't know what needed to be saved. [14:51] ScottK, its got history enabled, so feel free to clean up what you know is handled. [14:51] * skaet goes to get the link, for that alternate view [14:51] I didn't see what it started like for beta 2, so I'm not quite sure. [14:52] ScottK, are we talking the freeze pad, or ubuntu-release pad? [14:52] The one that's in /topic. [14:52] The release one. [14:53] I guess the freeze one should be there too. [14:53] http://pad.ubuntu.com/ep/pad/view/ubuntu-release/latest - is history of the release images... [14:53] I'll clean it now, since I'm in. [14:54] Thanks. [14:54] We'll start using it again, when we turn off the cron job [14:54] That would should probably have a pointer to the freeze one until then. [14:54] can we get -t in here? [14:54] I'll put the pad for the freeze archive up in the header later today. agree makes sense to have it handy. [15:03] * skaet wondering if flooded the bot on #ubuntu-meeting... anyone seeing what I put? [15:03] infinity: yes, the .py was a symlink (so that it's importable for testing) [15:06] skaet: FYI, I'll do Kubuntu since AFAIK Riddell is away. [15:07] thanks ScottK [15:08] hey, who accepted flashplugin-nonfree? It depends on the new version of update-manager still in the queue [15:08] ScottK: ? [15:09] sorry, it was sloppy of me to rely on the accept being delayed until the update-notifier had gone in [15:09] (update-notifier, not update-manager) [15:10] slangasek: That was me. It was unseeded multiverse, so technically not frozen. [15:10] yep - as I said, sloppy of me [15:12] ScottK: any chance you can review u-n? Otherwise I should do another flashplugin upload to revert [15:12] (and sit on it until u-n is accepted) [15:12] I'll take a look. [15:13] thanks [15:13] infinity made a start of it yesterday, but he's conferencing in California so I don't expect to see him for a while yet this morning :P [15:17] slangasek: Did this get an ack from translations? [15:17] bjf: looking at the kernel now [15:17] slangasek: cool [15:18] ScottK: it did not; I reasoned that, since the only time anyone will see this message is in a case where the upgrade/install otherwise would have failed with an opaque error, untranslated is better than nothing. But I can talk to them, in any case [15:19] slangasek: They should be notified, but I agree it shouldn't block. [15:19] * ScottK wonders how long until this cron job generates an "Ubuntu phones home" scare. [15:21] heh [15:25] slangasek: There are several Makefile.in that vanish in your change. That seems a bit surprising to me. Is that expected? [15:30] ScottK: hmm, it's not something I expected; let me have a closer look, it could be my screw-up or it could be a screw-up of the previous upload [15:33] Thanks [15:35] bjf: kernel copy done [15:35] ScottK: btw, I think the new qt has regressed drag-and-drop in mumble; I need to muster my facts and file a bug on that [15:36] slangasek: thanks [15:37] slangasek: OK. [15:37] fabo: ^^^ [15:39] slangasek: it seems to work for me [15:40] fabo: are you using unity-2d? it's specific to unity-2d [15:40] unity-2d+mumble [15:40] (I took a poll) [15:40] slangasek: ah true. I'm under KDE. [15:41] please don't spend any time on it just yet, I'm going to narrow it down a little more (restart desktop; try to downgrade qt) before filing a bug [15:41] ok [15:43] ScottK: beautiful; the u-n source package that was uploaded FTBFS due to missing files. Please reject and I'll look at how that happened [15:43] OK. [15:43] sorry, I build-tested out of the branch, not off the .dsc [15:44] ah of course, bzr-builddeb hook that calls autogen.sh, and ignores missing tools :P [15:44] ScottK: thanks for the careful scrutiny [15:44] slangasek: Done. FWIW, from what I could tell from staring at the intended changes they seemed fine. [15:45] You're welcome. [15:45] slangasek: You'll be filing a bzr-builddeb bug, right? [15:45] it's a bug in update-notifier's hook (specifically, its autogen.sh), not in bzr-builddeb itself [15:45] so I have to file an mvo bug [15:46] Oh. OK. [15:46] ;-) [15:51] slangasek, infinity: sorry about the multiple sync requests earlier; I hadn't realized they were being manually approved now [15:51] :) [15:51] I guess the past few syncs during freeze I did were just acked very very quickly [15:57] fyi, looks like there'll be another apt upload soon to make rosetta happy; we had stripped headers off the .pot files in the build tree to avoid build-time timestamp skew, and now rosetta doesn't like the headerless .pot files [15:57] ack [15:58] (this is non-critical for release since the translations themselves haven't changed, so rosetta already has a perfectly good set of imported strings; but we should tidy up if possible) [15:58] * skaet nods [16:02] ScottK: new u-n tarball uploaded, end-to-end build-tested this time [16:03] OK. I'll look in a few minutes. [16:03] thanks [16:03] could someone please take a look at virt-manager ^ [16:03] it's a simple regression fix for a recent patch [16:06] * slangasek takes virt-manager, to rebuild some of his karma [16:06] hehe [16:07] :) [16:11] waiting for it to get diffy. [16:11] slangasek, in scanning the lang-packs in the queue, they're pretty much looking like automatic updates. Anything in particular I should be looking for other than anomolies? [16:12] * skaet would like to get them through before Tuesday, when unity lands. [16:15] infinity, could you take a look at the compiz ones in the queue (GLES2 related)? your travel plans permitting. [16:15] mdeslaur: accepting, though I would note that 127.0.0.1 is not the only possible loopback address that could be affected here [16:16] mdeslaur: so perhaps a more robust fix is wanted long-term [16:17] skaet: language packs are always automatic updates in at least some sense; the challenge is making sure we didn't wind up with mismatched pairs of packages uploaded, such that the packs for a language become uninstallable after accept [16:17] and I don't know that we have any good tools for checking this [16:18] slangasek: Accepted. Don't forget about notifying translators (if you haven't already). [16:18] slangasek: yes, I agree. upstream's logic about what's local and what's not is pretty flawed. [16:19] ScottK: thanks, drafting mail to ubuntu-translators now [16:20] Great. [16:22] ev: it's been on nusakan for some months, yes [16:23] cjwatson: bug #967348 came up in the lubuntu release report today; do you know what's going on there? [16:23] Launchpad bug 967348 in lubuntu-meta "obconf is in the seed, but not in the ISO" [Undecided,New] https://launchpad.net/bugs/967348 [16:24] I've got about one minute here, let me look quickly [16:24] * cjwatson takes bets on the germinate task being bogus [16:26] :) [16:27] it's not a problem in current images AFAICS (from comparing livefs build logs), so don't worry about it for now. I'll do some archaeology when I get a chance [16:28] it was probably something to do with lubuntu being schizophrenic about whether they want recommends or not [16:28] (they build with --no-install-recommends, but use () seed entries ...) [16:28] cjwatson: ack, thanks for looking [16:34] slangasek, re: language packs, ack. [16:34] * skaet --> traveling for a while now. back on later. [16:36] skaet: have set bug importances for a few on http://iso.qa.ubuntu.com/qatracker/reports/defects/opened, but the remaining 'undecided' ones for foundations are all duplicates of bugs that do have the importance set; I think this is a bug in the report. [16:36] it even shows bugs as "new" when the master bug is "fix released" [16:37] skaet: who maintains this report? stgraber, or someone on QA? [16:37] slangasek, jibel says he's just put in a fix about the duplicates. [16:37] ok [16:38] lets see how it looks after that gets applied, and then if further clean up is necessary. [16:38] so that list of open defects should get a lot smaller shortly [16:38] * skaet still thinks launchpad should shadow status of bugs from master to its duplicates... :P [16:38] thanks for looking at them slangasek. [16:38] it does that for 'confirmed' status, and it's annoying as hell to get extra bug mail every time it does :-P [16:39] no problem [16:39] skaet: so as far as langpacks, given that the only affected images will be DVDs, I think it's best to just accept them all and look at uninstallability afterwards [16:39] anything else will be a lot more effort right now for little gain [16:40] slangasek. ok, will do as soon as I get back on line. [16:40] I can do it now if you like [16:40] slangasek, while before daily build, and I'd like to study them a bit. [16:40] ok [16:40] thanks. [17:11] slangasek: s/conferencing/travelling and day-offing/ [17:21] No one review/accept compiz-plugins until the above compiz is built and installed. [17:21] (Or just wait for my plane to land in 4 hours, and I'll do it) [17:22] Oh, nevermind, Oli actually gave it a properly-versioned build-dep. [17:23] Who is doing the skype packages now? I have an email I need to forward them. [17:25] ScottK: looks like mvo or slangasek from the last round of uploads [17:25] OK. Thanks. [17:27] It might be good if the maintainer field was updated in the skype packages to point at someone who still works at Canonical. [17:29] Probably. :P [17:29] skaet: You're not planning on accepting the langpacks by hand, are you? [17:30] skaet: I can just accept the mess in one go on ftpmaster. [17:30] infinity, was planning on going through them as education for me mostly. [17:30] not a big overhead really. [17:30] That way lies madness. [17:30] lol [17:31] Manually auditing packages that are auto-generated (several hundred of them!) sounds like masoshism. [17:31] masochism, too. [17:31] Typing hard. [17:32] I was planning on looking at about 20-30 to get feel for pattern, then applying a bulk operation. [17:32] * skaet is not that much of a masochist [17:32] You can't do them in bulk by more than a few at t atime. [17:32] Web UI will timeout. [17:32] Which was why I was offering to just one-shot the mess with a wildcard. :P [17:33] infinity, ok, go ahead. [17:33] (and thank you) [17:36] infinity: mmm, from the package relationships compiz really ought to have gone to -proposed [17:36] fwiw [17:37] ogra_: ^^ I guess that's your upload, so :) [17:37] slangasek: You have mail. [17:37] ScottK: reading, thanks [17:37] Great. [17:38] and yes, we should update the maintainer field; though I think I'll hold off on doing that until we have a permanent maintainer for it :P [17:38] slangasek: How about making a role address that can be pointed to whomever when they show up. [17:39] well, ideally the role address is "file a bug against the package in launchpad" [17:39] since https://bugs.launchpad.net/ubuntu/+source/skype will continue to work [17:39] We still have maintainer address. [17:40] partner-packaging@canonical.com [17:41] there are many packages in partner which (now) each have different maintainers; creating a catch-all role address isn't going to make mailing the maintainer a more useful operation [17:41] any more than mailing ubuntu-devel about a package in universe is [17:43] * skaet holding off on clicking accept on the langpacks she's looked at already to not much up infinity's bulk one. [17:43] skaet: Oh, they've all been accepted for a while. [17:44] skaet: The bot just suppresses them for sanity. [17:44] infinity, weird, still working on the upload queue web page. [17:45] * skaet goes and forces a refresh [17:45] yeah, langpacks gone, but the other bits are gone now too.... [17:46] which other bits? [17:46] there are 12 packages in the queue [17:46] slangasek, no packages in the unapproved queue now... [17:46] there are [17:47] ok, have I entered the twilight zone? [17:47] Show: uploads with names like: [17:47] The Unapproved queue is empty. [17:47] https://launchpad.net/ubuntu/precise/+queue?queue_state=1 [17:47] is what I'm seeing... [17:47] shows 12 packages for me [17:48] yeah, that was from https://launchpad.net/ubuntu/precise/+queue?queue_state=1 [17:48] yes, I have entered the twilight zone. [17:48] cool [17:48] refreshed yet again and now 12 packages. [17:48] bring us back some pig people [17:48] will do. [18:06] Doing gnome-contacts [18:06] Also evolution-mapi [18:11] Thanks ScottK. === ChanServ changed the topic of #ubuntu-release to: Archive: frozen | http://pad.ubuntu.com/ubuntu-frozen-archive | Precise Pangolin Release Coordination. Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | we accept payment in cash, check or chocolate covered ants | melior malum quod cognoscis [19:06] skaet, I have a potential random corruption bug fix in bug 975356 for xorg-server [19:06] Launchpad bug 975356 in xorg-server "Logging from signal context is unsafe" [Medium,In progress] https://launchpad.net/bugs/975356 [19:06] we are building a test package in a ppa and will ask some people to test it out [19:06] but if all goes well I would like to get it in before final freeze [19:07] at this point, I'm just noting it for your reference [19:08] thanks cnd. getting rid of random corruptions would be good. want to avoid it landing with some things though. [19:10] so timing it in may be needed. [19:10] when fix is ready, start the conversation off, and we'll figure out the best spot. [19:28] ok [19:28] skaet: when you get a chance, can you help review the myth* packages in unapproved, specifically the ones that should help bring our ISO size down (mythbuntu-live-autostart, mythbuntu-meta, mythbuntu-default-settings)? was hoping to get at least those in for the next ISO spin to see if that's enough to get us back within limits. the others are less critical to be reviewed before next ISO spin [19:35] superm1, in a meeting, but will do it right after. [19:36] thanks! [19:42] * cjwatson turns bug 971735 into an FFe [19:42] Launchpad bug 971735 in golang "[FFe] Update golang to Go 1 in Precise" [Undecided,Confirmed] https://launchpad.net/bugs/971735 [20:00] * doko supports the FFe [20:01] it seems fairly no-brainer [20:04] (I'll have to wait a bit before I can actually use syncpackage on it - it's still in incoming) [20:32] * ScottK looks at python2.7. [20:41] doko: I accepted python2.7. It'd be nice if the next time the documentation in debian/changelog on the differences from Debian could be at least slightly more verbose. [20:43] ScottK, yeah, just forgot [20:43] OK. [20:44] there's still an opportunity to do this for the final release =) [20:45] doko must like buying skaet beer [20:46] I do. just approve the expenses ;-P [20:47] slangasek: We've had three failed to upload due to alleged bzip2 integrity errors, all on armhf. I have this sneaking suspicion it's not the packages that are broken. [20:47] Maybe someone could have a look? [20:48] ScottK: example? [20:48] https://launchpad.net/ubuntu/+source/unity-greeter/0.2.7-0ubuntu2/+build/3387899/+files/buildlog_ubuntu-precise-armhf.unity-greeter_0.2.7-0ubuntu2_CHROOTWAIT.txt.gz [20:48] https://launchpad.net/ubuntu/+source/unity-greeter/0.2.7-0ubuntu2/+build/3387899 [20:48] it's not the packages, and we've seen it before, but not debugged [20:48] OK. Just retry them then? [20:48] the solution is to get a webops to remove the chroot filecache and then retry [20:48] unfortunately I'm not sure there are any webops around over the Easter weekend ... [20:49] well [20:49] if you retry and manage to get a different builder, that would work too [20:49] are they all the same builder? I could disable the busted one. [20:50] They are all nasl [20:50] If you could do that, it would help. [20:51] I've disabled it [20:51] I think [20:51] oh damnit [20:51] ok, actually disabled now [20:52] OK. I was still preparing my ubuntu-build invocation. [20:52] Retrying now. [20:53] Somebody beat me on unity-greeter. I got the other two. [20:53] Thanks cjwatson. [20:55] cool [20:56] * cjwatson checks for more in the API [20:57] I see 148 ... [20:57] Ouch. [20:58] let me just sanity-check that [20:58] I was using http://qa.ubuntuwire.org/ftbfs/ which lags, so I probably just saw the first few. [20:58] broken builders can fail lots of builds very quickly [20:58] I'd like to check that they're all nasl; the API doesn't tell me the builder so I'll have to quickly screen-scrape I think [20:59] Probably many of those are from the rebuild. [20:59] I'm only checking in the rebuild [20:59] already checked the primary archive [20:59] ok [20:59] >>> archive = lp.load('https://api.launchpad.net/1.0/ubuntu/+archive/test-rebuild-20120328') [20:59] >>> cpp = archive.getBuildRecords(build_state='Chroot problem') [20:59] * cjwatson breaks out BeautifulSoup [21:03] cjwatson: The first retry succeeded, so definite progress. [21:06] * cjwatson waits for this to screen-scrape 148 LP pages ... [21:08] >>> [cp for cp in cpp if builder(cp) != 'nasl'] [21:08] [, ] [21:09] those two are different problems - hash sum mismatch on the archive, which is transient [21:09] so retrying the lot now [21:10] I'm glad I noticed it before you vanished for the night. [21:11] should all be kicked now [21:11] * cjwatson <3 the API [21:14] avoiding that screen-scraping is probably a matter of http://paste.ubuntu.com/918003/ plus tests [21:14] which I'll sort out at some more convenient time [21:15] Nice. [21:15] then it'd've been [cp for cp in cpp if cp.builder.name != 'nasl'] [21:22] superm1, have gone through the myth* ones, looking reasonable to me. approving now. [21:22] thanks skaet [21:46] ^^ flashplugin-nonfree fixes a major regression in this morning's upload; evidently there was a latent bug in the update-alternatives handling that didn't show up on upgrades (bug #975426), so I'd appreciate having that reviewed asap [21:46] Launchpad bug 975426 in flashplugin-nonfree "flashplugin-installer failed to install during system installation: no alternatives for mozilla-flashplugin." [High,Triaged] https://launchpad.net/bugs/975426 [21:55] oh wait, technically that's not frozen anyway [21:55] slangasek: I've been following... 11.2.202.228ubuntu1 / 11.2.202.228ubuntu3 the same release as I grabbed from http://get.adobe.com/flashplayer/?no_redirect and installed via Alien? [21:55] * slangasek self-accepts :P [21:56] phillw: I don't know [21:56] it probably is, but why would you use alien for this when it's packaged in multiverse+partner :) [21:57] slangasek: because I did not know it was & used https://help.ubuntu.com/community/RestrictedFormats [21:58] so, some modifcations are required if you have moved things :) [21:59] phillw: https://help.ubuntu.com/community/RestrictedFormats/Flash "install Flash by going to the Ubuntu Software Center"? [21:59] slangasek: my very little tiny voice... but https://help.ubuntu.com/community/RestrictedFormats is the better apge? [22:00] s/apge/page [22:00] phillw: the only mention I see of flash on there is a pointer to the subpage :) [22:01] slangasek: https://help.ubuntu.com/community/RestrictedFormats#Easy_Install [22:01] one click links :) [22:02] I still see no mention there of alien... [22:02]