[00:07] -queuebot:#ubuntu-release- Unapproved: sane-backends (zesty-proposed/main) [1.0.25+git20150528-1ubuntu3 => 1.0.25+git20150528-1ubuntu4] (desktop-core, ubuntu-server)
[00:09] <slangasek> jbicha: demoted a few things
[00:15] -queuebot:#ubuntu-release- Unapproved: sane-backends (yakkety-proposed/main) [1.0.25+git20150528-1ubuntu2.16.10.1 => 1.0.25+git20150528-1ubuntu2.16.10.2] (desktop-core, ubuntu-server)
[00:15] -queuebot:#ubuntu-release- Unapproved: sane-backends (xenial-proposed/main) [1.0.25+git20150528-1ubuntu2.16.04.1 => 1.0.25+git20150528-1ubuntu2.16.04.2] (desktop-core, ubuntu-server)
[01:07] <jbicha> thanks
[01:38] <slangasek> does someone want to take ownership of boost1.62, llvm-toolchain-4.0, postgresql-9.6 being in main without a subscriber? :)
[01:55]  * mwhudson gets out his trap-o-meter
[01:57] <jbicha> boost1.61 was ~foundations-bugs
[01:57] <jbicha> postgresql hasn't had a subscriber in recent versions :(
[04:31] -queuebot:#ubuntu-release- Unapproved: gnuplot (zesty-proposed/universe) [5.0.5+dfsg1-5 => 5.0.5+dfsg1-6] (no packageset) (sync)
[04:32] -queuebot:#ubuntu-release- Unapproved: accepted gnuplot [sync] (zesty-proposed) [5.0.5+dfsg1-6]
[05:15] -queuebot:#ubuntu-release- Unapproved: ido (trusty-proposed/main) [13.10.0+14.04.20151021-0ubuntu1 => 13.10.0+14.04.20170403-0ubuntu1] (ubuntu-desktop) (sync)
[05:24] -queuebot:#ubuntu-release- Unapproved: libvpx (zesty-proposed/main) [1.6.1-2 => 1.6.1-3] (kubuntu, ubuntu-desktop) (sync)
[06:45] <caribou> slangasek: sure will do. On that topic, what's the rule on the use of the v-needed/v-done tags wrt release specific tags ? i.e. I've seen verification-needed-trusty & such, why isn't it systematic when the SRU covers multiple releases ?
[07:28] -queuebot:#ubuntu-release- Unapproved: firehol (zesty-proposed/universe) [3.1.1+ds-1 => 3.1.1+ds-1ubuntu1] (no packageset)
[07:28] -queuebot:#ubuntu-release- Unapproved: accepted firehol [source] (zesty-proposed) [3.1.1+ds-1ubuntu1]
[07:36] <tjaalton> xf86-video-armsoc, -omap and xorg want to get to -proposed, and then -freedreno removed for bug 1679323, then the xserver should finally migrate..
[07:37] <tjaalton> *wants
[07:38] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-welcome (zesty-proposed/universe) [17.04.10 => 17.04.11~zesty1.1] (ubuntu-mate)
[07:47] <Trevinho> anyone from the SRU team can unqueue https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text=ido please?
[07:48] <tjaalton> sure
[07:49] <tjaalton> unque as in, release or drop from the queue?-)
[07:54] <tjaalton> Trevinho: ^
[08:03] <flexiondotorg> Could someone please reject ubuntu-mate-welcome/17.04.11~zesty1.1)
[08:03] <flexiondotorg> It was uploaded in error.
[08:05]  * didrocks flushes
[08:06] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-mate-welcome [source] (zesty-proposed) [17.04.11~zesty1.1]
[08:10] <flexiondotorg> didrocks Thank you
[08:12] <didrocks> yw :)
[08:16] -queuebot:#ubuntu-release- Unapproved: rejected xdg-desktop-portal [source] (zesty-proposed) [0.6-0ubuntu1]
[08:16] <Laney> ^- asked for FFe
[08:23] -queuebot:#ubuntu-release- Unapproved: libxmlezout (zesty-proposed/universe) [1.06.1-8 => 1.06.1-8build1] (no packageset)
[08:23] -queuebot:#ubuntu-release- Unapproved: accepted libxmlezout [source] (zesty-proposed) [1.06.1-8build1]
[08:25] -queuebot:#ubuntu-release- Unapproved: libaunit (zesty-proposed/universe) [3.7.2-1build1 => 3.7.2-1build2] (no packageset)
[08:25] -queuebot:#ubuntu-release- Unapproved: libaws (zesty-proposed/universe) [3.3.2-2build3 => 3.3.2-2build4] (no packageset)
[08:26] -queuebot:#ubuntu-release- Unapproved: accepted libaunit [source] (zesty-proposed) [3.7.2-1build2]
[08:26] -queuebot:#ubuntu-release- Unapproved: accepted libaws [source] (zesty-proposed) [3.3.2-2build4]
[08:29] -queuebot:#ubuntu-release- Unapproved: libflorist (zesty-proposed/universe) [2016-1 => 2016-1build1] (no packageset)
[08:29] -queuebot:#ubuntu-release- Unapproved: accepted libflorist [source] (zesty-proposed) [2016-1build1]
[08:30] -queuebot:#ubuntu-release- Unapproved: libgmpada (zesty-proposed/universe) [1.0-3 => 1.0-3build1] (no packageset)
[08:30] -queuebot:#ubuntu-release- Unapproved: accepted libgmpada [source] (zesty-proposed) [1.0-3build1]
[08:31] <Laney> haha
[08:31]  * Laney hopes the ada stuff goes through this time
[08:37] -queuebot:#ubuntu-release- Unapproved: xf86-video-omap (zesty-proposed/universe) [0.4.5-1 => 0.4.5-1build1] (xorg)
[08:38] <tjaalton> ^ this time built against the proper tarball
[08:39] <tjaalton> Laney: so xorg, -omap, -armsoc needs a nudge, and -freedreno removed.. then it'll all migrate
[08:43] -queuebot:#ubuntu-release- Unapproved: libtexttools (zesty-proposed/universe) [2.1.0-8 => 2.1.0-8build1] (no packageset)
[08:43] <Laney> tjaalton: can't help you with freedreno
[08:43] -queuebot:#ubuntu-release- Unapproved: accepted libtexttools [source] (zesty-proposed) [2.1.0-8build1]
[08:44] <tjaalton> no?
[08:44] <Laney> nope
[08:44] -queuebot:#ubuntu-release- Unapproved: accepted xf86-video-armsoc [source] (zesty-proposed) [1.4.1-0ubuntu1]
[08:44] -queuebot:#ubuntu-release- Unapproved: accepted xf86-video-omap [source] (zesty-proposed) [0.4.5-1build1]
[08:45] <tjaalton> not enough powers?
[08:45] <infinity> Laney: Laaaaaaaaaney.
[08:45]  * Laney points to the kryptonite
[08:46]  * Laney stares at infinity but never gets to the end
[08:46] <tjaalton> :)
[08:46] <infinity> Laney: Heh.  Any ideas, based on your extensive knowledge of adt runners, why setcap would fail on armhf (and only armhf)?
[08:47] <infinity> Laney: http://autopkgtest.ubuntu.com/packages/newpid
[08:47] <Laney> Something LXDish that is different in LXC
[08:47] <Laney> s390x is lxc
[08:47] <infinity> Laney: I was about to upload to setcap || setuid, like we do for ping, but... The only reason we do that for ping is because we preinstall it on setcap-incapable filesystems (like tarballs).  newpid should kinda work.
[08:48] <infinity> Though, if lxd is blocking setcap, it might also block chmod u+s
[08:50] <infinity> Laney: Does green->red transition between 2016-08-12 and 2016-11-28 match when armhf went more lxdish?
[08:50] <infinity> Should I be yelling at stgraber instead? :P
[08:50] <infinity> stgraber: No idea what timezone you're in, but hi.
[08:51] <Laney> infinity: Look at the second(?) line of the log for the commandline
[08:51] <Laney> it'll end in -- {lxc,lxd} <stuff>
[08:52] <infinity> Laney: Would help if the last green log wasn't a 404. ;)
[08:52] <Laney> Go to the release it came from
[08:52] <Laney> I guess pitti's script only copies the result but not its log or something
[08:52]  * Laney neither ran nor wrote it :P
[08:53] <infinity> Laney: Ah-ha, yep.  The last two runs in yakkety were lxc=green, lxd=red.
[08:54] <infinity> I'd berate people for not noticing this for 6 months, but I'm one of the people who only just looked. :P
[08:54]  * infinity is on a warpath to actually make glibc autopkgtests completely green instead of just hinting "good enough".
[08:54] <infinity> Which means basically the whole distro needs to be green or hinted yellow.
[08:58] <Laney> I think you can't do file capabilities from non privileged containers
[08:59] <infinity> Possibly.  Can you do setuid?
[08:59] <infinity> I'll ignore that failure for now.
[09:00] <infinity> Oh, joy.  The nss-mdns autopkgtest is pretty much guaranteed to fail when tested against a new glibc.
[09:00] <infinity> Because it attempts things that break with how we pin the triggering packages.
[09:01] <Laney> http://lxc-users.linuxcontainers.narkive.com/IL4g1Y7i/setcap-capabilities
[09:01] <Laney> setuid should work
[09:01] <Laney> and 'autopkgtest --shell-fail -U newpid  -- lxd  autopkgtest/ubuntu/zesty/amd64 -c "raw.lxc=lxc.aa_profile=unconfined" -c "security.privileged=true"' works here
[09:03] <infinity> Kay, maybe I'll do the setuid fallback fix.
[09:03] <Laney> try it without the latter -c at home and see if it works
[09:03] <Laney> that more or less matches production
[09:07] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-welcome (zesty-proposed/universe) [17.04.10 => 17.04.11] (ubuntu-mate)
[09:08] <infinity> Laney: Well, the fallback is correct for other reasons, so meh.
[09:08] <Laney> Yeah
[09:08] <infinity> Laney: http://paste.ubuntu.com/24312212/ <-- Review (since the autoaccept bot will let it through)
[09:08] <Laney> I mean that you can test if it does fall back and work
[09:09] <Laney> sec
[09:14] <Trevinho> tjaalton: I mean, put it in the SRU process...
[09:14] <Laney> Failed to set capabilities on file `/usr/bin/newpid' (Operation not permitted)
[09:14] <Laney> The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
[09:14] <Laney> Setcap failed on /usr/bin/newpid, falling back to setuid
[09:15] <infinity> If that output isn't followed by a non-zero exit, yay?
[09:16] -queuebot:#ubuntu-release- Unapproved: nss-mdns (zesty-proposed/main) [0.10-8 => 0.10-8ubuntu1] (core)
[09:19] -queuebot:#ubuntu-release- Unapproved: opentoken (zesty-proposed/universe) [6.0b-5build1 => 6.0b-5build2] (no packageset)
[09:20] -queuebot:#ubuntu-release- Unapproved: accepted opentoken [source] (zesty-proposed) [6.0b-5build2]
[09:20] <Laney> Yeh, it works
[09:20] <Laney> please to forward?
[09:21] <Laney> nss-mdns could futz with the pinning itself if it wanted
[09:21] <Laney> probably with breaks-testbed
[09:21] <tjaalton> Trevinho: ok, accepted
[09:21] -queuebot:#ubuntu-release- Unapproved: accepted ido [sync] (trusty-proposed) [13.10.0+14.04.20170403-0ubuntu1]
[09:21] <Trevinho> tjaalton: thanks
[09:24] <infinity> Laney: Yeah, the test could be fixed, or the infra could be fixed, but skipping the test is the path of least resistance today.
[09:24] <infinity> Laney: And given the irony that the one package most likely to break an NSS module is glibc, and glibc is the one package that can't be tested against nss-mdns because of this bug...
[09:25] <infinity> Laney: And yes, I'll forward the newpid thing, seems generally correct for Debian too.
[09:26] -queuebot:#ubuntu-release- Unapproved: newpid (zesty-proposed/universe) [7 => 7ubuntu1] (no packageset)
[09:28] -queuebot:#ubuntu-release- Unapproved: accepted newpid [source] (zesty-proposed) [7ubuntu1]
[09:28] <tjaalton> infinity: so could you check bug 1679323, ack xorg and kick x-x-v-freedreno out as it's essentially obsoleted by the new xserver. when you have time that is
[09:45] <infinity> tjaalton: "Essentially obsoleted"... Not sure I like the adjective there. :P
[09:46] <infinity> tjaalton: Oh, but if Rob says so, alright.
[09:46] <infinity> tjaalton: So, no.  Can't remove it until you reupload xorg to remove freedreno from the video-all meta.
[09:47] <infinity> Reverse-Depends
[09:47] <infinity> [09:47] <infinity> * xserver-xorg-video-all        (for xserver-xorg-video-freedreno)
[09:47] <infinity> Packages without architectures listed are reverse-dependencies in: arm64, armhf
[09:47] <tjaalton> infinity: xorg is on the queue
[09:47] <infinity> tjaalton: Oh, lemme look.
[09:50] <rbalint> kees
[09:52] -queuebot:#ubuntu-release- Unapproved: accepted xorg [source] (zesty-proposed) [1:7.7+16ubuntu3]
[09:53] <Laney> quays
[09:54] <rbalint> rbalint: Laney early enter :-)
[10:01] <infinity> rbalint: And now you're talking to yourself?
[10:02] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (zesty-proposed) [2.12-0ubuntu2]
[10:05] -queuebot:#ubuntu-release- Unapproved: suricata (zesty-proposed/universe) [3.2-2ubuntu1 => 3.2-2ubuntu2] (no packageset)
[10:05] -queuebot:#ubuntu-release- Unapproved: accepted suricata [source] (zesty-proposed) [3.2-2ubuntu2]
[10:37] <rbalint> infinity: i thought Laney was referring to my line missing content, but apparently it was not the case
[10:38] <rbalint> infinity: do you still dislike the autopkgtest merge? https://code.launchpad.net/~rbalint/livecd-rootfs/livecd-rootfs-autopkgtest/+merge/321459
[10:40] -queuebot:#ubuntu-release- Unapproved: repowerd (zesty-proposed/main) [2017.02+17.04.20170221-0ubuntu1 => 2017.03+17.04.20170403-0ubuntu1] (ubuntu-desktop) (sync)
[10:43] <acheronuk> Is there a way to roll back to a previous archive version for a package in zesty release?
[10:43] <acheronuk> https://bugs.launchpad.net/ubuntu/+source/choqok/+bug/1667903
[10:45] <acheronuk> someone merged that with debian experimental, and decided to ignore/lower the debian versioned deps against other stuff in experimental we don't have (Qt5 libqoath), so choqok is broken
[10:50] <cjwatson> once it's reached the release pocket, you'd just have to make a new upload reversing the relevant bit of the diff
[10:53] <infinity> rbalint: Honestly not a huge fan, but I've not given it much thought either.
[10:56] -queuebot:#ubuntu-release- Unapproved: notmuch (zesty-proposed/main) [0.23.7-2ubuntu1 => 0.23.7-3ubuntu1] (core)
[10:56] -queuebot:#ubuntu-release- Unapproved: screen (zesty-proposed/main) [4.5.0-4ubuntu1 => 4.5.0-5ubuntu1] (ubuntu-desktop, ubuntu-server)
[10:57] <cjwatson> Could an SRU person have a look at {xenial,yakkety}-proposed/openssh?
[11:02] <acheronuk> cjwatson: well, it was a whole new version ported from Qt4 to Qt5 (v 1.5 - v 1.6), so a new upload like that isn't going to do the job. the Qt5 v1.6 will never work with the Qt4 libqoath we have and that is still needed by other stuff
[11:02] <rbalint> infinity: the problem here is that without autopkgtest the interface to livecd-rootfs is growing undocumented parts
[11:02] <rbalint> like reliance on scripts /build
[11:03] <rbalint> infinity: or relying on ARCH, but not failing if ARCH is not set
[11:03] <rbalint> infinity: i can file those cleanups in a separate merge, but such stuff would creep in again
[11:04] <cjwatson> acheronuk: It's always possible to reverse a change with a new upload, one way or another
[11:04] <cjwatson> Even if the diff might be massive
[11:04] <cjwatson> acheronuk: Anyway, I'm just telling you what's possible; what you do with that information is up to you
[11:05] <acheronuk> cjwatson: would have to version it 1.6 something really1.5 I suppose.
[11:06] <rbalint> infinity: i think autotesting 3 important bootstrap variant is a good compromise on coverage vs. speed
[11:06] <rbalint> infinity: i would build on those changes in minimization
[11:06] <acheronuk> cjwatson: thanks. I'm just asking as I keep getting pinged with the bug emails. it's not in our packages or seeded or really anything for us, so I am not going to spend more time on it.
[11:07] <acheronuk> if the person who did the inappropriate merge wants to, then up to them.
[11:08] <cjwatson> acheronuk: I would certainly recommend putting the person who did the merge on the hook for the breakage they caused
[11:08] <cjwatson> acheronuk: worth contacting them directly about it
[11:09] <acheronuk> cjwatson: ok. I may try that later. thx
[11:26] -queuebot:#ubuntu-release- Unapproved: accepted asterisk [source] (xenial-proposed) [1:13.1.0~dfsg-1.1ubuntu4.1]
[12:43] <handsome_feng> Hi, could someone help me to approve the ubuntukylin-theme in upload queue?
[12:45] <tjaalton> infinity: ok, _now_ you can purge -freedreno, everything else is ready
[12:46] <cyphermox> ^ as handsome_feng points out; there is ubuntukylin-theme and ubiquity-slideshow-ubuntu which are fixes for Ubuntu Kylin which should be pretty straightforward if someone has time to review them
[12:49] -queuebot:#ubuntu-release- Unapproved: libx11 (zesty-proposed/main) [2:1.6.3-1ubuntu3 => 2:1.6.4-3] (core, xorg) (sync)
[12:49] <infinity> cyphermox: Define "straightforward".
[12:50] <infinity> 317KB diffs don't usually qualify.
[12:50] -queuebot:#ubuntu-release- Unapproved: ipset (zesty-proposed/main) [6.30-2 => 6.30-2ubuntu1] (ubuntu-server)
[12:50] -queuebot:#ubuntu-release- Unapproved: percona-xtrabackup (xenial-proposed/universe) [2.3.7-0ubuntu0.16.04.1 => 2.3.7-0ubuntu0.16.04.2] (no packageset) (sync)
[12:50] -queuebot:#ubuntu-release- Unapproved: percona-xtrabackup (zesty-proposed/universe) [2.3.7-0ubuntu1 => 2.3.7-0ubuntu2] (no packageset) (sync)
[12:50] <cyphermox> infinity: I haven't look at ubuntukylin-theme, but it's a theme, CSS and icons probably
[12:51] -queuebot:#ubuntu-release- Unapproved: percona-xtrabackup (yakkety-proposed/universe) [2.3.7-0ubuntu0.16.10.1 => 2.3.7-0ubuntu0.16.10.2] (no packageset) (sync)
[12:51] <cyphermox> and the slideshow is a translation fix for my derp moment.
[12:52] -queuebot:#ubuntu-release- Unapproved: accepted percona-xtrabackup [sync] (zesty-proposed) [2.3.7-0ubuntu2]
[12:52] -queuebot:#ubuntu-release- Unapproved: accepted ipset [source] (zesty-proposed) [6.30-2ubuntu1]
[12:52] <tjaalton> ^ libx11 there fixes CVE's, also builds fine with w3m so can be synced
[12:52] <handsome_feng> infinity: The ubuntukylin-theme has added the support for UKUI, without this, the Desktop will be very ugly...
[12:55] <mterry> Can we get promotions for unity-scope-mediascanner and mediascanner2?  They have approved MIRs and an FFe
[12:58] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity-slideshow-ubuntu [source] (zesty-proposed) [123]
[12:59] <infinity> tjaalton: It doesn't seem obvious from the Debian changelog that the Ubuntu delta isn't necessary anymore.
[12:59] <tjaalton> infinity: the patches that we carried are included upstream
[13:00] <tjaalton> and builds fine even with w3m
[13:01] <tjaalton> but it's in universe, that shouldn't be a problem for build-deps?
[13:01] <tjaalton> it just generates some documentation or such
[13:02] <infinity> Build-deps in universe are fine.
[13:03] -queuebot:#ubuntu-release- Unapproved: accepted libx11 [sync] (zesty-proposed) [2:1.6.4-3]
[13:04] <tjaalton> sweet
[13:05] <tjaalton> there's mesa point-release too, some 30+ bugfixes backported from master
[13:08] <tjaalton> https://lists.freedesktop.org/archives/mesa-dev/2017-April/150466.html
[13:23] <jbicha> hi, any Archive Admin have time to review switcheroo-control for zesty (new) ? LP: #1671828
[13:26] <tjaalton> sounds like a useful addition
[13:27] <tjaalton> debian NEW processing is slow now during the freeze :/
[13:27] <jbicha> KDE iimplemented the same basic thing themselves but I think the hope was that it would be useful for other desktops too
[13:29] <jbicha> tjaalton: would you be interested in sponsoring it into Debian (I'm just a DM)?
[13:29] <tjaalton> ah, sure
[13:29] <tjaalton> I thought it was just sitting on the queue there too
[13:30] <jbicha> well, the Debian GNOME team hasn't gotten around to GNOME 3.24 yet
[13:31] <jbicha> tjaalton: did you want to maintain it in the Debian X team instead? I believe the upstream developer considers it basically feature complete so he doesn't anticipate it changing much from now on
[13:31] <tjaalton> well doesn't matter much
[13:31] <tjaalton> you can have it :)
[13:32] <jbicha> ok, packaging is at https://anonscm.debian.org/git/pkg-gnome/switcheroo-control.git/
[13:33] <tjaalton> not finalized
[13:35] <jbicha> tjaalton: done
[13:43] <tjaalton> jbicha: thanks, uploaded
[13:54] <jamespage> if there is a sru team member around, I have openvswitch updates for xenial and yakkety queued up in the UNAPPROVED queue that I'd quite like to include in this months OpenStack update cycle
[13:54] <jamespage> (they show up as syncs as I did them both via bileto)
[14:02] -queuebot:#ubuntu-release- New sync: cockpit (zesty-proposed/primary) [134-1]
[14:14] -queuebot:#ubuntu-release- Unapproved: boinc (zesty-proposed/universe) [7.6.33+dfsg-10 => 7.6.33+dfsg-11] (no packageset) (sync)
[14:16] -queuebot:#ubuntu-release- Unapproved: accepted boinc [sync] (zesty-proposed) [7.6.33+dfsg-11]
[14:24] <pmcgowan> can anyone help with these FFEs bug #1676436 bug #1677263 and bug #1677242
[14:24] -queuebot:#ubuntu-release- Unapproved: grub2 (zesty-proposed/main) [2.02~beta3-4ubuntu1 => 2.02~beta3-4ubuntu2] (core)
[14:30] -queuebot:#ubuntu-release- Unapproved: grub2-signed (zesty-proposed/main) [1.79 => 1.80] (core)
[14:31] <cyphermox> slangasek: infinity: ^ this grub2/grub2-signed is for the enforcing EFI image with only 'linuxefi'.
[14:32] <cjwatson> Did you just remove the obvious patch?
[14:32] <cyphermox> cjwatson: no, because we didn't want to just flip the switch for everyone.
[14:33] <cjwatson> Oh, I see
[14:33] <cjwatson> Interesting
[14:33] <cyphermox> cjwatson: also, I thought it was more a matter of dropping the place where the linuxefi patch wipes out the err, and then falls back to linux?
[14:33] <cjwatson> see debian/patches/linuxefi_non_sb_fallback.patch
[14:33] <cyphermox> (but when I looked Friday, I couldn't find that bit anymroe)
[14:34] <cjwatson> Shipping without the linux module surely won't work well for cases where you need more than hand-written grub.cfg files
[14:34] <cjwatson> Because the standard grub-mkconfig machinery expects linux to exists
[14:34] <cjwatson> *exist
[14:34] <cyphermox> cjwatson: right
[14:35] <cyphermox> cjwatson: this is for a special case where we'll use linuxefi directly.
[14:35] <cjwatson> Are you planning to flip the switch for everyone eventually?
[14:35] <cyphermox> yes
[14:35] <cjwatson> OK, good
[14:35] <cjwatson> The other tactic I can think of would be some kind of one-way-settable variable that switches to enforce mode
[14:35] <cyphermox> cjwatson: in that case it *will* use linux to go hand off to linuxefi, I think
[14:36] <cyphermox> yeah
[14:36] <cjwatson> Then you could set that in an embedded config file
[14:36] <infinity> cyphermox: I will only look at grub if you figure out WTF is wrong with nplan's autopkgtests.
[14:37] <cyphermox> cjwatson: the idea for now was to do this with the smallest effort possible, but it still took me a day and half to get together, at least to test that things weren't just blowing up
[14:37] <cyphermox> cjwatson: my vision for the global flag day of eforcing Secure Boot was to remove that second grub_errno = GRUB_ERR_NONE; line from the patch
[14:37] <slangasek> caribou: v-done implies verified for all releases; if you're only doing one at a time you can use the v-done-$release tags
[14:38] <caribou> slangasek: ah, ok. I've seen a few cases where the tag v-needed-$release appeared in the bug
[14:41] <cyphermox> infinity: sure, I'll upload just autopkgtest fixes in a few minutes
[14:41] <cjwatson> cyphermox: oh, right, I thought I had that as a separate patch at one point but perhaps not.  Your suggestion is in the right area but not quite correct: you need to replace that line with "goto fail;"
[14:42] <cyphermox> cjwatson: oh, indeed
[14:42] <cjwatson> but yeah, small change
[14:42] <cjwatson> cyphermox: if at some point you can help me work out when it's safe to enforce that in Debian, that would be good
[14:43] <cyphermox> cjwatson: for now we're waiting for the shim review
[14:44] <cyphermox> cjwatson: let's discuss that on OFTC though?
[14:44] <cjwatson> sure (and also probably not right now)
[14:44] <cyphermox> yep
[14:45] -queuebot:#ubuntu-release- Unapproved: gtkglext (zesty-proposed/universe) [1.2.0-3.2fakesync1ubuntu1 => 1.2.0-6] (kubuntu) (sync)
[14:47] -queuebot:#ubuntu-release- Unapproved: accepted nss-mdns [source] (zesty-proposed) [0.10-8ubuntu1]
[14:47] <mapreri> could somebody please process libosl from NEW?
[14:47] <mapreri> (process as in _accept_ ;))
[14:48] <stgraber> infinity: we can't yet use setcap in unprivileged containers because the kernel doesn't implement unprivileged fs caps
[14:48] <stgraber> infinity: hallyn wrote a kernel patch for that but we're still waiting for it to hit linus' tree
[14:48] <infinity> stgraber: Yeah, Laney found an upstream bug with hallyn's comments on the matter.
[14:48] <infinity> stgraber: So, I fixed the package to fall back to suid.
[14:48] -queuebot:#ubuntu-release- New: accepted libosl [amd64] (zesty-proposed) [0.8.0-1.1]
[14:50] -queuebot:#ubuntu-release- New: accepted rpi.gpio [arm64] (zesty-proposed) [0.6.3-1ubuntu1]
[14:50] -queuebot:#ubuntu-release- New: accepted rpi.gpio [armhf] (zesty-proposed) [0.6.3-1ubuntu1]
[14:50] <mapreri> thanks!
[14:50] -queuebot:#ubuntu-release- New: accepted cockpit [sync] (zesty-proposed) [134-1]
[14:50] -queuebot:#ubuntu-release- New: accepted telegram-desktop [sync] (zesty-proposed) [1.0.14-1]
[14:55] -queuebot:#ubuntu-release- New binary: cockpit [ppc64el] (zesty-proposed/none) [134-1] (no packageset)
[14:55] -queuebot:#ubuntu-release- New binary: cockpit [s390x] (zesty-proposed/none) [134-1] (no packageset)
[14:56] -queuebot:#ubuntu-release- Unapproved: miral (zesty-proposed/main) [1.3.1+17.04.20170316.1-0ubuntu1 => 1.3.2+17.04.20170330.5-0ubuntu1] (ubuntu-desktop) (sync)
[14:57] -queuebot:#ubuntu-release- Unapproved: accepted openvswitch [sync] (yakkety-proposed) [2.6.1-0ubuntu0.16.10.1]
[14:57] -queuebot:#ubuntu-release- New binary: cockpit [i386] (zesty-proposed/none) [134-1] (no packageset)
[14:58] -queuebot:#ubuntu-release- New binary: cockpit [amd64] (zesty-proposed/none) [134-1] (no packageset)
[15:00] -queuebot:#ubuntu-release- New binary: cockpit [arm64] (zesty-proposed/none) [134-1] (no packageset)
[15:01] <tjaalton> infinity: sorry for pestering you, again, but x-x-v-freedreno can go now, and xserver 1.19 should finally be unleashed to the masses..
[15:01] <infinity> tjaalton: I know.  I've been waiting for tools to agree.
[15:01] <tjaalton> oh.. sorry
[15:07] -queuebot:#ubuntu-release- Unapproved: gpsshogi (zesty-proposed/universe) [0.7.0-1.1 => 0.7.0-1.1build1] (no packageset)
[15:09] -queuebot:#ubuntu-release- Unapproved: accepted gpsshogi [source] (zesty-proposed) [0.7.0-1.1build1]
[15:14] <infinity> cjwatson, cyphermox: So, what was the outcome of that spontaenous grub discussion?  Does the one in the queue need more love?
[15:14] <cjwatson> I don't see anything obviously wrong
[15:15] <infinity> cjwatson: Feel free to put your release hat back on and review/process. :P
[15:17] -queuebot:#ubuntu-release- Unapproved: accepted screen [source] (zesty-proposed) [4.5.0-5ubuntu1]
[15:17] <infinity> Oh, maybe I should have looked at the diff first. :P
[15:17] <infinity> cyphermox: So, that's super simple.  Was the previous assertion that removing the linux module would remove the "linux" command from grub.cfg total BS then?
[15:18] <cyphermox> the what?
[15:18] <infinity> (ie: linuxefi and linux both provide the command, in some order of precedence)
[15:18] <cyphermox> if you remove the 'linux' module, you remove the 'linux' command. linuxefi provides the 'linuxefi' command
[15:18] <infinity> cyphermox: There was a concern that "just remove the linux module" would also lead to "linux" commands in grub.cfg not doing a thing.
[15:18] <infinity> cyphermox: Okay.  Then this isn't what Steve wanted?
[15:18] <cyphermox> this works as intended, and to be useful we also need to change grub.cfg
[15:19] <cyphermox> infinity: he revised his position.
[15:19] <infinity> cyphermox: Which is exactly what he said he didn't want when we all discussed this.  Did that opinion chan--- Okay.
[15:19] <cjwatson> FWIW I don't think changing grub.cfg is a good thing, except in hardcoded situations like images
[15:19] <cyphermox> for this particular use case, it'd fine to modify grub.cfg.
[15:20] <cjwatson> I was led to believe by cyphermox above that this is only for use in hardcoded situations
[15:20] <cyphermox> it's hardcoded in an image creation process, and we can change it and re-spin those images to start enforcing.
[15:20] <cyphermox> the image needs to be modified anyway to include the new EFI binary.
[15:21] <infinity> Except that grub.cfg is written by snapd.
[15:21] <Odd_Bloke> slangasek: infinity: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1679252 could really do with some attention; it's currently breaking image builds. :(
[15:21] <infinity> But I guess if you're fine sedding the crap out of it after, then meh.
[15:21] <infinity> Odd_Bloke: Will look.
[15:22] <Odd_Bloke> infinity: Thanks; it'll look familiar as a bug you've already fixed in trunk (several months ago ¬.¬).
[15:23] <cyphermox> infinity: slangasek was fine with this process in a private discussion; I'm not the one who will be making the snap changes.
[15:23] <cyphermox> infinity: I would argue that even so, providing our users a way to do enforcing of Secure Boot (even if manually) is a net gain.
[15:24] <cyphermox> I thought you weren't going to review until I fixed netplan? :)
[15:24] -queuebot:#ubuntu-release- Unapproved: eancheck (zesty-proposed/universe) [1.0-1.1ubuntu1 => 1.0-2] (no packageset) (sync)
[15:25] <cyphermox> (fwiw, fix is being tested in autopkgtest here right now)
[15:25] -queuebot:#ubuntu-release- Unapproved: accepted eancheck [sync] (zesty-proposed) [1.0-2]
[15:28] -queuebot:#ubuntu-release- New binary: telegram-desktop [amd64] (zesty-proposed/universe) [1.0.14-1] (no packageset)
[15:29] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.9 => 2.408.10] (desktop-core)
[15:31] -queuebot:#ubuntu-release- Unapproved: url-dispatcher (zesty-proposed/main) [0.1+17.04.20170318-0ubuntu1 => 0.1+17.04.20170328-0ubuntu1] (ubuntu-desktop) (sync)
[15:33] <slangasek> infinity: yes, in further discussion with cyphermox, we agreed that removing the 'linux' module, and fixing up the grub.cfg of the affected gadget to use 'linuxefi'+'initrdefi', is the safest thing we can accomplish quickly
[15:34] <slangasek> infinity: and had the nice side effect that you will wind up using the EFI entry point even on systems without SB enabled, which currently does not happen, which is a bug ;)
[15:34] <infinity> slangasek: Fair enough.
[15:36] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.10]
[15:36] -queuebot:#ubuntu-release- Unapproved: indicator-location (zesty-proposed/universe) [13.10.0+17.04.20170210-0ubuntu2 => 13.10.0+17.04.20170330.3-0ubuntu1] (no packageset) (sync)
[15:37] -queuebot:#ubuntu-release- Unapproved: accepted indicator-location [sync] (zesty-proposed) [13.10.0+17.04.20170330.3-0ubuntu1]
[15:45]  * ogra glares at bug 1679252 and wonders how often we have fixed this in the last 6 years
[15:53] <infinity> ogra: Once or twice, perhaps. :P
[15:53] <ogra> at least :P
[15:54] <slangasek> Odd_Bloke: did LP: #1679252 also need fixing in yakkety?
[15:54] <slangasek> better said: does it affect yakkety? if so it needs fixing there
[15:54] <infinity> slangasek: No, his cherry-pick was a commit I made in yakkety.
[15:54] <slangasek> ok
[15:58] -queuebot:#ubuntu-release- Unapproved: gpsshogi (zesty-proposed/universe) [0.7.0-1.1build1 => 0.7.0-1.1build2] (no packageset)
[15:58] <mapreri> ↑ sorry, first upload was apparently too early to actually build against the just-accepted libosl1v5…
[15:58] <bdmurray> robru: Is there something wrong or can I not see the difference in the urls here? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2691
[15:59] -queuebot:#ubuntu-release- Unapproved: accepted gpsshogi [source] (zesty-proposed) [0.7.0-1.1build2]
[16:00] <robru> bdmurray: looks fine to me. Look at the filenames
[16:01] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-keyboard [sync] (zesty-proposed) [0.100+17.04.20170320-0ubuntu1]
[16:02] <bdmurray> robru: ah, maybe a header would help? [xenial] diff, diff [yakkety] diff, diff?
[16:03] <robru> bdmurray: it's the same information on the ticket: https://bileto.ubuntu.com/#/ticket/2691 is it easier to read there?
[16:04] -queuebot:#ubuntu-release- Unapproved: rejected gtk-doc [source] (zesty-proposed) [1.25-7ubuntu1]
[16:05] <bdmurray> robru: yes, maybe because the text isn't so long.
[16:06] <robru> bdmurray: yeah, unfortunately that ppa description field doesn't allow html so you just get a dump of links. They're sorted alphabetically so devel series will always be at the bottom
[16:06] <robru> er, until A opens ;-)
[16:07] -queuebot:#ubuntu-release- Unapproved: accepted percona-xtrabackup [sync] (yakkety-proposed) [2.3.7-0ubuntu0.16.10.2]
[16:07] <muktupavels> can someone review gtk+3 in xenial, please?
[16:09] <Laney> Do rejection mails for silo copies get to a human these days?
[16:09] -queuebot:#ubuntu-release- Unapproved: accepted percona-xtrabackup [sync] (xenial-proposed) [2.3.7-0ubuntu0.16.04.2]
[16:09] <infinity> Laney: I'm not convinced humans read them, no.
[16:10] <infinity> Laney: On the plus side, that means you can curse.
[16:10] <Laney> hocus pocus
[16:12] <robru> Laney: are you referring to libertine?
[16:13] <apw> Laney, don't tell 'em that is no fun :)
[16:13] <Laney> robru: Nope.
[16:13] -queuebot:#ubuntu-release- Unapproved: accepted openvswitch [sync] (xenial-proposed) [2.5.2-0ubuntu0.16.04.1]
[16:13] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (zesty-proposed) [2.02~beta3-4ubuntu2]
[16:13] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (zesty-proposed) [1.80]
[16:13] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-terminal-app [sync] (zesty-proposed) [0.7.218+17.04.20170328.3-0ubuntu1]
[16:14] <robru> alright then
[16:14] <slangasek> did maas commit some offense to get itself left in the queue for 7 days?
[16:15] <Laney> apw: I wrote it on a piece of paper, encrypted it, burnt it and buried the ashes at sea
[16:15] <slangasek> I mean, besides filing a request for standing FFe that was not acked, and that the maas team subsequently closed in their own upload ;)
[16:15] <slangasek> Laney, infinity: ^^ ?
[16:16] <infinity> slangasek: I feel like you answered your own question.
[16:16] <slangasek> infinity: but no one has reviewed the upload and had specific exceptions?
[16:17] <infinity> slangasek: Can't speak for others, but I've just not found the time.
[16:18] <Laney> I put it off when I saw the FFe wasn't going to be approved and then never went back to it
[16:19] <Laney> Feel free
[16:19] <Laney> The ubuntukylin theme is similar
[16:20] -queuebot:#ubuntu-release- Unapproved: accepted notmuch [source] (zesty-proposed) [0.23.7-3ubuntu1]
[16:20] <apw> slangasek, for me i saw the below and meant to ask security about it:
[16:20] <apw> +maas ALL= NOPASSWD: /usr/lib/maas/maas-delete-file
[16:20] <apw> +maas ALL= NOPASSWD: /usr/lib/maas/maas-write-file
[16:22] <jbicha> Laney: ubuntukylin-theme is just a UIF break, right? and UIF doesn't necessarily apply to flavors that don't really have docs? (I don't know if Kylin has docs)
[16:22] -queuebot:#ubuntu-release- Unapproved: accepted libgpod [sync] (zesty-proposed) [0.8.3-8.1]
[16:22] -queuebot:#ubuntu-release- Unapproved: accepted seahorse [sync] (zesty-proposed) [3.20.0-3.1]
[16:22] <apw> Laney, that is suitibly protected indeed
[16:23] <Laney> jbicha: Dunno, the changelog implies it adds an icon theme and maybe a new gtk theme so I feel it warrants some review
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-hwe to kernel in xenial
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-hwe-edge to kernel in xenial
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-meta-hwe to kernel in xenial
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-meta-hwe-edge to kernel in xenial
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-signed-hwe to kernel in xenial
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-signed-hwe-edge to kernel in xenial
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-hwe to kernel in yakkety
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-hwe-edge to kernel in yakkety
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-meta-hwe to kernel in yakkety
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-meta-hwe-edge to kernel in yakkety
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-signed-hwe to kernel in yakkety
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-signed-hwe-edge to kernel in yakkety
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-hwe to kernel in zesty
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-hwe-edge to kernel in zesty
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-meta-hwe to kernel in zesty
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-meta-hwe-edge to kernel in zesty
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-signed-hwe to kernel in zesty
[16:23] -queuebot:#ubuntu-release- Packageset: Added linux-signed-hwe-edge to kernel in zesty
[16:24] -queuebot:#ubuntu-release- Unapproved: calligra (zesty-proposed/universe) [1:3.0.0.1-0ubuntu3 => 1:3.0.1-0ubuntu1] (kubuntu)
[16:24] <jbicha> ok, makes sense
[16:24] <Laney> I would definitely prefer someone else to look. :)
[16:24] <slangasek> Laney: "wasn't going to be approved"?  It wasn't commented on at all in LP, and I guess you could have approved it? :)
[16:24] <Laney> slangasek: oops, s/going to be//
[16:24] <slangasek> apw: right, seems worth giving security a heads-up about that, but I don't think that's an FFe matter
[16:25] <slangasek> Laney: k
[16:25] <apw> slangasek, and i have just done tha
[16:25] -queuebot:#ubuntu-release- Unapproved: grub2 (zesty-proposed/main) [2.02~beta3-4ubuntu2 => 2.02~beta3-4ubuntu2] (core)
[16:25] <slangasek> apw: cool
[16:26] <slangasek> infinity: unless you tell me that accepting this is going to delay server image mastering, I'll accept it now
[16:27] <jbicha> apw: hi, do you think you'll have time to review switcheroo-control (new) for zesty? (it was just uploaded to Debian new today, my fault for not looking for a sponsor there sooner)
[16:27] <infinity> slangasek: I'm a bit puzzled by your response to apw.  Sure, "it might be scary" doesn't relate to feature freeze, but queue reviews at this point in time are useful on many fronts, we don't just blindly review for "no new features, but these new bugs are okay".
[16:28] <infinity> slangasek: Also, an FFe that doesn't seem to have an ACK doesn't go away because the uploader closed the bug, surely. :P
[16:29] <infinity> s/FFe/FFe request/
[16:30] <slangasek> infinity: yes, this is a point that you and I have a different philosophy on; I don't consider it the purpose of release freeze queue reviews to prevent all bugs, only to prevent those bugs that could conceivably be considered blockers for the release
[16:30] <slangasek> infinity: and once the archive is frozen, as far as I'm concerned an upload to the archive is equivalent to an FFe request and the exception can be granted in-line by hitting 'accept' :)
[16:31] <infinity> slangasek: Perhaps, though documenting that in the bug so the next review has precedence to refer to would be nice.
[16:33] <infinity> slangasek: If you're inclined to accept the FFe, fine.  We absolutely disagree on queue reviews, I suspect.  "That won't be a release blocker, but enjoy SRUing fixes later for this bug I found" seems like a silly statement.  And "enjoy the pending CVE" is even worse. :P
[16:33] <infinity> (Not that this will be a security issue, but the concern that maybe it could use a security review is valid)
[16:35] -queuebot:#ubuntu-release- Unapproved: accepted gtkglext [sync] (zesty-proposed) [1.2.0-6]
[16:36] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (zesty-proposed) [2.02~beta3-4ubuntu2]
[16:51] -queuebot:#ubuntu-release- Unapproved: acme-tiny (zesty-proposed/universe) [20160801-1 => 20160801-3] (no packageset) (sync)
[16:51] -queuebot:#ubuntu-release- Unapproved: accepted acme-tiny [sync] (zesty-proposed) [20160801-3]
[16:59] <Laney> I left mesa because its changelog is lacking and there's no NEWS or anything and it's quite big
[16:59] <Laney> Someone else please review :)
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted apt-xapian-index [source] (zesty-proposed) [0.47ubuntu12]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted erlang [source] (zesty-proposed) [1:19.2.1+dfsg-2ubuntu1]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted k3b [source] (zesty-proposed) [2.0.3a+git20170325-0ubuntu1]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted miral [sync] (zesty-proposed) [1.3.2+17.04.20170330.5-0ubuntu1]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted repowerd [sync] (zesty-proposed) [2017.03+17.04.20170403-0ubuntu1]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-welcome [source] (zesty-proposed) [17.04.11]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted url-dispatcher [sync] (zesty-proposed) [0.1+17.04.20170328-0ubuntu1]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted calligra [source] (zesty-proposed) [1:3.0.1-0ubuntu1]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted libvpx [sync] (zesty-proposed) [1.6.1-3]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted sane-backends [source] (zesty-proposed) [1.0.25+git20150528-1ubuntu4]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted flatpak [sync] (zesty-proposed) [0.8.5-1]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted unity-gtk-module [sync] (zesty-proposed) [0.0.0+17.04.20170403-0ubuntu1]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted opencv [sync] (zesty-proposed) [2.4.9.1+dfsg1-2]
[17:01] <slangasek> infinity: given that it's a package that has a stable release exception (which someone could maybe document the parameters of ;), I'm sure they will enjoy SRUing fixes later in this case!  But also, all the security bugs that we *didn't* find, because they were uploaded before the freeze and therefore weren't presented in the diff, would still be there no matter what.  Which is why I don't like
[17:01] <slangasek> using queue review to block based on issues that don't have a direct release impact
[17:03] <Laney> I should have said "... and I've got to go now" - night!
[17:04] -queuebot:#ubuntu-release- Unapproved: grub2 (zesty-proposed/main) [2.02~beta3-4ubuntu2 => 2.02~beta3-4ubuntu2] (core)
[17:10] <barry> slangasek: do we need to do anything else to drop xapian1.3-bindings from zesty?
[17:10] <slangasek> barry: did apt-xapian-index land or is it in the queue?
[17:10] -queuebot:#ubuntu-release- Unapproved: python-django (zesty-proposed/main) [1.8.7-1ubuntu10 => 1.8.7-1ubuntu11] (ubuntu-server)
[17:11] <barry> slangasek: it just got approved.  after that lands, is there anything else?
[17:11] <slangasek> barry: ah, it's been accepted -ok. nope, that's the only thing
[17:11] <barry> slangasek: cool, thanks
[17:32] <rbalint> I'm looking at http://people.canonical.com/~ubuntu-archive/proposed-migration/zesty/update_excuses.html and i don't get why clamav does not migrate
[17:33] <rbalint> it says: libclamav7/amd64 unsatisfiable Depends: libtfm1 (>= 0.13)
[17:33] <rbalint> while libtfm is 0.13-4 is there in zesty
[17:36] <jbicha> rbalint: it looks like libtfm1 needs to be promoted to main LP: #1619239
[17:39] <rbalint> jbicha: thanks
[17:39] <rbalint> makes sense that way
[17:40] <jbicha> the "unsatisfiable depends" is a common confusing message that often means you have something in main depending on something in universe
[17:43] <rbalint> jbicha: from the bug it looks like it is ready to be promoted to main
[17:44] <rbalint> jbicha: is there anyone who i should ping about that?
[17:45] <jbicha> you're asking in the right place so I'd just wait a bit for the right person to read this conversation :)
[17:46]  * rbalint patiently waiting :-)
[17:47] <rbalint> this could unblock another package LP: #1679769
[17:54] <bdmurray> If my dad has two brothers how many siblings does he have?
[18:04] -queuebot:#ubuntu-release- Unapproved: epiphany-browser (zesty-proposed/universe) [3.24.0-0ubuntu1 => 3.24.0-0ubuntu2] (desktop-extra)
[18:35] -queuebot:#ubuntu-release- Unapproved: gtk+3.0 (zesty-proposed/main) [3.22.11-0ubuntu2 => 3.22.11-0ubuntu3] (ubuntu-desktop)
[18:39] <rbalint> another binary package not built anymore LP: #1679792
[18:50] <jbicha> rbalint: I believe mongodb 3.4 is blocked in zesty because it ftbfs on arm64
[18:51] <jbicha> it builds in Debian though https://buildd.debian.org/status/package.php?p=mongodb&suite=experimental
[18:53] <rbalint> jbicha: true, i'm looking into the failure as well
[19:32] -queuebot:#ubuntu-release- Unapproved: devscripts (zesty-proposed/main) [2.16.8ubuntu1 => 2.16.8ubuntu2] (core)
[19:49] -queuebot:#ubuntu-release- New: accepted ibm-java80 [amd64] (xenial-proposed) [8.0.4.1-0ubuntu1]
[19:49] -queuebot:#ubuntu-release- New: accepted ibm-java80 [ppc64el] (xenial-proposed) [8.0.4.1-0ubuntu1]
[19:49] -queuebot:#ubuntu-release- New: accepted ibm-java80 [i386] (xenial-proposed) [8.0.4.1-0ubuntu1]
[19:49] -queuebot:#ubuntu-release- New: accepted ibm-java80 [s390x] (xenial-proposed) [8.0.4.1-0ubuntu1]
[21:14] <jbicha> yay, switcheroo-control made it through the Debian new queue very quickly so I'll just sync it in a few hours
[21:26] -queuebot:#ubuntu-release- Unapproved: tmux (zesty-proposed/main) [2.3-4 => 2.3-4ubuntu1] (ubuntu-desktop, ubuntu-server)
[21:30] -queuebot:#ubuntu-release- Unapproved: netcfg (zesty-proposed/main) [1.138ubuntu4 => 1.138ubuntu5] (core)
[21:37] <tjaalton> jbicha: oh wow
[21:55] <barry> coreycb: ping re LP: #1679837
[21:59] <barry> fwiw, i think we should just syncpackage python-eventlet from unstable and drop the ubuntu delta
[22:18] <coreycb> barry, that'd be fine with me
[22:19] <coreycb> barry, looks like we were just skipping a test, so maybe that's working now
[22:20] <barry> coreycb: cool.  i'll sync it now then i'm eod
[22:20] <coreycb> barry, ok thanks
[22:20] <barry> cheers
[22:22] -queuebot:#ubuntu-release- Unapproved: python-eventlet (zesty-proposed/main) [0.19.0-2ubuntu1 => 0.19.0-6] (openstack, ubuntu-server) (sync)
[22:37] -queuebot:#ubuntu-release- Unapproved: lightdm (zesty-proposed/main) [1.22.0-0ubuntu1 => 1.22.0-0ubuntu2] (kubuntu, ubuntu-desktop)
[23:20] -queuebot:#ubuntu-release- Unapproved: mate-utils (zesty-proposed/universe) [1.18.0-0ubuntu1 => 1.18.1-0ubuntu1] (ubuntu-mate)
[23:23] -queuebot:#ubuntu-release- Unapproved: caja (zesty-proposed/universe) [1.18.0-0ubuntu1 => 1.18.1-0ubuntu1] (ubuntu-mate)
[23:24] -queuebot:#ubuntu-release- Unapproved: pluma (zesty-proposed/universe) [1.18.0-0ubuntu1 => 1.18.1-0ubuntu1] (ubuntu-mate)
[23:26] -queuebot:#ubuntu-release- Unapproved: mate-icon-theme (zesty-proposed/universe) [1.18.0-0ubuntu1 => 1.18.1-0ubuntu1] (ubuntu-mate)
[23:27] -queuebot:#ubuntu-release- Unapproved: mate-sensors-applet (zesty-proposed/universe) [1.18.0-0ubuntu1 => 1.18.1-0ubuntu1] (ubuntu-mate)
[23:27] -queuebot:#ubuntu-release- Unapproved: mate-settings-daemon (zesty-proposed/universe) [1.18.0-0ubuntu2 => 1.18.1-0ubuntu1] (ubuntu-mate, ubuntukylin)
[23:28] -queuebot:#ubuntu-release- Unapproved: engrampa (zesty-proposed/universe) [1.18.0-0ubuntu1 => 1.18.1-0ubuntu1] (ubuntu-mate)
[23:37] -queuebot:#ubuntu-release- Unapproved: phpmyadmin (zesty-proposed/universe) [4:4.6.6-2 => 4:4.6.6-3] (no packageset) (sync)
[23:38] -queuebot:#ubuntu-release- Unapproved: accepted phpmyadmin [sync] (zesty-proposed) [4:4.6.6-3]
[23:40] -queuebot:#ubuntu-release- Unapproved: qmidiarp (zesty-proposed/universe) [0.6.4-1 => 0.6.4-2] (ubuntustudio) (sync)
[23:40] -queuebot:#ubuntu-release- Unapproved: tryton-server (zesty-proposed/universe) [4.2.1-1 => 4.2.1-2] (no packageset) (sync)
[23:40] -queuebot:#ubuntu-release- Unapproved: accepted tryton-server [sync] (zesty-proposed) [4.2.1-2]
[23:41] -queuebot:#ubuntu-release- Unapproved: ciphersaber (zesty-proposed/universe) [1.01-2ubuntu1 => 1.01-2.1] (no packageset) (sync)
[23:43] -queuebot:#ubuntu-release- Unapproved: accepted ciphersaber [sync] (zesty-proposed) [1.01-2.1]
[23:50] -queuebot:#ubuntu-release- Unapproved: click-apparmor (zesty-proposed/main) [0.3.17 => 0.3.18] (ubuntu-desktop)
[23:50] -queuebot:#ubuntu-release- Unapproved: accepted click-apparmor [source] (zesty-proposed) [0.3.18]