[00:00] <slangasek> xnox: but yes, that would definitely match what we're seeing, with armhf-only failure
[00:20] <xnox> slangasek, because lxd is better and has better apparmor containment and strong defaults
[00:20] <xnox> lxc1 containments have not been strengthned lately by default; the way lxd is.
[00:21] <xnox> i think s390x went with lxc1 as there were no lxd at the time; and maybe no lxd images.
[00:21] <xnox> but pitti did manage to use lxc1 already with handcrafted tarballs.
[00:21] <slangasek> xnox: right, the last bit is what I was trying to understand; I understand the reasons /not/ to let things in containers call mknod :)
[00:21] <xnox> slangasek, what is the status of the new scalingstack in boston to move s390x to the cloud?!
[00:21] <slangasek> great question
[00:21] <slangasek> wgrant:
[00:21] <wgrant> No progress, as far as I know.
[00:22] <wgrant> (also I highlight on scalingstack, so I was already here :P)
[00:22] <slangasek> hahaha
[00:22] <xnox> i highlight on s390x
[01:05] <handsome_feng> Hi, Could someone in Ubuntu Archive Admin team help to approve those UKUI packages? The final beta is coming soon, and we are waiting for this to do the next step, Thank you in advance ! bug: #1663477
[02:46] -queuebot:#ubuntu-release- Unapproved: steam (yakkety-proposed/multiverse) [1:<IP_ADDRESS>-5ubuntu1 => 1:<IP_ADDRESS>-5ubuntu2] (no packageset)
[02:58] <infinity> scalingstack: We need to talk about ppc removal Really Soon Now.
[02:59] <wgrant> infinity: Hah
[02:59] <wgrant> infinity: It's all ready for LP to nuke it, right?
[03:00] <infinity> wgrant: If anything on our end blows up as a result, we're prepared to fix it, so sure.  Though, I think having me around when you do it might not hurt.
[03:00] <infinity> (That said, you have access to ubuntu-archive@snakefruit, I believe)
[03:00] <infinity> Or maybe you don't.
[03:01] <infinity> But you could in a jiffy.
[03:03] <infinity> wgrant: But yes, I think the next steps are "purge it with fire from zesty", "wait for garbage collection (or force early expiry and collection)", "manually tidy up dists", and interlaced in there "fix anything that breaks on snakefruit as it explodes". :P
[03:04] <wgrant> infinity: I've never had snakefruit or pepo access.
[03:05] <infinity> wgrant: Yeah, I realised that after I said it.
[03:05] <infinity> wgrant: You meet the criteria to be in the UNIX group, if we decided that would be a good thing.
[03:05] <wgrant> I do, it might be handy.
[03:05] <infinity> (But I also like the precedent of not adding more people to a group where >0 members is already too many)
[03:05] <wgrant> Quite.
[03:10] <infinity> Hrm.  Why does sudo -l not have a flag to tell my WHY.
[03:37] -queuebot:#ubuntu-release- Unapproved: steam (trusty-proposed/multiverse) [1:<IP_ADDRESS>-1ubuntu1.1 => 1:<IP_ADDRESS>-1ubuntu1.2] (no packageset)
[03:43] -queuebot:#ubuntu-release- Unapproved: steam (xenial-proposed/multiverse) [1:<IP_ADDRESS>-1ubuntu3 => 1:<IP_ADDRESS>-1ubuntu4] (no packageset)
[05:50] -queuebot:#ubuntu-release- New binary: gcc-6-cross-ports [i386] (zesty-proposed/main) [17ubuntu1] (ubuntu-desktop)
[07:39] -queuebot:#ubuntu-release- New binary: golang-github-grpc-ecosystem-go-grpc-prometheus [amd64] (zesty-proposed/universe) [1.1+git20160910.0.6b7015e-1] (no packageset)
[07:40] -queuebot:#ubuntu-release- New binary: golang-github-grpc-ecosystem-grpc-gateway [amd64] (zesty-proposed/universe) [1.1.0+git20170127.54.6863684-1] (no packageset)
[08:08] <handsome_feng>  Hi, Could someone in Ubuntu Archive Admin team help to approve those UKUI packages? The final beta is coming soon, and we are waiting for this to do the next step, Thank you in advance ! bug: #1663477
[08:09] -queuebot:#ubuntu-release- New binary: rclone [amd64] (zesty-proposed/universe) [1.35-1] (no packageset)
[08:09] -queuebot:#ubuntu-release- New binary: rclone [s390x] (zesty-proposed/universe) [1.35-1] (no packageset)
[08:09] -queuebot:#ubuntu-release- New binary: rclone [ppc64el] (zesty-proposed/universe) [1.35-1] (no packageset)
[08:10] -queuebot:#ubuntu-release- New binary: rclone [i386] (zesty-proposed/universe) [1.35-1] (no packageset)
[08:11] -queuebot:#ubuntu-release- New binary: rclone [arm64] (zesty-proposed/universe) [1.35-1] (no packageset)
[08:12] -queuebot:#ubuntu-release- New binary: rclone [armhf] (zesty-proposed/universe) [1.35-1] (no packageset)
[08:34] -queuebot:#ubuntu-release- New binary: abci [amd64] (zesty-proposed/universe) [0.0~git20170124.0.f94ae5e-2] (no packageset)
[08:34] -queuebot:#ubuntu-release- New binary: golang-github-rsc-letsencrypt [amd64] (zesty-proposed/universe) [0.0~git20160929.0.76104d2-2] (no packageset)
[08:35] -queuebot:#ubuntu-release- New binary: abci [ppc64el] (zesty-proposed/universe) [0.0~git20170124.0.f94ae5e-2] (no packageset)
[08:36] -queuebot:#ubuntu-release- New binary: abci [arm64] (zesty-proposed/universe) [0.0~git20170124.0.f94ae5e-2] (no packageset)
[08:36] -queuebot:#ubuntu-release- New binary: abci [i386] (zesty-proposed/universe) [0.0~git20170124.0.f94ae5e-2] (no packageset)
[08:36] -queuebot:#ubuntu-release- New binary: tendermint-go-p2p [amd64] (zesty-proposed/universe) [0.0~git20170113.0.3d98f67-1] (no packageset)
[08:36] -queuebot:#ubuntu-release- New binary: abci [armhf] (zesty-proposed/universe) [0.0~git20170124.0.f94ae5e-2] (no packageset)
[08:36] -queuebot:#ubuntu-release- New binary: abci [s390x] (zesty-proposed/universe) [0.0~git20170124.0.f94ae5e-2] (no packageset)
[08:37] -queuebot:#ubuntu-release- New binary: abci [powerpc] (zesty-proposed/universe) [0.0~git20170124.0.f94ae5e-2] (no packageset)
[08:42] -queuebot:#ubuntu-release- New binary: dnss [amd64] (zesty-proposed/universe) [0.0~git20161126.0.162090e-1] (no packageset)
[08:42] -queuebot:#ubuntu-release- New binary: dnss [ppc64el] (zesty-proposed/universe) [0.0~git20161126.0.162090e-1] (no packageset)
[08:43] -queuebot:#ubuntu-release- New binary: dnss [arm64] (zesty-proposed/universe) [0.0~git20161126.0.162090e-1] (no packageset)
[08:43] -queuebot:#ubuntu-release- New binary: dnss [s390x] (zesty-proposed/universe) [0.0~git20161126.0.162090e-1] (no packageset)
[08:43] -queuebot:#ubuntu-release- New binary: dnss [armhf] (zesty-proposed/universe) [0.0~git20161126.0.162090e-1] (no packageset)
[08:43] -queuebot:#ubuntu-release- New binary: golang-github-grpc-ecosystem-grpc-gateway [ppc64el] (zesty-proposed/universe) [1.1.0+git20170127.54.6863684-1] (no packageset)
[08:44] -queuebot:#ubuntu-release- New binary: dnss [powerpc] (zesty-proposed/universe) [0.0~git20161126.0.162090e-1] (no packageset)
[08:44] -queuebot:#ubuntu-release- New binary: golang-github-grpc-ecosystem-grpc-gateway [armhf] (zesty-proposed/universe) [1.1.0+git20170127.54.6863684-1] (no packageset)
[08:44] -queuebot:#ubuntu-release- New binary: golang-github-grpc-ecosystem-grpc-gateway [arm64] (zesty-proposed/universe) [1.1.0+git20170127.54.6863684-1] (no packageset)
[08:44] -queuebot:#ubuntu-release- New binary: golang-github-grpc-ecosystem-grpc-gateway [s390x] (zesty-proposed/universe) [1.1.0+git20170127.54.6863684-1] (no packageset)
[08:45] -queuebot:#ubuntu-release- New binary: golang-github-grpc-ecosystem-grpc-gateway [i386] (zesty-proposed/universe) [1.1.0+git20170127.54.6863684-1] (no packageset)
[08:45] -queuebot:#ubuntu-release- New binary: golang-github-grpc-ecosystem-grpc-gateway [powerpc] (zesty-proposed/universe) [1.1.0+git20170127.54.6863684-1] (no packageset)
[08:48] -queuebot:#ubuntu-release- New binary: dnss [i386] (zesty-proposed/universe) [0.0~git20161126.0.162090e-1] (no packageset)
[09:56] -queuebot:#ubuntu-release- New: accepted abci [amd64] (zesty-proposed) [0.0~git20170124.0.f94ae5e-2]
[09:56] -queuebot:#ubuntu-release- New: accepted abci [armhf] (zesty-proposed) [0.0~git20170124.0.f94ae5e-2]
[09:56] -queuebot:#ubuntu-release- New: accepted abci [powerpc] (zesty-proposed) [0.0~git20170124.0.f94ae5e-2]
[09:56] -queuebot:#ubuntu-release- New: accepted abci [s390x] (zesty-proposed) [0.0~git20170124.0.f94ae5e-2]
[09:56] -queuebot:#ubuntu-release- New: accepted dnss [arm64] (zesty-proposed) [0.0~git20161126.0.162090e-1]
[09:56] -queuebot:#ubuntu-release- New: accepted dnss [i386] (zesty-proposed) [0.0~git20161126.0.162090e-1]
[09:56] -queuebot:#ubuntu-release- New: accepted dnss [ppc64el] (zesty-proposed) [0.0~git20161126.0.162090e-1]
[09:56] -queuebot:#ubuntu-release- New: accepted abci [arm64] (zesty-proposed) [0.0~git20170124.0.f94ae5e-2]
[09:56] -queuebot:#ubuntu-release- New: accepted abci [ppc64el] (zesty-proposed) [0.0~git20170124.0.f94ae5e-2]
[09:57] -queuebot:#ubuntu-release- New: accepted dnss [armhf] (zesty-proposed) [0.0~git20161126.0.162090e-1]
[09:57] -queuebot:#ubuntu-release- New: accepted dnss [s390x] (zesty-proposed) [0.0~git20161126.0.162090e-1]
[09:57] -queuebot:#ubuntu-release- New: accepted abci [i386] (zesty-proposed) [0.0~git20170124.0.f94ae5e-2]
[09:57] -queuebot:#ubuntu-release- New: accepted dnss [powerpc] (zesty-proposed) [0.0~git20161126.0.162090e-1]
[09:57] -queuebot:#ubuntu-release- New: accepted dnss [amd64] (zesty-proposed) [0.0~git20161126.0.162090e-1]
[09:57] -queuebot:#ubuntu-release- New: accepted golang-github-grpc-ecosystem-go-grpc-prometheus [amd64] (zesty-proposed) [1.1+git20160910.0.6b7015e-1]
[09:57] -queuebot:#ubuntu-release- New: accepted golang-github-grpc-ecosystem-grpc-gateway [arm64] (zesty-proposed) [1.1.0+git20170127.54.6863684-1]
[09:57] -queuebot:#ubuntu-release- New: accepted golang-github-grpc-ecosystem-grpc-gateway [i386] (zesty-proposed) [1.1.0+git20170127.54.6863684-1]
[09:57] -queuebot:#ubuntu-release- New: accepted golang-github-grpc-ecosystem-grpc-gateway [ppc64el] (zesty-proposed) [1.1.0+git20170127.54.6863684-1]
[09:57] -queuebot:#ubuntu-release- New: accepted golang-github-rsc-letsencrypt [amd64] (zesty-proposed) [0.0~git20160929.0.76104d2-2]
[09:57] -queuebot:#ubuntu-release- New: accepted golang-github-grpc-ecosystem-grpc-gateway [amd64] (zesty-proposed) [1.1.0+git20170127.54.6863684-1]
[09:57] -queuebot:#ubuntu-release- New: accepted golang-github-grpc-ecosystem-grpc-gateway [powerpc] (zesty-proposed) [1.1.0+git20170127.54.6863684-1]
[09:57] -queuebot:#ubuntu-release- New: accepted golang-github-grpc-ecosystem-grpc-gateway [armhf] (zesty-proposed) [1.1.0+git20170127.54.6863684-1]
[09:57] -queuebot:#ubuntu-release- New: accepted golang-github-grpc-ecosystem-grpc-gateway [s390x] (zesty-proposed) [1.1.0+git20170127.54.6863684-1]
[09:57] -queuebot:#ubuntu-release- New: accepted rclone [amd64] (zesty-proposed) [1.35-1]
[09:57] -queuebot:#ubuntu-release- New: accepted rclone [armhf] (zesty-proposed) [1.35-1]
[09:57] -queuebot:#ubuntu-release- New: accepted rclone [ppc64el] (zesty-proposed) [1.35-1]
[09:57] -queuebot:#ubuntu-release- New: accepted tendermint-go-p2p [amd64] (zesty-proposed) [0.0~git20170113.0.3d98f67-1]
[09:57] -queuebot:#ubuntu-release- New: accepted rclone [arm64] (zesty-proposed) [1.35-1]
[09:57] -queuebot:#ubuntu-release- New: accepted rclone [s390x] (zesty-proposed) [1.35-1]
[09:58] -queuebot:#ubuntu-release- New: accepted rclone [i386] (zesty-proposed) [1.35-1]
[10:00] <tjaalton> could someone review bug 1671799 so that I can start pushing this to proposed
[10:00] <tjaalton>  FFe: xserver 1.19.3
[10:13] <wgrant> I'm starting the removal of zesty/powerpc. Nothing should break, and packages won't vanish for a few days, but new builds and publications should have stopped. Let me know if anything seems awry.
[10:53] -queuebot:#ubuntu-release- New binary: merkleeyes [i386] (zesty-proposed/universe) [0.0~git20170130.0.549dd01-1] (no packageset)
[10:53] -queuebot:#ubuntu-release- New binary: merkleeyes [s390x] (zesty-proposed/universe) [0.0~git20170130.0.549dd01-1] (no packageset)
[10:53] -queuebot:#ubuntu-release- New binary: merkleeyes [ppc64el] (zesty-proposed/universe) [0.0~git20170130.0.549dd01-1] (no packageset)
[10:54] -queuebot:#ubuntu-release- New binary: merkleeyes [amd64] (zesty-proposed/universe) [0.0~git20170130.0.549dd01-1] (no packageset)
[10:54] -queuebot:#ubuntu-release- New binary: merkleeyes [armhf] (zesty-proposed/universe) [0.0~git20170130.0.549dd01-1] (no packageset)
[10:55] -queuebot:#ubuntu-release- New binary: merkleeyes [arm64] (zesty-proposed/universe) [0.0~git20170130.0.549dd01-1] (no packageset)
[10:55] -queuebot:#ubuntu-release- New binary: tendermint [ppc64el] (zesty-proposed/universe) [0.8.0+git20170113.0.764091d-1] (no packageset)
[10:55] -queuebot:#ubuntu-release- New binary: tendermint [amd64] (zesty-proposed/universe) [0.8.0+git20170113.0.764091d-1] (no packageset)
[10:56] -queuebot:#ubuntu-release- New binary: tendermint [arm64] (zesty-proposed/universe) [0.8.0+git20170113.0.764091d-1] (no packageset)
[10:56] -queuebot:#ubuntu-release- New binary: tendermint [s390x] (zesty-proposed/universe) [0.8.0+git20170113.0.764091d-1] (no packageset)
[10:58] <doko> apw: please could you consider overriding the linux autopkg test failures for binutils/gcc-6 again?
[11:00] -queuebot:#ubuntu-release- New: accepted merkleeyes [amd64] (zesty-proposed) [0.0~git20170130.0.549dd01-1]
[11:00] -queuebot:#ubuntu-release- New: accepted merkleeyes [armhf] (zesty-proposed) [0.0~git20170130.0.549dd01-1]
[11:00] -queuebot:#ubuntu-release- New: accepted merkleeyes [ppc64el] (zesty-proposed) [0.0~git20170130.0.549dd01-1]
[11:00] -queuebot:#ubuntu-release- New: accepted merkleeyes [arm64] (zesty-proposed) [0.0~git20170130.0.549dd01-1]
[11:00] -queuebot:#ubuntu-release- New: accepted merkleeyes [s390x] (zesty-proposed) [0.0~git20170130.0.549dd01-1]
[11:00] -queuebot:#ubuntu-release- New: accepted merkleeyes [i386] (zesty-proposed) [0.0~git20170130.0.549dd01-1]
[11:01] -queuebot:#ubuntu-release- New: accepted tendermint [amd64] (zesty-proposed) [0.8.0+git20170113.0.764091d-1]
[11:01] -queuebot:#ubuntu-release- New: accepted tendermint [ppc64el] (zesty-proposed) [0.8.0+git20170113.0.764091d-1]
[11:01] -queuebot:#ubuntu-release- New: accepted tendermint [arm64] (zesty-proposed) [0.8.0+git20170113.0.764091d-1]
[11:01] -queuebot:#ubuntu-release- New: accepted tendermint [s390x] (zesty-proposed) [0.8.0+git20170113.0.764091d-1]
[11:05] <doko> although the ppc64el might be a real one ...
[11:09] <jamespage> bdmurray (or any other SRU team member): the neutron task of bug 1664306 was blocked on resolution of bug 1668578 in zesty - this has now been done so please can the neutron update be accepted into yakkety so I can trigger the SRU testing process.
[11:09] <jamespage> cheers
[11:39] <cjwatson> Does anyone know what's up with these failed snapd autopkgtests that are stopping openssh from migrating?
[11:45] -queuebot:#ubuntu-release- New binary: curry-base [i386] (zesty-proposed/universe) [0.4.2-3] (no packageset)
[11:46] -queuebot:#ubuntu-release- New binary: curry-base [ppc64el] (zesty-proposed/universe) [0.4.2-3] (no packageset)
[11:54] -queuebot:#ubuntu-release- New binary: curry-base [s390x] (zesty-proposed/universe) [0.4.2-3] (no packageset)
[11:57] -queuebot:#ubuntu-release- New binary: curry-base [amd64] (zesty-proposed/universe) [0.4.2-3] (no packageset)
[12:29] -queuebot:#ubuntu-release- New binary: curry-base [arm64] (zesty-proposed/universe) [0.4.2-3] (no packageset)
[12:33] -queuebot:#ubuntu-release- New binary: curry-base [armhf] (zesty-proposed/universe) [0.4.2-3] (no packageset)
[12:55] <infinity> rtg: wgrant has a gift for you this morning.
[12:55] <wgrant> rip powerpc
[12:55] <infinity> rtg: As of an hour or two ago, we no longer create build records for powerpc in zesty, so your next zesty upload can drop PPC if you want.
[12:55] <wgrant> At least I hope that's the gift.
[12:55] <wgrant> Or I've made a terrible mistkae
[12:55] <infinity> wgrant: It was either that or a lap dance.
[12:55]  * wgrant shudders.
[12:56] <rtg> infinity, oh gross
[12:56] <infinity> Gross?
[12:56] <infinity> Oh, the lap dance? :P
[12:56] <rtg> he's all arms and legs. it would just hurt.
[12:56] <infinity> He's a prodigy.  I'm sure he'd figure it out.
[12:57] <rtg> infinity, anyway, -14 will have powerpc purged
[12:57] <rtg> (maybe)
[12:58] -queuebot:#ubuntu-release- New: accepted curry-base [amd64] (zesty-proposed) [0.4.2-3]
[12:58] -queuebot:#ubuntu-release- New: accepted curry-base [armhf] (zesty-proposed) [0.4.2-3]
[12:58] -queuebot:#ubuntu-release- New: accepted curry-base [ppc64el] (zesty-proposed) [0.4.2-3]
[12:58] -queuebot:#ubuntu-release- New: accepted curry-base [arm64] (zesty-proposed) [0.4.2-3]
[12:58] -queuebot:#ubuntu-release- New: accepted curry-base [s390x] (zesty-proposed) [0.4.2-3]
[12:58] -queuebot:#ubuntu-release- New: accepted curry-base [i386] (zesty-proposed) [0.4.2-3]
[12:59] <infinity> rtg: It doesn't have to.  But since you've already tried two or three times, just informing you that you really can this time. :P
[13:00] <rtg> infinity, sforshee has enjoyed the process so much that I'm gonna let him do it again.
[13:02] <sforshee> oh joy
[13:03] -queuebot:#ubuntu-release- New: accepted qtubuntu-print [sync] (zesty-proposed) [0.1+17.04.20170301.2-0ubuntu1]
[13:03] -queuebot:#ubuntu-release- New: accepted ubuntu-printing-app [sync] (zesty-proposed) [0.1+17.04.20170308-0ubuntu1]
[13:05] -queuebot:#ubuntu-release- Unapproved: walinuxagent (xenial-proposed/main) [2.2.2-0ubuntu0~16.04.1 => 2.2.6-0ubuntu1~16.04.1] (ubuntu-cloud, ubuntu-server)
[13:05] -queuebot:#ubuntu-release- Unapproved: walinuxagent (yakkety-proposed/main) [2.2.2-0ubuntu0~16.10.1 => 2.2.6-0ubuntu1~16.10.1] (ubuntu-cloud, ubuntu-server)
[13:06] -queuebot:#ubuntu-release- Unapproved: walinuxagent (trusty-proposed/main) [2.2.2-0ubuntu0~14.04.1 => 2.2.6-0ubuntu1~14.04.1] (ubuntu-cloud, ubuntu-server)
[14:38] <bdmurray> jamespage: should the neutron upload supersede the existing one in yakkety-proposed?
[14:40] <jamespage> bdmurray: yes please -that should resolve the DEP-8 test failure (according to the bug)
[14:44] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (yakkety-proposed) [2:9.2.0-0ubuntu1]
[14:56] -queuebot:#ubuntu-release- New binary: curry-frontend [i386] (zesty-proposed/universe) [0.4.2-5] (no packageset)
[14:56] -queuebot:#ubuntu-release- New binary: curry-frontend [ppc64el] (zesty-proposed/universe) [0.4.2-5] (no packageset)
[14:58] -queuebot:#ubuntu-release- New binary: curry-frontend [amd64] (zesty-proposed/universe) [0.4.2-5] (no packageset)
[15:02] -queuebot:#ubuntu-release- New binary: curry-frontend [s390x] (zesty-proposed/universe) [0.4.2-5] (no packageset)
[15:32] -queuebot:#ubuntu-release- New binary: curry-frontend [armhf] (zesty-proposed/universe) [0.4.2-5] (no packageset)
[15:34] -queuebot:#ubuntu-release- New binary: curry-frontend [arm64] (zesty-proposed/universe) [0.4.2-5] (no packageset)
[16:38] <bdmurray> slangasek: I'm looking at update-manager in -proposed for yakkety which is supposed to fix bug 1623856. I was never able to recreate it but the fix is just "+                        <property name="min_content_height">80</property>" which while it may not fix it doesn't hurt.
[16:39] <slangasek> bdmurray: so when you trigger a dpkg conffile prompt, you can't reproduce it/
[16:40] <bdmurray> slangasek: I want to do an SRU of update-manager to fix bug 1654008.
[16:41] <bdmurray> slangasek: the description just talks about the details window which shows the log of the package download / installs
[16:44] <bdmurray> slangasek: oh, hey I see it now on zesty
[16:44] <bdmurray> slangasek: I guess I'll figure out how to fix it right then and bundle it with the other thing.
[17:14] <slangasek> bdmurray: ok cool
[17:17] -queuebot:#ubuntu-release- New binary: rustc [s390x] (zesty-proposed/universe) [1.16.0+dfsg1-1~exp1ubuntu1] (no packageset)
[18:05] -queuebot:#ubuntu-release- New: accepted curry-frontend [amd64] (zesty-proposed) [0.4.2-5]
[18:05] -queuebot:#ubuntu-release- New: accepted curry-frontend [armhf] (zesty-proposed) [0.4.2-5]
[18:05] -queuebot:#ubuntu-release- New: accepted curry-frontend [ppc64el] (zesty-proposed) [0.4.2-5]
[18:05] -queuebot:#ubuntu-release- New: accepted curry-frontend [arm64] (zesty-proposed) [0.4.2-5]
[18:05] -queuebot:#ubuntu-release- New: accepted curry-frontend [s390x] (zesty-proposed) [0.4.2-5]
[18:05] -queuebot:#ubuntu-release- New: accepted curry-frontend [i386] (zesty-proposed) [0.4.2-5]
[19:04] -queuebot:#ubuntu-release- Unapproved: rejected walinuxagent [source] (yakkety-proposed) [2.2.6-0ubuntu1~16.10.1]
[19:05] -queuebot:#ubuntu-release- Unapproved: rejected walinuxagent [source] (trusty-proposed) [2.2.6-0ubuntu1~14.04.1]
[19:05] -queuebot:#ubuntu-release- Unapproved: rejected walinuxagent [source] (xenial-proposed) [2.2.6-0ubuntu1~16.04.1]
[19:22] -queuebot:#ubuntu-release- New binary: pakcs [i386] (zesty-proposed/universe) [1.14.1-4] (no packageset)
[19:29] -queuebot:#ubuntu-release- Unapproved: walinuxagent (yakkety-proposed/main) [2.2.2-0ubuntu0~16.10.1 => 2.2.6-0ubuntu1~16.10.1] (ubuntu-cloud, ubuntu-server)
[19:30] -queuebot:#ubuntu-release- Unapproved: walinuxagent (xenial-proposed/main) [2.2.2-0ubuntu0~16.04.1 => 2.2.6-0ubuntu1~16.04.1] (ubuntu-cloud, ubuntu-server)
[19:30] -queuebot:#ubuntu-release- Unapproved: walinuxagent (trusty-proposed/main) [2.2.2-0ubuntu0~14.04.1 => 2.2.6-0ubuntu1~14.04.1] (ubuntu-cloud, ubuntu-server)
[19:45] -queuebot:#ubuntu-release- Unapproved: accepted steam [source] (yakkety-proposed) [1:<IP_ADDRESS>-5ubuntu2]
[19:48] -queuebot:#ubuntu-release- Unapproved: accepted steam [source] (xenial-proposed) [1:<IP_ADDRESS>-1ubuntu4]
[19:50] -queuebot:#ubuntu-release- Unapproved: accepted steam [source] (trusty-proposed) [1:<IP_ADDRESS>-1ubuntu1.2]
[19:53] -queuebot:#ubuntu-release- New binary: pakcs [armhf] (zesty-proposed/universe) [1.14.1-4] (no packageset)
[19:57] -queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (yakkety-proposed) [2.2.6-0ubuntu1~16.10.1]
[19:59] -queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (xenial-proposed) [2.2.6-0ubuntu1~16.04.1]
[20:03] -queuebot:#ubuntu-release- New binary: pakcs [s390x] (zesty-proposed/universe) [1.14.1-4] (no packageset)
[20:10] -queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (trusty-proposed) [2.2.6-0ubuntu1~14.04.1]
[20:19] -queuebot:#ubuntu-release- New binary: rustc [ppc64el] (zesty-proposed/universe) [1.16.0+dfsg1-1~exp1ubuntu1] (no packageset)
[20:30] -queuebot:#ubuntu-release- New binary: pakcs [ppc64el] (zesty-proposed/universe) [1.14.1-4] (no packageset)
[20:42] <slangasek> robru: at one point I remember discussion that the britney nagmails would happen periodically, not one time; was that idea abandoned?
[20:43] <robru> slangasek: oh, uh, I don't recall that, sorry. the current implementation is just one-off emails
[20:43] <robru> slangasek: do you want daily mails? I can make them happen daily ;-)
[20:43] <slangasek> robru: ok, I believe I read a question about this in an email from you :)
[20:43] <robru> slangasek: oh right, I remember asking that but I don't recall ever getting a reply
[20:43] <slangasek> robru: *I* think daily emails are better than a one-off, but I didn't know if you had feedback from others
[20:45] <jbicha> wow, daily
[20:45] <robru> slangasek: I never got any feedback on that, no
[20:45] <robru> slangasek: wouldn't be hard to implement, just need to change the cache from a boolean to storing age and then can send a new email every time the age increases by a day
[20:45]  * slangasek nods
[20:46] <slangasek> from my POV that would be better, because e.g. I might read the mail, do a thing, think it's fixed, be wrong, and never be told
[20:46] <robru> slangasek: true. but if "do a thing" means "upload a new package" then there'd be a fresh timeout and fresh email for that
[20:47] <slangasek> yes, but that's not always the thing I'd do
[20:47] <robru> true
[20:47] <slangasek> for instance, I just removed from s390x binaries
[20:47] <slangasek> :)
[20:47] <slangasek> s/from/some/
[20:54] -queuebot:#ubuntu-release- New binary: pakcs [amd64] (zesty-proposed/universe) [1.14.1-4] (no packageset)
[20:56] <Ukikie> 1. That really stinks for people without upload rights and stuff in the sponsoring queue.  2. I "fixed" a package so it builds on most arches rather than on none (now matching Debian), this would give me daily emails.  This would discourage those types of fixes IMO.  3. Can I opt-out of daily?
[20:56] <robru> slangasek: ^
[21:07] <nacc> Ukikie: why 1?
[21:08] <Ukikie> nacc: Because you've already "fixed" it, it's pending on someone else to review, so daily reminders to fix something that you've already looked at and proposed a fix is only going to agitate one.
[21:10] <nacc> Ukikie: oh i see what you mean now
[21:11] <Ukikie> (And in the case of the latter, my goal was to make it better and bring it up to par with Debian, not fix the entire problem.  More specifically since the issue is in another package.)
[21:15] <robru> Ukikie: well, whoever sponsored your upload will also get the same nag mail. so it's not just nagging you, at least
[21:15] <slangasek> Ukikie: 1. the people being emailed are the ones who either uploaded or had sponsored the package that is stuck in -proposed; I think it's perfectly fair for those people to be asked to be responsible for following through, and if you have a package currently in this state you can point me at it and I'll sponsor it here and now
[21:16] <slangasek> 3. no, you should opt out by filtering the mail on the receiving end
[21:16]  * robru sighs a huge sigh of relief
[21:17] <Ukikie> slangasek: Oh I agree, I'm not saying they shouldn't fix it.  Luckily I don't, I just could see how that can easily happen.  Yeah, if it goes daily I'll have to. :/  Thanks for following up.
[21:19] <infinity> Daily might be excessive, but "I want to fire and forget an upload" is exactly why we're doing this.  So people stop forgetting. :P
[21:19] <infinity> That is to say, I'm not sure I want uploads to be attributed to people who don't care to follow through.
[21:19] <infinity> Patches, sure, but not uploads.
[21:19] <Ukikie> slangasek: FWIW, the second case I gave actually does exist, I already got the second email. :P
[21:20] <slangasek> sure
[21:20] <slangasek> but it's only "fixed" if it lands in devel :)(
[21:20] <Ukikie> infinity: If it makes you feel better, I got an upload sponsored because I knew that when gcc updated, it'd ftbfs.  So I got it fixed before it broke. :)
[21:20] <slangasek> and someone who has the context to say the package is now fixed but needs manual action by an AA can tell us that
[21:21] <Ukikie> (New package for Ubuntu, so the rest did migrate.)
[21:24] <infinity> robru, slangasek: Anyhow, if we're to make the mails repeat (not the worst idea ever), might I suggest an exponential back-off?  Either 2^n or 3^n (where n=notified_count) would probably be a bit less ick.
[21:24] <robru> infinity: you mean send an email every 2^n days?
[21:24] <slangasek> infinity: if daily is too frequently, I think repeating at a fixed interval is better than an exponential backoff
[21:24] <slangasek> I /want/ someone who has a package stuck in -proposed to be annoyed by the mails ;)
[21:24] <robru> I'm open to whatever is decided
[21:25] <infinity> Maybe I'm special, but I find that predictably repetitive emails end up deleted as noise.  "oh look, that again".  An exponential back-off lets you simmer down from your annoyance about useless email for a bit before it reminds you that, hey, you're still a slacker.
[21:26] <infinity> So, it's partially about being less annoying for things stuck for a long time, but also a bit of a psychological warfare via rfc2822 game.
[21:27] <slangasek> maybe we should ask how quickly we can reasonably expect someone to respond to such a mail
[21:27] <slangasek> because it doesn't make sense to ever send the mails more frequently than that response time
[21:27] <infinity> (And, really, if it's been stuck for 64 or 128 days, it's in the realm of "clearly there's a larger problem", and a daily/frequent nag WILL be ignored to the point where it's meaningless)
[21:27] <slangasek> infinity: except in the case of the initial mails, where everything was stuck a long time and the mails have just started
[21:28] <infinity> Though a cap on the back-off would also be reasonable, as eventually "every 3 years" is pointless too. ;)
[21:29] <infinity> 2^n, capped at 32 seems like a reasonable straw man to me.
[21:29] <robru> instead of a backoff based on the number of mails sent, it should be a backoff based on the existing age, as indeed there are already packages stuck for multiple hundreds of days that we probably don't want daily nags for
[21:29] <infinity> Cause, yes, it's reasonable to expect people to respond in the first 1 and 2 days, but if they don't, they're not likely to suddenly find the time on day 3, hence the back-off, to balance nag with desensitizing them.
[21:30] <robru> actually I'm liking this idea.
[21:30] <infinity> robru: Assuming the cap, one could just one-time mangle the back-off DB to say all of that is at the 32 mark or whatever.
[21:32] <infinity> robru: Err, on the other hand, your way is one state file less, so do that. :P
[21:32] <infinity> robru: (We already have state for age, counting emails is silly)
[21:32] <robru> heh
[21:33] <infinity> Just means some stat and sloppy math to make sure you never miss an age "tick", but also don't count one twice.
[21:33] <robru> slangasek: ^ so, uh, are we doing exponential backoff with a ceiling of monthly nag mails?
[21:34] <robru> I already have the code written for daily but wouldn't be hard to change
[21:35] <nacc> slangasek: so it seems like emacs25 stuck in -proposed occurred with 25.1+1-2ubuntu3 ... but not before. dannf was looking into it, but I don't think we have much progress on it yet :/. it's holding up imagemagick (which in turn is holding up emacs24)
[21:35] <dannf> nacc: fwiw, been trying to repro on debian, no success so far
[21:36] <Ukikie> robru: Hrm, I thought there was going to be a header for this?  I'm not seeing it.
[21:36] <robru> Ukikie: yeah, should be X-Proposed-Migration
[21:37] <robru> Ukikie: https://git.launchpad.net/~ubuntu-release/britney/+git/britney2-ubuntu/tree/britney2/policies/email.py#n25 this is the email that gets sent
[21:37] <infinity> From the psychological perspective, powers of 2 not exactly matching week lengths also shuffles things around enough that you wouldn't be nagging a Friday uploader every Friday night.  Unpredictability is key to a successful nag.
[21:38] <Ukikie> robru: Oh hrm, thanks.  That's not the message I got.
[21:38] <infinity> And I've officially spent too much time thinking about this when I was meant to be napping.
[21:38] <robru> Ukikie: then I dunno what you got but it's not a "stuck in -proposed" nag ;-)
[21:39] <Ukikie> Indeed.  Guess a random rebuild one that came at a suspicious time. :P
[21:40] <infinity> I did do a mass retry of FTBFS this morning.
[21:41] <Ukikie> Fri, 17 Mar 2017 07:37:24; that'd be it.
[21:43] <robru> brb
[21:47] <nacc> dannf: darn! :/
[21:49] <nacc> dannf: i get the feeling that the paralle=1 change was done for this reason before, and ithappened to fix it, but maybe was just masking it
[21:49] <dannf> yeah, i can try dropping that to see if it makes it more reproducible
[21:50] <nacc> dannf: it's hard to say if it was fixing/working around this issue or if it was any of the other arm64 failures we see :)
[21:52] <dannf> oh, nm- parallel builds are enabled now - didn't realize that'd been restored
[21:53] <dannf> what's the memsize of our arm64 guest builders again? i've tried w/ 1G & 2G of mem assigned
[21:53] <dannf> w/ & w/o swap
[21:53] <infinity> dannf: They should be 4cores/8gigs.
[21:54] <nacc> dannf: https://launchpad.net/ubuntu/+source/emacs25/25.1+1-3ubuntu1 says it's parallel=1 on arm64?
[21:56] <dannf> oh - yeah, it's because i'm using debian's source (since i was trying to repro in debian, to get a bug filed/help there)
[21:56] <nacc> dannf: ack
[21:56] <nacc> dannf: which i guess is even stranger, we use a stricter paralle and trigger it :)
[21:57] <dannf> yeah, i probably need to get back to where i can reproduce it on ubuntu - but even then, it wasn't very reliable in my case
[21:57] <dannf> or find someone that can actually debug emacs :)
[22:10] <slangasek> robru: I am not convinced by the argument for a backoff; but a backoff would get us more mails than we get currently, so I'm ok to go ahead with that
[22:39] -queuebot:#ubuntu-release- New binary: pakcs [arm64] (zesty-proposed/universe) [1.14.1-4] (no packageset)
[22:41] -queuebot:#ubuntu-release- Unapproved: update-notifier (yakkety-proposed/main) [3.175.1 => 3.175.2] (ubuntu-desktop, ubuntu-server)
[22:44] -queuebot:#ubuntu-release- Unapproved: update-manager (yakkety-proposed/main) [1:16.10.8 => 1:16.10.9] (core)
[23:22] -queuebot:#ubuntu-release- New binary: gcc-6-cross-ports [amd64] (zesty-proposed/main) [17ubuntu1] (ubuntu-desktop)


