[14:40] <lotuspsychje> !latest
[14:40] <lotuspsychje> any triggers for latest packages here?
[14:58] <LocutusOfBorg1> lotuspsychje, which package?
[14:59] <lotuspsychje> LocutusOfBorg1: we were looking for libsdl 2.0.4 before
[15:00] <LocutusOfBorg1> oh, what a coincidence
[15:00] <LocutusOfBorg1> http://lists.alioth.debian.org/pipermail/pkg-sdl-maintainers/2016-January/002272.html
[15:01] <LocutusOfBorg1> it should be fixed in debian before
[15:01] <lotuspsychje> mcphail: ^
[15:01] <LocutusOfBorg1> actually I did the work http://anonscm.debian.org/cgit/pkg-sdl/packages/libsdl2.git
[15:01] <LocutusOfBorg1> there is still two points to address, I hope my fellow Debian Maintainers will address them
[15:03] <mcphail> LocutusOfBorg1: lotuspsychje: does this mean 2.0.4 is likely to come to xenial? 2.0.2 doesn't work with Mir properly
[15:04] <LocutusOfBorg1> you can ping the other sdl maintainers on the mail I sent
[15:04] <LocutusOfBorg1> maybe this can speed up things
[15:04] <LocutusOfBorg1> I, for sure, won't upload it because just I have permissions, it needs a transition probably
[15:05] <LocutusOfBorg1> and changes are quite large
[15:06] <mcphail> LocutusOfBorg1: thanks. I'll keep poking. need to find out if all bschaefer's mir fixes have made it into upstream anyway
[15:07] <mcphail> Would be a shame if a functional SDL missed LTS release
[15:08] <LocutusOfBorg1> mcphail, the transition is quite large, so it needs to start ASAP
[15:09] <LocutusOfBorg1> mcphail, it isn't Debian or Ubuntu fault if upstream took 2 years to release 2.0.4 :)
[15:09] <lotuspsychje> LocutusOfBorg1: isnt there like a request url for packages?
[15:09] <LocutusOfBorg1> lotuspsychje, what does it mean?
[15:09] <mcphail> LocutusOfBorg1: ha!
[15:09] <LocutusOfBorg1> no, there is a mail list, just ping it
[15:09] <lotuspsychje> LocutusOfBorg1: well like mcphail here suggest sdl to be added
[15:10] <LocutusOfBorg1> I imported on git as soon as it has been released (a few hours later)
[15:10] <LocutusOfBorg1> now I need to have someone on pkg-sdl team to upload
[15:10]  * LocutusOfBorg1 can upload it, but it needs coordination from -release team
[15:10] <lotuspsychje> LocutusOfBorg1: so if someone wants a package added==mailinglist mail?.
[15:12] <LocutusOfBorg1> there is already a debian open bug
[15:12] <LocutusOfBorg1> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788688
[15:31] <cjwatson> LocutusOfBorg1: please don't start an SDL transition until perl 5.22 is out of the way
[15:32] <cjwatson> oh autopkgtest, y u take forever
[16:03] <LocutusOfBorg1> cjwatson, it won't start for at least a week, and according to what you said on -devel the perl should be done in a few hours :)
[16:03] <cjwatson> LocutusOfBorg1: I'm certainly hoping so
[16:09] <LocutusOfBorg1> I hope with you :)
[16:09] <LocutusOfBorg1> BTW how can I help in vpx transition? it should be already started, and preventing virtualbox from migrate
[16:10] <LocutusOfBorg1> do you have any single command for issuing rebuilds? I would like to avoid dget dch dpkg-buildpackage dput
[16:18] <cjwatson> it'll be a lot less impossible to see what's going on with libvpx (and mostly everything else) once perl lands
[16:18] <LocutusOfBorg1> yes, of course
[16:18] <LocutusOfBorg1> I'm finding difficult to understand the log too
[16:19] <cjwatson> http://irclogs.ubuntu.com/2015/12/22/%23ubuntu-release.html#t14:10
[16:19] <LocutusOfBorg1> btw can somebody please accept hedgewars/*-backports?
[16:19] <cjwatson> rebuild stuff
[16:19] <LocutusOfBorg1> yes, I remember that log, but I don't keep logs on my pc, thanks
[16:19] <cjwatson> you might have noticed that at the time but you were busy nitpicking about binNMUs ;-)
[16:20] <LocutusOfBorg1> the problem is that I don't know an easy way to keep logs and find them ;)
[16:21] <cjwatson> dunno how to do it in hexchat.  I configured irssi autolog years ago ...
[16:22] <cjwatson> I also have http://paste.ubuntu.com/14421429/ as ~/bin/grep-ubuntu-irclogs, which is slow but functional in cases where it's for a channel I'm not routinely in
[16:22] <cjwatson> (also makes quite a lot of requests ...)
[16:23] <LocutusOfBorg1> lol wonderful!
[17:57] <LocutusOfBorg1> cjwatson, http://paste.ubuntu.com/14422449/
[17:57] <LocutusOfBorg1> what do you think about?
[17:58] <LocutusOfBorg1> it should avoid the "codename release" issue, and avoid to hardcode the reason for the rebuild
[17:58] <LocutusOfBorg1> I think I'll use this one
[18:02] <xnox> cjwatson, well done =)
[18:02] <xnox> i see perl migrating.
[19:54] <mapreri> LocutusOfBorg1:         dch -R 'Rebuild for new '$2'.'
[19:54] <mapreri>         sed s/UNRELEASED/$RELEASE/ -i debian/changelog
[19:54] <mapreri> use `dch -D` instead of the sedding?
[20:27] <slangasek> arges: hi, so I wonder about the self-accept etc. on bug #1513227, given that bug #1511347 was filed first :)
[20:41] <slangasek> arges: also seems to include changes (multi-arch) with no SRU bug or justification...
[20:44] <slangasek> ah, I guess that piece goes hand-in-hand with the Architecture change
[20:52] <LocutusOfBorg1> mapreri, seems legit
[21:20] <arges> slangasek: the multi-arch change should have been explained better in the previous bug. So will including the patches from ibm fix it for ppc64el?
[21:21] <slangasek> arges: that's my understanding, yes
[21:21] <slangasek> arges: I'd assigned the bug to me, I'm happy to follow through with a 1.3 upload; or do you want to do it?
[21:22] <arges> slangasek: I won't get to it today, so if you have time go ahead. otherwise i can put on my list for later this week
[21:22] <slangasek> arges: ok I'll probably do it this afternoon then
[22:50] <LocutusOfBorg1> mapreri, http://paste.ubuntu.com/14424960/
[22:50] <LocutusOfBorg1> :)
[23:53] <cjwatson> LocutusOfBorg1: I'm not taking patches to my ad-hoc stuff; if you want to run something a bit different then be my guest
[23:54] <cjwatson> LocutusOfBorg1: but you don't need to tell me about it, nor do I really want to know :)