=== salem_ is now known as _salem
[00:47] <barry> doko: ack, thanks.  the evidence mounts against the python change
[00:54] <ScottK> barry: how's it looking for a quick resolution upstream?
[01:09] <barry> ScottK: fairly good i think.  i'll do a few more tests locally but unless serhiy objects, i'm just going to back out that change for 3.5.2 then prep a patch for doko
[01:09] <barry> probably monday
[01:09] <ScottK> Cool.
[01:10] <doko> still need something for #809079, but I'm lost how to reproduce this
[01:10] <ScottK> barry: I think the same thing was committed for 3.4 and 2.7 too (just not released yet).  Those'll need fixing too.
[01:11] <doko> we don't care about 3.4 anymore
[01:12] <ScottK> Upstream does.
[01:14] <barry> ScottK: right.  and i want to back it out of the 3.6 branch too
[02:03] <psusi> is the sponsor queue really behind?  bug #1250109 has been waiting for a sponsor to apply the patch for a month now
[02:03] <ubottu> bug 1250109 in linux (Ubuntu) "Please use dpkg-triggers" [Wishlist,Triaged] https://launchpad.net/bugs/1250109
[02:05] <psusi> I wonder if it is because it is marked as assigned to apw?
[02:06] <sarnold> heh just the other day I waited through a few of those update-grubs and wondered how this fix was going :)
[02:07] <psusi> been waiting for either a sponsor to upload, or me to finally get upgraded to core-devel ;)
[02:07] <sarnold> hehehe
[02:07] <psusi> missed the meeting due to new baby and no sponsors yet, so if you care to sponsor: https://wiki.ubuntu.com/PhillipSusi/DeveloperApplication2
[02:07] <psusi> ;)
[02:07] <sarnold> psusi: I suspect whoever would patch-pilot this would want to know better what kinds of testing you've done with it --
[02:07] <sarnold> congrats :)
[02:08] <psusi> thanks
[02:08] <sarnold> psusi: -- so if you could add to it which kinds of dist-upgrades, apt-get purges, dpkg --purge, mixed purge and install, etc. you've done with it, that'd probably ehlp grow confidence in the patch
[02:08] <psusi> it was a fairly straight forward stealing of the code from update-initramfs, and I tested it by removing a few older kernels and seeing that it only did an update once... then installing one new kernel and seeing that it also runs one update
=== Saviq_ is now known as Saviq
=== jincreator_ is now known as jincreator
[10:32] <doko> xnox, changed maintainer address: https://packages.qa.debian.org/libo/libopenobex.html
[15:29] <mapreri> can somebody try another run of pbuilder's autopkgtest on s390x ?
[16:17] <jamespage> doko, hey - just so I don't forget next week - I think I've done all the right bits to get fop demoted to universe, however its not showing up on the component mismatches report
[16:17] <jamespage> I can't find it in a seed - the only thing still showing is an alternative Recommends on xmlto - would that cause that?
[16:52] <cjwatson> mapreri: done
[16:54] <cjwatson> jamespage: no, it wouldn't; the reason it's not showing is that xmlstarlet is scheduled for promotion to main and build-depends on fop
[16:57] <cjwatson> mapreri: (in theory.  doesn't seem to have done anything - maybe ask again when pitti's around if it doesn't happen eventually)
[17:25] <mapreri> cjwatson: ok, i'll poke pitti.  "unfortunately" pbuilder has very few deps, so it's not triggered that often...
[21:41] <dobey> pitti: hey, if you happen to see this anytime, can you please re-run the amd64 autopkgtest for unity-scope-click? thanks.