[14:07] <maco> bcurtiswx: i dont have your number. can you tell her 10:15 instead?
[14:08] <bcurtiswx> sure
[14:08] <maco> thanks
[21:05] <bcurtiswx> maco: how long do depwaits last?
[21:05] <bcurtiswx> until it tries again
[21:05] <maco> until the deps are resolved i think
[21:07] <bcurtiswx> maco, hmm OK.  maybe it scans every ten minutes or so


[02:49] <schultza> Whats the fast way to get ubuntu+1 set up so when testing updates to a new code name, it just continues to roll on without editing the sources.list file or clicking a button?
[08:17] <lordievader> Good morning.
[08:23] <elfy> hi lordievader
[08:24] <lordievader> Hey elfy, how are you?
[08:24] <elfy> all good thanks - you?
[08:25] <lordievader> Trying to wake up...
[08:26] <elfy> heh
[08:28] <elfy> well - good luck with that, but I'm off to work
[08:30] <lordievader> Good luck with that too ;)
[13:14] <BluesKaj> Hiyas all


[02:10] <blackcatgatonegr> Uget, best download manager for ubuntu, and is no small it can fit on a floppy disk
[02:10] <blackcatgatonegr> I mean, best small light download manager
[04:16] <origamifreak> hello
[04:17] <origamifreak> anyone here?
[04:36] <origamifreak> hello?
[04:41] <Unit193> !anybody
[04:46] <origamifreak> ok, just seeing if anyone was there to answer
[04:50] <origamifreak> I'm tryilng to get lubuntu to use the correct aspect ratio and a decent resolution on an external monitor. The external monitor is a 1080 HD tv and I'm running lubuntu off of an Asus 1000 he netbook. I know I'm probably not going to get 1080 hd resolution but non of the default values are the correct aspect ratio and a decent resolution.
[04:51] <origamifreak> I tried using the terminal and xrandr, but no luck
[04:52] <Unit193> Did you try and see if generating an xorg.conf file helped?  Or maybe arandr?  I know mine supports more than it's pretending too so I just add what I want manually with xrandr.
[04:53] <origamifreak> I tried adding a couple different configurations using the terminal and xrandr but the screen just turned black when I applied the changes
[04:54] <origamifreak> I haven't tried arandr, Does it allow you to add different resolutions other than the default?
[04:55] <Unit193> !fixres
[04:55] <Unit193> !xorgconf
[04:55] <Unit193> It's just a GUI to xrandr, so I'd say not a ton of help.
[04:58] <origamifreak> ok thanks, ubottu and Unit193, I might try making an xorg.conf file. I'm still kind of new to Linux, so it may take a little study/ trial and error.
[05:00] <origamifreak> I've also tried other distros based off of Ubuntu that gave me a better resolution/ aspect ratio options, but lubuntu seems to be doing the best so far when it comes to speed
[05:08] <Unit193> You could try and see what may differ.
[05:14] <origamifreak> Since it's a netbook (and several years old) I was looking for a really minimal linux distrobution. So far I've tried joli os, bodhi linux, crunchbang linux, and lubuntu.
[05:16] <origamifreak> lubuntu and joli os seem to work the best, Joli os is just a little slower and doesn't support some of the applets I want to install, but Lubuntu has this aspect ratio problem which makes everything look a little squished
[05:25] <holstein> the aspect ratio problem?
[05:26] <holstein> sometimes i fire up knoppix, and steal the xorg.conf from it
[05:26] <holstein> if it looks like you want on some other distro of linux, then you *can* make it look that way in lubuntu... it might be challenging though
[05:44] <Unit193> I hear puppy gives good xorgs too, you seen it?
[05:50] <holstein> Unit193: your right... that would be better
[05:50] <holstein> you have that nice config at the startup
[05:51] <holstein> origamifreak: ^^
[06:15] <origamifreak> hey, sorry, I was checking some stuff on my tv and computer
[06:15] <origamifreak> it turns out that the TV has a mode to display in 4x3 which is the correct aspect ratio
[06:17] <origamifreak> although I still might try and get an xorg.conf file or make my own
[08:37] <jarnos> I can not umount an usb stick. Umount anyway does not work for it in pcmanfm 0.9.9.
[08:37] <jarnos> Neither does sudo umount -f
[08:40] <jarnos> Oh, later it worked by pcmanfm. BTW, I could not umount the stick by Windows XP earlier today.
[09:23] <bkm> hello, how can i alter the autocompleted items in `lxpanelctl run` or add a command to `lxpanel menu` ?
[14:24] <leszek> hi
[15:25] <BMS1> Hello wizards, does lubuntu not load the .config/openbox/lxde-rc.xml file by default?
[15:32] <BMS1> I suppose not, since the lubuntu-rc.xml encourages copying it, but it would be nice to have several files loaded so I can segregate some stuff out into smaller, more manageable files.
[17:09] <sb1980> hi! i've got a weird behaviour: when running mpd (via sonata) i can't view flash videos. i have to stop sonata (sometimes even disconnect) to view. anyone know what to do?
[17:10] <holstein> these days, i usually try the chrome browser (not chromium) since its got its own flash in there
[17:15] <leszek> which has nothing to do with the described problem holstein :P
[17:15] <holstein> its a suggestion for troubleshooting the current version of flash being used
[17:15] <leszek> sb1980: what is the output audio plugin you use for mpd ? It should be alsa not oss otherwise your soundcard is blocked and therefore flash does not play any audio
[17:16] <holstein> also, trying a different browser... feel free and suggest anything you'd like though
[17:16] <leszek> holstein: I highly doubt it has to do with the used browser or flashplayer
[17:18] <holstein> sure.. and i bet you are right.. flash *is* problematic in linux though
[17:30] <sb1980> the problem occurs in firefox as well as chrome.
[17:30] <sb1980> leszek: audio_output { type: "alsa": }
[17:30] <sb1980> could this be overwritten somewhere?
[17:31] <sb1980> also (maybe related) as soon as i mute my alsa master once, i can't get the sound back
[17:51] <leszek> sb1980: but playback of audio works like say for example mplayer when you are playing a song in sonata ?
[17:52] <sb1980> lesczek: as now its muted anyway i can' check, but i think other players might have been blocked too.
[17:52] <leszek> thats a strange problem then. Seems that dmix is broken I guess. What soundcard do you have ?
[18:06] <sb1980> i've got a RealTek alc892 onboard. and i've got a nvidia gpu which is listed in my sound devices?!
[18:06] <sb1980> b/c of hdmi i guess
[18:07] <sb1980> wait, i'll reboot to verify the problem with another audio player instead of flash player
[18:15] <sb1980> rhythmbox: no sound at all, nomatter whats happening in sonata
[18:17] <sb1980> but now mpd tells me: output: Failed to open "My ALSA Device" [alsa]: Failed to open ALSA device "hw:0,0": Device or resource busy
[18:20] <sb1980> it looks like the sound is being distributed on my different output options . now rhythmbox was playing on "left"
[19:13] <melodie_> hello
[20:12] <kanliot> hi melodie_
[20:13] <melodie_> hi kanliot !
[20:13] <kanliot> sup
[21:16] <melodie_> good night


