[02:10] <slangasek> flocculant: cron fixed
[03:55] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Zesty Alpha 2] has been updated (20170130)
[03:55] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Zesty Alpha 2] has been updated (20170130)
[03:55] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop powerpc [Zesty Alpha 2] (20170130) has been added
[04:22] <jbicha> slangasek: I guess Zesty Alpha 2 needs to be marked as Released in the iso tracker to quiet the queuebot ^
[11:02] <acheronuk> Hi. Could someone please take a look at the new sources in the queue for KDE applications 16.12.1? thank you
[11:20] <ginggs> how does one mark a package so that its autopkgtests run on a 'big' host? Iirc,  p.itti may have done something like that for the julia package
[11:41] <apw> ginggs, that is a server side configuration, so you need to "ask" here
[11:43] <ginggs> apw: what is it called, and does it work for all architectures?
[11:44] <apw> ginggs, its part of the primary configuration for the autopkgtest builder hosts
[11:47] <ginggs> apw: so what do i need to ask for, and will it help on ppc64el, for example?
[11:49] <apw> i don't think it affects anything other than the virtual machine architectures
[11:49] <apw> but i would defer to Laney for more knowledge
[11:54] <flocculant> slangasek: ty :)
[12:02] <ginggs> apw: I think it was setting '--flavor m1.large' and I think it would have been for amd64, because julia's tests don't succeed anywhere else. Anyway, could we do this for python-hypothesis please?
[12:03] <apw> ginggs, that is the effect for scaling stack yes,but it is a mark of "huge" for the package as a whole
[12:15] <ginggs> apw: so can we mark python-hypothesis "huge" please?
[12:25] <apw> ginggs, will see what i can do
[12:25] <ginggs> apw: thanks!
[12:47] <fossfreedom_> jbicha: quick question - I saw you have a v0.22 in zesty proposed - in debian sid shotwell is v0.25 - I thought for zesty we should be syncing against sid/testing - why are we still at the rather elderly v0.22 series?
[12:53] <jbicha> fossfreedom_: see bug 1581180 particularly comment 2
[12:53] <ubot5> bug 1581180 in shotwell (Ubuntu) "Update to Shotwell 0.24.x" [Wishlist,Triaged] https://launchpad.net/bugs/1581180
[12:54] <jbicha> odd numbers are unstable releases so Debian should have stayed with 0.24 since Debian is freezing for release now
[12:55] <fossfreedom_> k - thanks for the feedback.  agreed - very much a blocker :(
[12:56] <fossfreedom_> the reason for the question - for Ubuntu Budgie we were going to drop GNOME Photos in favour for the new shotwell.  Guess we can't.
[13:01] <jbicha> the bug is available for anyone to work on; the important thing is to not regress Ubuntu Online Accounts support (or anything else)
[13:02] <jbicha> it was too challenging for me 6 months ago but I haven't looked at it recently
[13:15] <cpaelzer> FYI  I've seen multiple reverse dependencies tests breaking on the synced Debian DPDK - I'm working to get a fix to Debian and sync a newer one then
[14:00] <apw> ginggs, ok that should be in production (if i have done it right)
[14:05] <ginggs> apw: thanks, let me try kicking off a test - should know in about 45 minutes
[14:08] -queuebot:#ubuntu-release- New binary: libixion [ppc64el] (zesty-proposed/main) [0.12.2-1] (kubuntu, ubuntu-desktop)
[14:09] -queuebot:#ubuntu-release- New binary: libixion [i386] (zesty-proposed/main) [0.12.2-1] (kubuntu, ubuntu-desktop)
[14:10] -queuebot:#ubuntu-release- New binary: libixion [s390x] (zesty-proposed/main) [0.12.2-1] (kubuntu, ubuntu-desktop)
[14:10] -queuebot:#ubuntu-release- New binary: libixion [amd64] (zesty-proposed/main) [0.12.2-1] (kubuntu, ubuntu-desktop)
[14:11] -queuebot:#ubuntu-release- New binary: libixion [arm64] (zesty-proposed/main) [0.12.2-1] (kubuntu, ubuntu-desktop)
[14:11] -queuebot:#ubuntu-release- New binary: libixion [powerpc] (zesty-proposed/main) [0.12.2-1] (kubuntu, ubuntu-desktop)
[14:15] -queuebot:#ubuntu-release- New binary: libixion [armhf] (zesty-proposed/main) [0.12.2-1] (kubuntu, ubuntu-desktop)
[14:49] <elopio> join #ubuntu-devel
[14:54] -queuebot:#ubuntu-release- New: accepted libixion [amd64] (zesty-proposed) [0.12.2-1]
[14:54] -queuebot:#ubuntu-release- New: accepted libixion [armhf] (zesty-proposed) [0.12.2-1]
[14:54] -queuebot:#ubuntu-release- New: accepted libixion [powerpc] (zesty-proposed) [0.12.2-1]
[14:54] -queuebot:#ubuntu-release- New: accepted libixion [s390x] (zesty-proposed) [0.12.2-1]
[14:54] -queuebot:#ubuntu-release- New: accepted libixion [arm64] (zesty-proposed) [0.12.2-1]
[14:54] -queuebot:#ubuntu-release- New: accepted libixion [ppc64el] (zesty-proposed) [0.12.2-1]
[14:54] -queuebot:#ubuntu-release- New: accepted libixion [i386] (zesty-proposed) [0.12.2-1]
[14:54] -queuebot:#ubuntu-release- New: accepted u-boot-menu [amd64] (zesty-proposed) [1]
[14:57] <flocculant> do I have to?
[14:58] <LocutusOfBorg> apw, please remove the block proposed to ocaml stuff? it shouldn't be needed anymore, and maybe Debian will fix them
[15:00] <apw> LocutusOfBorg, gone
[15:01] <LocutusOfBorg> <3 ta!
[15:26] -queuebot:#ubuntu-release- New binary: liborcus [i386] (zesty-proposed/main) [0.12.1-1] (kubuntu, ubuntu-desktop)
[15:27] -queuebot:#ubuntu-release- New binary: liborcus [ppc64el] (zesty-proposed/main) [0.12.1-1] (kubuntu, ubuntu-desktop)
[15:28] -queuebot:#ubuntu-release- New binary: liborcus [amd64] (zesty-proposed/main) [0.12.1-1] (kubuntu, ubuntu-desktop)
[15:30] -queuebot:#ubuntu-release- New binary: liborcus [s390x] (zesty-proposed/main) [0.12.1-1] (kubuntu, ubuntu-desktop)
[15:31] -queuebot:#ubuntu-release- New binary: liborcus [powerpc] (zesty-proposed/main) [0.12.1-1] (kubuntu, ubuntu-desktop)
[15:32] <ginggs> apw: \o/ that worked, thanks!
[15:33] -queuebot:#ubuntu-release- New binary: liborcus [arm64] (zesty-proposed/main) [0.12.1-1] (kubuntu, ubuntu-desktop)
[15:33] -queuebot:#ubuntu-release- New binary: liborcus [armhf] (zesty-proposed/main) [0.12.1-1] (kubuntu, ubuntu-desktop)
[15:34] <apw> ginggs, good!
[15:36] -queuebot:#ubuntu-release- New: accepted liborcus [amd64] (zesty-proposed) [0.12.1-1]
[15:36] -queuebot:#ubuntu-release- New: accepted liborcus [armhf] (zesty-proposed) [0.12.1-1]
[15:36] -queuebot:#ubuntu-release- New: accepted liborcus [powerpc] (zesty-proposed) [0.12.1-1]
[15:36] -queuebot:#ubuntu-release- New: accepted liborcus [s390x] (zesty-proposed) [0.12.1-1]
[15:36] -queuebot:#ubuntu-release- New: accepted liborcus [arm64] (zesty-proposed) [0.12.1-1]
[15:36] -queuebot:#ubuntu-release- New: accepted liborcus [ppc64el] (zesty-proposed) [0.12.1-1]
[15:36] -queuebot:#ubuntu-release- New: accepted liborcus [i386] (zesty-proposed) [0.12.1-1]
[15:36] -queuebot:#ubuntu-release- New source: python-murano-pkg-check (zesty-proposed/primary) [0.2.0-0ubuntu1]
[15:38] <ogra_> infinity, http://cdimage.ubuntu.com/ubuntu-core/16/current/current/ misses .htacces it seems (i see FOOTER and HEASDER as files there)
[16:42] -queuebot:#ubuntu-release- New binary: gpgme1.0 [ppc64el] (zesty-proposed/main) [1.8.0-3ubuntu1] (core)
[16:42] -queuebot:#ubuntu-release- New binary: gpgme1.0 [amd64] (zesty-proposed/main) [1.8.0-3ubuntu1] (core)
[16:46] -queuebot:#ubuntu-release- New binary: gpgme1.0 [i386] (zesty-proposed/main) [1.8.0-3ubuntu1] (core)
[16:47] -queuebot:#ubuntu-release- New binary: gpgme1.0 [s390x] (zesty-proposed/main) [1.8.0-3ubuntu1] (core)
[17:52] <smoser> hi, can i get someone to release the cloud-init yakkety SRU ?
[17:52] <smoser> josvaz, ^
[18:10] <apw> smoser, looking
[18:19] <apw> smoser, done
[18:38] <smoser> apw, thank you.
[20:18] <infinity> ogra_: Who set that up?
[20:18] <ogra_> infinity, i thought that was you
[20:18] <ogra_> "foundations" :)
[20:18] <infinity> Certainly not me, maybe "us".
[20:18] <ogra_> slangasek, who set up http://cdimage.ubuntu.com/ubuntu-core/16/current/current/ ?
[20:19]  * ogra_ would also liek to know if there are any builds for the edge channel 
[20:19] <ogra_> *like
[20:20] <infinity> Anyhow, if it's published by the cdimage code, .htaccess is meant to be written automatically.  If that was slapped together by hand, or is an in-progress thing, patience?
[20:21] <ogra_> yeah, no hurry
[20:22] <slangasek> ogra_: current/current?  Do you mean stable/current?
[20:22] <slangasek> I set that up
[20:22] <ogra_> slangasek, just a copy/paste from my browser
[20:22] <slangasek> there are no edge channel builds currently; those will happen when automation is completed
[20:23] <ogra_> ah, k
[20:23] <ogra_> i dont really care about stable :)
[20:23] <slangasek> I... have no idea what has been done here
[20:23] <ogra_> (apart from release day)
[20:23] <slangasek> oh I see, stable was a symlink and I though it was a directory. fixing.
[20:23] <ogra_> well, all the dirs miss the hataccess in fact
[20:23] <ogra_> *htaccess
[20:24] <infinity> I prefer hat access.
[20:24] <ogra_> heh :)
[20:24] <slangasek> ogra_: 'current' is missing .htaccess because /that/ one was done by hand, back in November
[20:24] <slangasek> 'pending' has it
[20:25] <ogra_> well, looks all better now
[20:26] <ogra_> thx
[20:33] <acheronuk> Could someone please take a look at the new sources in the queue for KDE applications 16.12.1? thanks
[21:33] <acheronuk> can someone please also accept gpgme binaries please? these are now required for new KDE frameworks and applications, and without them we are sort of stuck!