[00:01] Could you take this to #ubuntu-bugs or similar, please? [00:01] pastebin.com/iNEUgVES [00:03] cjwatson: certainly, I just asked here in case one of you could give me what to bug report it against. My apologies. :( [00:57] cjwatson: xnox - my apologies.. old /home + new install = reset ~/.Xauthority, in my feeble defence, been 18 months since I was last bitten by that little critter. [02:39] doko_: ^^^ That'll work with 3.2/3.3, so it should get in. === bencer is now known as heidita2 === heidita2 is now known as bencer === doko_ is now known as doko [09:03] The md5sum for the latest quantal-desktop-amd64 (20121017.5 i think) does not match that is listed in cdimage.u.c. Would someone be able to have a look please? [09:06] psivaa: It matches on cdimage. [09:07] can someone reject the old seahorse from quantal-proposed/unapproved please? [09:07] just in case [09:07] Laney: done [09:08] merci buckets [09:12] cjwatson: it does indeed, not sure why our tests report they dont match. i'll have a look thanks === quadrispro_ is now known as quadrispro === henrix_ is now known as henrix === henrix_ is now known as henrix [10:31] * cjwatson finishes his first pass at a "redirect-release-uploads" LP branch [10:31] (though also waiting for the DB branch to be reviewed and deployed) [10:32] Hrm. Methinks we missed the "create raring in the partner archive" step. [10:32] Or, so apt tells me. [10:33] infinity: So, well [10:33] "Verify that the partner repository has been created on archive.canonical.com as a result of this process; if not, notify the Soyuz developers to fix it and check that this happens." [10:33] infinity: That got screwed by setting raring to frozen early [10:33] Ahh, that was one of the fallout issues from my oops? [10:34] infinity: I tried running publish-distro -A manually, and it republished a load of old series [10:34] infinity: so I screamed and reverted to a backup [10:34] infinity: I think the easiest way to fix this is likely to publish something irrelevant to raring/partner and then delete it [10:34] Or something relevant. [10:35] infinity: Just to force the publisher to do something (you might need to hold off on the deletion until after a publisher run) [10:35] I could just push vmware-view-client with a raring version. [10:35] infinity: If you have something, sure :) [10:35] Yeah, I'll just do that. [10:37] Hrm. The painful decision between "working from the hotel to avoid distraction" and "going into the office to have bandwidth" really becomes apparent when I download massive sources. [10:37] * infinity turns the hand crank. [10:43] Ahh, but welcome to the bizzaro world of hotel networks, where my upstream is 10 times better than my downstream. === Ursinha is now known as Ursinha-afk [10:56] * infinity blinks at the /etc/os-release conffile prompt. [10:56] We *just* added that file in Q, how could we have messed it up already? :P [10:57] Oh, feh. It wasn't a conffile in doko's upload. [10:57] So this needs migration magic. === henrix_ is now known as henrix [11:03] 6 [11:04] Yes. Six. [11:14] infinity, https://launchpadlibrarian.net/120762889/buildlog_ubuntu-raring-armhf.python-pylibacl_0.5.1-1.1build1_CHROOTWAIT.txt.gz ? [11:17] doko: What machine was that on? [11:17] Erm. Where did these new buildds come from? [11:18] infinity, bukavac, alfirk, diphda [11:18] Yeah, those all use to be "virtual". [11:18] And they're misconfigured. [11:18] Hunting down. [11:32] cjwatson: partner fixed. [11:36] So it is. Great, thanks. [11:37] Though raring seems to have fewer pockets than quantal does on archive.c.c. Probably correctly, though ... [11:37] Series initialisation is confusing. [11:37] infinity: Any objections if I nuke r-series* from there? [11:38] cjwatson: Nope, I was just noticing that hilarity myself. [11:38] cjwatson: And the pocket thing is weird, since partner shouldn't have pockets AT ALL. [11:38] Done. [11:38] Yeah, I know. [11:38] cjwatson: Which means either someone fixed it, or it's accidentally doing it correctly now, and that's worrisome. :P [11:39] The accident is probably because only raring/partner was dirty. [11:39] cjwatson: But the others never should be. [11:39] If not for your oops, I'm pretty sure we'd have the unnecessarily full set. [11:39] cjwatson: So, maybe they're just cruft from IFP, and haven't been touched since... [11:39] Yeah, but series init doesn't rely on dirtiness [11:40] (And should all go away) [11:40] I doubt it's as simple as IFP; I suspect the fresh-series logic in the publisher is wrong. [11:40] Possibly that too. [11:40] I'm still all for nuking the other pockets. [11:40] After a quick verification that all the Packages files are empty, which they'd effin' better be. [11:40] Pockets are so hardcoded that I suspect IFP has nothing to do with them. [11:41] Any objections to such a tidy? [11:41] I don't object, but best talk to LP folks first, and it would probably be a good idea to fix the publisher so that they don't come back next time. [11:42] Well, let's see if they're all empty first. [11:46] Right, so, tons of 0-length files, as I'd assumed. And all with timestamps of Apr 26, 16:15. Was that the last IFP? [11:47] And going all the way back to breezy, which seems somewhat excessive. [11:48] First publisher run after the IFP of quantal, but yes. [11:48] Yeah, that's what I meant, but I'm a lazy typist. :P [11:48] Might have been the first time we relied on the new fresh-series logic. [11:48] Could be, since I don't remember partner being this... populous. [11:48] * cjwatson goes to remedy critical lack-of-coffee error. [11:48] Though, if it's taken 6 months to notice, I'm obviously not that observant. [11:54] feceti/win 47 [11:54] Err. [11:54] My IRC client is revolting. [11:58] is the publisher currently running? [11:59] doko: As in, right this second, or in general? [12:00] doko: It just finished running 4 minutes ago, and will run again in 3. [12:00] in general, don't see updates, like the python3-tz promotion to main [12:02] ok, did use the de archive mirror at release time, now switched back === Ursinha-afk is now known as Ursinha === yofel_ is now known as yofel [13:40] doko: apparmor ^^^ =) [14:33] * cjwatson resolves conflicts in the transition tracker config; whoops [14:33] the horror [14:35] lsdiff !$ [14:35] oops [14:59] * cjwatson unbreaks promote-to-release and tells britney to copy debootstrap for real [15:18] cjwatson: the second email is "funny" and "confusing" =)))) it's addressed to me and my "sponsor" (cjwatson+ubuntu-archive-robot@...) and attached changes file has "Sorry, changesfile not available." [15:18] and there is no indication where to the package moved. [15:19] Yeah, I know [15:19] bug 1069862 for the first part [15:19] Launchpad bug 1069862 in Launchpad itself "Need some way to copy without the copier ending up in From:" [Low,Triaged] https://launchpad.net/bugs/1069862 [15:20] Feel free to file a bug about the second part [15:20] At the moment I'm just trying to make the whole thing work at all; prettiness is for the next iteration [15:22] Hmm, neither debootstrap nor apparmor appeared on raring-changes [15:22] Wonder why [15:22] cjwatson: hmm... if it's a copy, then it's a known issue that there are no changes files available. [15:22] same as for syncs, there are no changes files. [15:22] Sure, but it could synthesise the changes [15:23] They're in the database somewhere, after all [15:23] No reason LP has to expose *every* detail of its internal DB layout :-) [15:23] I asked for this when we first started doing API copies (for ubuntu-upload-history) [15:23] someone, I forget who, argued that it was a bad idea [15:24] Meh. Dig that up and I'll pay attention to it if the argument is reasonable, otherwise I'll ignore it :) [15:26] (But, if nothing else, why include an attachment at all if it's only going to say "nee-ner you can't have it"?) [15:30] python-apt failed to build on armel for the third time, given back now. (with different errors) [15:30] failed to find it [15:30] * Laney moves on with life [15:31] doko: with a error that makes sense? [15:31] mvo, unreproducible GCC ICE [15:31] doko: ok [15:31] the other one was a hang in the test suite [15:32] mod-wsgi is not public module - but plugins, but still fixed to build in raring. [16:11] dpkcd ~/ [16:11] * xnox clearly didn't have focus where I thought it was [16:22] hi, I was wondering if there's some sort of mirror redirector link that automatically redirects the user to his/her nearest iso mirror [16:22] like how ubuntu does [16:22] but I want it for Kubuntu [16:23] ubuntu.com uses the list of mirrors from Launchpad, though flavours aren't on releases.ubuntu.com so there's no such list for cdimage mirrors (and not that many mirrors I believe) [16:30] pyzmq/i386 ftbfs on the buildd, succeeds locally === Ursinha-afk is now known as Ursinha === henrix is now known as henrix_ === Ursinha-afk is now known as Ursinha [18:51] For 13.04 I'll be re-organizing the Edubuntu DVD image a tiny bit by moving all our squashfs files under casper/ (we'll ship three of them in 13.04). To achieve that, I need to move our current ltsp squashfs to the new location without breaking 12.04 as we're doing LTS releases. [18:51] I came up with http://paste.ubuntu.com/1300855/ which should do the trick, but I'm happy to hear about less hackish solutions [18:55] stgraber: looks fine, though my personal tendency is to leave such guards in place permanently by way of a kind of documentation [18:56] cjwatson: ok. I'll drop the FIXME and just make it a standard comment saying that as of 13.04 we're moving all the squashfses into casper/ [20:01] stgraber: re mirrors, drat [20:01] IIRC there was a redirector sometime ago, but maybe that expired [20:01] well, kubuntu used to be on releases.ubuntu.com but that changed fairly recently [20:02] ah, I guess that makes sense then ... [20:03] ( move was most likely due to us moving to a community maintained flavor ) [20:04] yeah, that and pretty limited disk space on the releases mirrors [20:06] righto, its just that someone mirroring Kubuntu ISO's wanted to know why Kubuntu did not do mirror redirects === Ursinha is now known as Ursinha-afk [22:07] Please accept psycopg2 and python-cups into raring-proposed [22:07] doko ^ =)))) [22:10] xnox: Hahaha. <3 for the bash-completion fix. Did you forward that to Debian? [22:11] infinity: =))))) Yeah I got pissed at hitting tab and diverted my anger into upload...... [22:12] infinity: yeah I could. I need to forward a few patches from todays uploads. [22:12] Oh, indeed. [22:12] +Forwarded: not yet [22:13] I'm not sure "not yet" is one of the documented states for that field, but I like it. [22:13] "Forwarded: I'll get to it, stop nagging." [22:13] that's the documented state? [22:14] The documented states are "no", "yes", and "not needed", I believe. :P [22:14] But I like "not yet". [22:14] I'd also accept "maybe, depends on your temporal view". [22:14] I submitted a branch into lp:session-indicator it got "approved" but jenkins ci rejected it because merge proposal did not have commit message set in lp.net metadata..... wtf =) [22:14] what about "workforce welcome" [22:16] knome: no, worforce is not welcome in this case =) [22:16] :) [22:48] cjwatson, am I allowed to copy xnox's python related uploads from raring-proposed to raring? [22:49] doko: in part, I am being a tester for cjwatson's britney runs =) [22:49] he did a few today. [22:49] xnox, ohh, nice, so please test =) [22:51] infinity: I've done the verification of bug 1070542 depending on how you feel about waiving the aging period [22:51] Launchpad bug 1070542 in apport-symptoms (Ubuntu Precise) "not possible to use ubuntu-bug ubuntu-release-upgrader-core on precise" [High,Fix committed] https://launchpad.net/bugs/1070542 [22:53] doko: join in on the spam^W fun and upload to -proposed =) [22:54] bdmurray: Yeah, done. It's not like upgrader things get "tested" in any meaningful way by aging in proposed anyway.