=== jbicha is now known as Guest1332
micahgBTW, the rest of the tntnet binaries will be coming through shortly06:46
micahgpitti: could I ask you to process the promotion requests in the ubuntu-archive queue as well please?06:49
micahgmultiverse -> universe ones I mean06:49
=== yofel_ is now known as yofel
pittimicahg: done06:59
micahgpitti: thanks06:59
RAOFAnother gtk+3.0? :/10:08
seb128RAOF, there was a regression in the previous one10:09
cjwatsonprecise daily CD builds should be up and running again now, though the first ones haven't run yet14:02
* ogra_ crosses fingers for arms14:14
=== bjf[swapped] is now known as bjf
bjfskaet, pitti, can someone copy the Precise kernel package (3.2.0-24.38) from -proposed to -updates?14:44
skaetbjf, hmm... looks like someones just taken care of it.14:48
pittibjf: done14:48
bjfpitti, thanks14:49
pitti(ubuntu-docs shouldn't go to -security, rejecting that)14:51
cjwatsonI have moved the sync-blacklist to lp:~ubuntu-archive/+junk/sync-blacklist; please stop using the old location (which I'm going to render inoperative)17:42
* micahg assumes that includes fixing syncpackage and/or launchpad to check the new location as well?17:43
cjwatsonNo, because they already used http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt17:44
cjwatsonLaunchpad itself hasn't cared for some months17:44
cjwatsonThe only clients are syncpackage and auto-sync, both client-side17:45
micahgsorry, ignore me :)17:45
bdmurrayis this the right channel to talk about the SRU-ability of a bug for Precise?21:22
infinityAlmost certainly.21:25
bdmurrayI want to SRU this change to Precise but I'm not excited about writing a test case21:25
bdmurrayhonestly, I'm not sure how to get a .deb to generate that message21:25
slangasekhmm, quite21:26
bdmurrayand this seems like an 'obviously safe patch' to me21:27
slangasekobviously safe, yes, but we also want to be sure it fixes the bug21:29
bdmurrayah true21:29
slangasekbdmurray: how about dpkg-divert --add --local --rename --divert /usr/bin/dpkg.real /usr/bin/dpkg, and then a wrapper script that deliberately clobbers any files in /var/cache/apt/archives with bogus data?21:30
infinityIf you're diverting dpkg, you can just replace it with something that throws the error every time it's run...21:31
infinityMangling data seems a bit silly at that point.21:31
bdmurrayThe foundations bug bot takes care of these after reporting and I only see 24 tagged not-debian-format so maybe its not worth it21:32
slangasekmaybe something like this: http://paste.ubuntu.com/999824/21:33
slangasekinfinity: this bug is tied up with whether strings are localized or not21:33
slangasekinfinity: so I think it's easier to do a wrapper script than to correctly emulate dpkg behavior21:34
slangasek(I'm not even sure which fd the message is output on...)21:34
slangasek$ sudo dpkg -i /var/cache/apt/archives/postfix_2.9.1-5_amd64.deb21:34
slangasekdpkg-deb: error: `/var/cache/apt/archives/postfix_2.9.1-5_amd64.deb' is not a debian format archive21:34
slangasekdpkg: error processing /var/cache/apt/archives/postfix_2.9.1-5_amd64.deb (--install):21:34
slangasek subprocess dpkg-deb --control returned error exit status 221:34
slangasekErrors were encountered while processing:21:34
slangasek /var/cache/apt/archives/postfix_2.9.1-5_amd64.deb21:34
slangasekbdmurray: ^^ tested21:35
jdstrandcjwatson: fyi, I started adding comments to the end of the commands I have been running on cocoplum so that 'history' will show why I am doing things21:35
jdstrandcjwatson: (referencing your eliminating shell access on cocoplum work items here)21:36
bdmurrayslangasek: okay, noted I'll open a bug with the test case and precise task but may wait for more bugs before causing the SRU work21:38
slangasekbdmurray: sounds good21:38
cjwatsonjdstrand: OK, but maybe best just edit the wiki page directly if you do something not mentioned there; I'm probably not going to trawl the history again :)21:39
jdstrandwell, it was more about "why did he do that?" if someone was looking there. I will update the wiki as needed21:40
cjwatsonLaney: your update-sources problems were a MoM bug - 'def open' at the top level of a module is liable to produce abject confusion ...21:50
Laneyhrm, how did it ever work then?21:51
cjwatsonIt used to use file()21:51
cjwatsonI changed it some time ago (since file() no longer works in Python 3), but either an older version of Python resolved local definition vs. builtin differently, or I didn't deploy that change until after MoM stopped working for other reasons21:52
cjwatsonOoh, this new box has twice the disk too21:53
cjwatsonAnd a honkload of CPUs21:53
lamontslangasek: what have you done!?!?22:15
slangaseklamont: mm?22:21
jdstrandfyi, my team has also been seeing oddities with the work items tracker22:26
slangaseklamont: I have done many things... care to be more specific? :)22:26
lamontslangasek: the postfix dpkg -i highlighted me, that's all.22:26
slangasekoh, haha22:26
slangaseklamont: I replaced dpkg with a very malicious shell script22:26
jdstrandpeople haven't been able to delete things from 'security-q-ecryptfs' and things are reordered after save ('security-q-apparmor-dev')22:26
lamontslangasek: ah, yes, I can see that now.22:27
jdstrandto delete, when I went to edit, I copied all the work items somewhere (I used gnote), and then deleted everything from the work items, saved it, then added them all back minus the one I deleted22:27
jdstrands/I deleted/I wanted deleted/22:28
slangasekskaet: do you know who it was that worked on the WI implementation in launchpad?22:29
jdstrandI will probably be copying things somewhere else for a little while22:29

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