[01:47] <eyecreate>  I have been keeping an updated version of a package that seems to be unmaintained in the Ubuntu repos in a PPA of mine. I was wondering the process needed to get this package available to the greater Ubuntu community so that others can benefit from the updated software.
[06:16] <Noskcaj> Has someone got time to see if the latest debian revision of blender will build on ubuntu? I lack the hardware and it would be nice if we could have a version that builds for saucy (i know it's late)
[06:26] <Noskcaj> also, what is the process for syncing a debian revision that fixes FTBFS and nothing else? (the package is libswe)
[06:46] <dholbach> good morning
[06:53] <Noskcaj> dholbach, Is there any chance we could sync jwchat? It fixes a installation error. We are currently on -1.1, the current debian revision is -1.3http://ftp-master.metadata.debian.org/changelogs/main/j/jwchat/unstable_changelog
[06:53] <Noskcaj> Or is it better to cherry pick?
[06:54] <Noskcaj> Also, libswe needs syncing, although only one revision up, not the ~10 new ones
[06:56] <dholbach> Noskcaj, for jwchat the changes don't look crazy huge to me
[06:56] <Noskcaj> How do i request a sync since the archive is frozen?
[06:57] <dholbach> just request the sync - whenever it's suitable to get uploaded it should be taken care of
[06:59] <Noskcaj> ok
[13:35] <Rhonda> whaaaaat
[13:49] <Rhonda> Why is there an ubuntu patch in/for wesnoth-1.10 that I didn't notice  :/
[13:50] <Laney> Rhonda: not forwarded?
[14:03] <Rhonda> hmm
[14:04] <Rhonda> Ha
[14:05] <Rhonda> That's fixed in 1.10.7
[14:05] <Rhonda> So a syncpackage should get rid of the ubuntu change, right?
[14:05] <Laney> --force, but yes
[14:05] <Laney> it'll tell you off otherwise