[05:44] <robru> stgraber: thanks for merging!
[09:56] <xnox> lsb went from arch:any -> arch:all could it please be "decrufted"? It's currently stuck in britney saying "old binaries left on <arch:any>"
[12:15] <cjwatson> xnox: Hmmmm.  I think that's likely a bug in britney.py:merge_binaries (the partial suite handling is very very very delicate and there are some corner cases).  I don't think it can be decrufted at the moment - the best approach is to get a member of ~ubuntu-release to force it
[12:44] <xnox> cjwatson, right. would removing arch:any binaries from -release make things better? there are no rdepends on them.
[12:45] <xnox> cjwatson, where is britney code? surely it can inspect source package and notice any->all change.
[12:47] <cjwatson> xnox: it's not that simple (tm)
[12:47] <cjwatson> lp:~ubuntu-release/britney/britney2-ubuntu
[12:47] <cjwatson> xnox: oh, if there are no rdepends, that would probably work around it, yes, although horrible
[12:47] <cjwatson> one sec
[12:49] <xnox> (there are no rdepends on the arch:any packages, all of which are dropped)
[12:49] <cjwatson> xnox: OK, removed
[13:49] <xnox> cjwatson, thanks that did the trick and triggered a world of tests =)
[13:53] <cjwatson> It did indeed
[14:45] <xnox> no powerpc builds for today? =(
[15:59] <lamont> where would I go to find out why https://launchpad.net/ubuntu/+source/python-django/1.8.5-2ubuntu1 is still sitting in xenial-proposed, instead of actually making it into xenial?
[16:01] <rbasak> lamont: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html in the first instance.
[16:01] <rbasak> lamont: that looks OK, so
[16:02] <rbasak> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
[16:02] <rbasak> lamont: that says that the update would make     * amd64: mumble-django, python-django-mumble uninstallable.
[16:02] <rbasak> lamont: documentation for the future at https://wiki.ubuntu.com/ProposedMigration but that's the answer to your specific case
[16:06] <lamont> rbasak: thanks for both versions of the answer!
[16:11] <rbasak> You're welcome!
[16:34] <roaksoax> barry: so we have python-django1.8 in -proposed, blocked on a package in universe that depends on python-django << 1.8. It seems unmaintained upstream, but seems to support 1.7... what should we done in that case ?
[16:37] <barry> roaksoax: which package is that?
[16:37] <roaksoax> barry: mumble-django
[16:37] <roaksoax> that's the source
[16:37] <roaksoax> python-django-mumble
[16:37] <rbasak> Looks like mumble-django was kicked out of testing in Debian 415 days ago
[16:38] <roaksoax> https://bitbucket.org/Svedrin/mumble-django/src/ed55b15dd108acc2cb01102d0f7630a9fd676b4a?at=default -> last commit seems to only have added support to django 1.7
[16:38] <roaksoax> in 2014
[16:38] <roaksoax> other than that seems pretty much unmaintained
[16:39] <barry> rbasak: so i guess we should kick it out of ubuntu too then
[16:39] <rbasak> I agree but I presume that the release team needs to make the call?
[16:40] <barry> http://permalink.gmane.org/gmane.linux.debian.packages.voip.devel/25584
[16:40] <barry> was it that long ago?
[16:40] <rbasak> https://packages.qa.debian.org/m/mumble-django.html was what I was using
[16:41] <rbasak> Does the removed from testing email autoamtically repeat?
[16:41] <barry> oh, looks like it does
[16:41] <barry> it keeps trying to migrate to testing
[16:41] <rbasak> Oh, it kept migrating to testing
[16:41] <rbasak> And being kicked out
[16:41] <barry> yeah
[16:41] <rbasak> Which seems odd
[16:41] <rbasak> But whichever way, it doesn't look like it's being looked after in Debian
[16:43] <barry> right, so i guess ubuntu-release does need to kick it out.  maybe file a bug on the srcpkg in ubuntu?
[16:43] <rbasak> It'd probably be polite to file a bug upstream asking for Django 1.8 support as I don't see one.
[16:43] <barry> that too
[17:11] <roaksoax> barry: but in the menatime, I'm happy to file a bug to remove that package
[17:11] <barry> roaksoax: thanks