[00:00] -queuebot:#ubuntu-release- Unapproved: shim-signed (yakkety-proposed/main) [1.27~16.10.1 => 1.28~16.04.1] (core)
[00:07] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [source] (yakkety-proposed) [1.28~16.04.1]
[00:55] <handsome_feng> Hi, Could anyone help approving ubuntukylin-theme? FinalFreeze is coming... Thank you in advance!
[01:37] <tsimonq2> Hey handsome_feng :)
[01:37] <handsome_feng> Hi, tsimonq2 :)
[01:38] <tsimonq2> handsome_feng: Unfortunately I don't have the access, I just wanted to say hi ;)
[01:38] -queuebot:#ubuntu-release- Unapproved: shim-signed (xenial-proposed/main) [1.27~16.04.1 => 1.28~16.04.1] (core)
[01:39] <handsome_feng> hehe... Thanks anyway !
[01:43] <Bashing-om> \
[04:41] -queuebot:#ubuntu-release- Unapproved: accepted eom [source] (zesty-proposed) [1.18.1-0ubuntu1]
[04:42] -queuebot:#ubuntu-release- Unapproved: accepted gnome-terminal [source] (zesty-proposed) [3.20.2-1ubuntu7]
[04:42] -queuebot:#ubuntu-release- Unapproved: accepted gnutls28 [source] (zesty-proposed) [3.5.6-4ubuntu4]
[04:43] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (zesty-proposed) [0.7.9-90-g61eb03fe-0ubuntu1]
[04:45] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (zesty-proposed) [0.1.0~bzr482-0ubuntu1]
[04:45] -queuebot:#ubuntu-release- Unapproved: accepted python-babel [source] (zesty-proposed) [2.3.4+dfsg.1-2ubuntu1]
[04:45] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (zesty-proposed) [1.28]
[04:45] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-artwork [source] (zesty-proposed) [17.04.11]
[04:45] -queuebot:#ubuntu-release- Unapproved: accepted mate-control-center [source] (zesty-proposed) [1.18.1-0ubuntu1]
[04:45] -queuebot:#ubuntu-release- Unapproved: accepted tbb [source] (zesty-proposed) [4.4~20160526-0ubuntu2]
[04:45] -queuebot:#ubuntu-release- Unapproved: accepted python-pika [source] (zesty-proposed) [0.10.0-1ubuntu1]
[04:47] -queuebot:#ubuntu-release- Unapproved: cuneiform (zesty-proposed/multiverse) [1.1.0+dfsg-5build5 => 1.1.0+dfsg-5ubuntu4] (no packageset)
[04:47] -queuebot:#ubuntu-release- Unapproved: accepted cuneiform [source] (zesty-proposed) [1.1.0+dfsg-5ubuntu4]
[06:14] -queuebot:#ubuntu-release- Unapproved: linux-meta (zesty-proposed/main) [4.10.0.17.19 => 4.10.0.18.20] (core, kernel) (sync)
[06:14] -queuebot:#ubuntu-release- Unapproved: linux (zesty-proposed/main) [4.10.0-17.19 => 4.10.0-18.20] (core, kernel) (sync)
[06:14] -queuebot:#ubuntu-release- Unapproved: linux-signed (zesty-proposed/main) [4.10.0-17.19 => 4.10.0-18.20] (core, kernel) (sync)
[06:26] <Saviq> hi team, is there chance to push the packages from https://bileto.ubuntu.com/#/ticket/2668 through the queue? they've been waiting since last night
[06:26] <Saviq> it's all bugfixes
[06:28] -queuebot:#ubuntu-release- Unapproved: telegram-desktop (zesty-proposed/universe) [1.0.14-1 => 1.0.14-1ubuntu1] (no packageset)
[06:29] -queuebot:#ubuntu-release- Unapproved: accepted telegram-desktop [source] (zesty-proposed) [1.0.14-1ubuntu1]
[07:29] -queuebot:#ubuntu-release- Unapproved: lm-sensors (zesty-proposed/main) [1:3.4.0-3 => 1:3.4.0-4] (core) (sync)
[07:38] <LocutusOfBorg> somebody from release team, can you please ignore tests of r-cran-curl (blocking curl migration)?
[07:38] <LocutusOfBorg> rationale is: testsuite is bad, just not ordering cookies before checking them, and I don't want to upload such testsuite fix at this very moment
[07:38] <LocutusOfBorg> https://github.com/jeroen/curl/commit/f885cdbd37e4361ec0f8de679223636e8ea68030
[07:38] <LocutusOfBorg> the new release should be good but I prefer to don't touch r-* stuff
[07:39] <LocutusOfBorg> I could grab some patches, but meh, too risky at this point, it is a testsuite issue, the tool is good
[07:40] -queuebot:#ubuntu-release- Unapproved: libarchive (zesty-proposed/main) [3.2.1-6 => 3.2.2-2] (core) (sync)
[07:40] <LocutusOfBorg> libarchive is a new security release ^^
[07:41] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta [sync] (zesty-proposed) [4.10.0.18.20]
[07:41] -queuebot:#ubuntu-release- Unapproved: accepted linux [sync] (zesty-proposed) [4.10.0-18.20]
[07:41] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed [sync] (zesty-proposed) [4.10.0-18.20]
[07:45] <ypwong> infinity, could you take a look at https://bugs.launchpad.net/ubuntu/+source/ubuntukylin-theme/+bug/1677157 when you have time, this package needs AA to approve.
[07:55] <infinity> ypwong: I'll get there before the freeze today.
[07:56] <ypwong> infinity, thanks!
[08:00] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-raspi2 [sync] (zesty-proposed) [4.10.0.1003.5]
[08:00] -queuebot:#ubuntu-release- Unapproved: accepted linux-raspi2 [sync] (zesty-proposed) [4.10.0-1003.5]
[08:06] <LocutusOfBorg> Laney, ^^ wrt curl :)
[08:07] <infinity> LocutusOfBorg: Why are you against fixing the testsuite?
[08:08] <LocutusOfBorg> because we are too late in the release cycle for doing such things, for zesty + 1 the new release will be uploaded anyway
[08:08] <infinity> LocutusOfBorg: Having an XFAIL makes the whole testsuite useless.  If there's a clear and obvious fix, JFDI?
[08:08] <LocutusOfBorg> the end user won't benefit in any case from my upload
[08:08] <infinity> LocutusOfBorg: We're not too late in the release cycle.  I'm literally just telling you that.
[08:08] <LocutusOfBorg> oh ok
[08:08] <LocutusOfBorg> if you are confortable fine by me
[08:08] <infinity> LocutusOfBorg: End users benefit from regression testing not being broken.
[08:08] <LocutusOfBorg> ok got it
[08:09] <Laney> did I say something about curl before to deserve getting pinged about it? :P
[08:15] <LocutusOfBorg> infinity, just to abuse of your time, do you know why gcc is not complaining for this simple code?
[08:15] <LocutusOfBorg> http://paste.ubuntu.com/24326368/
[08:15] <LocutusOfBorg> doko, ^^
[08:15] <LocutusOfBorg> I would expect an int a[n] with n undefined to be a serious warning or error in gcc
[08:15]  * LocutusOfBorg his world just crashed
[08:28] -queuebot:#ubuntu-release- Unapproved: rejected screen [source] (zesty-proposed) [4.5.0-5ubuntu2]
[08:32] -queuebot:#ubuntu-release- Unapproved: r-cran-curl (zesty-proposed/universe) [2.3-1 => 2.3-1ubuntu1] (no packageset)
[08:33] -queuebot:#ubuntu-release- Unapproved: accepted r-cran-curl [source] (zesty-proposed) [2.3-1ubuntu1]
[08:36] -queuebot:#ubuntu-release- Unapproved: snapd (zesty-proposed/main) [2.23.6+17.04 => 2.23.6+17.04ubuntu1] (desktop-core, ubuntu-server)
[08:42] -queuebot:#ubuntu-release- Unapproved: unity8 (zesty-proposed/main) [8.15+17.04.20170328.3-0ubuntu1 => 8.15+17.04.20170404.7-0ubuntu2] (ubuntu-desktop, ubuntu-qt-packages) (sync)
[08:43] <Saviq> hi again, team, is there still time to get things in the release? I know final freeze is today, just not sure when today :) - was told uploading last night should still allow for things to get in
[08:43] -queuebot:#ubuntu-release- Unapproved: accepted runc [source] (yakkety-proposed) [1.0.0~rc2+docker1.12.6-0ubuntu1~16.10.1]
[08:44] <Laney> we're going to review the queue today
[08:44] <Saviq> so we've unity8, qtmir{,-gles}, qtubuntu{,-gles} and qmenumodel waiting in the queue, if you could please have a look
[08:45] <LocutusOfBorg> why did screen got rejected?
[08:46] <LocutusOfBorg> the current patch is incomplete
[08:46] <Saviq> Laney, ack, thanks
[08:47] <apw> LocutusOfBorg, because there is a possible interaction with the screen we use for release-upgrading
[08:47] <apw> LocutusOfBorg, and until that has been discussed we did not want it accepted accidentaly
[08:50] <LocutusOfBorg> I discussed that screen stuff with the Debian maintainer, and he told me that the patch was "half correct", but incomplete, just forwarding that message to you :)
[08:55] -queuebot:#ubuntu-release- Unapproved: accepted runc [source] (xenial-proposed) [1.0.0~rc2+docker1.12.6-0ubuntu1~16.04.1]
[08:56] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (zesty-proposed/main) [4.10.0-18.20] (core, kernel)
[08:58] -queuebot:#ubuntu-release- Unapproved: rejected snapd [source] (zesty-proposed) [2.23.6+17.04ubuntu1]
[08:58] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (zesty-proposed) [4.10.0-18.20]
[09:08] <acheronuk> freeze @ normal 21:00 UTC (ish)?
[09:13] -queuebot:#ubuntu-release- Unapproved: snapd (zesty-proposed/main) [2.23.6+17.04 => 2.23.6+17.04.1] (desktop-core, ubuntu-server)
[09:16] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (zesty-proposed) [2.23.6+17.04.1]
[09:21] -queuebot:#ubuntu-release- Unapproved: debian-installer (zesty-proposed/main) [20101020ubuntu502 => 20101020ubuntu503] (core)
[09:25] <rbalint> I would like to get in kodi 17.1, see details at: #859708
[09:26] <rbalint> disclaimer: I'm kodi's maintainer :-)
[09:41] <infinity> rbalint: kodi's not seeded, it's fine to go in, so long as you don't break it all in the process.
[09:42] <infinity> rbalint: Although, pointing me at a Debian bug is curious.  Did you mean to ping the Debian release team? ;)
[09:42] <Ukikie> https://bugs.debian.org/859708?
[09:42] -queuebot:#ubuntu-release- Unapproved: r-cran-curl (zesty-proposed/universe) [2.3-1ubuntu1 => 2.3-1ubuntu2] (no packageset)
[09:44] -queuebot:#ubuntu-release- Unapproved: accepted r-cran-curl [source] (zesty-proposed) [2.3-1ubuntu2]
[09:46] -queuebot:#ubuntu-release- Unapproved: tellico (zesty-proposed/universe) [2.3.9+dfsg.1-1.1 => 2.3.9+dfsg.1-1.1ubuntu1] (no packageset)
[09:47] -queuebot:#ubuntu-release- Unapproved: accepted tellico [source] (zesty-proposed) [2.3.9+dfsg.1-1.1ubuntu1]
[09:47] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (zesty-proposed) [20101020ubuntu503]
[09:49]  * Laney spanks LocutusOfBorg 
[09:49] <infinity> Laney: Should we be seeing this?
[09:50]  * LocutusOfBorg agrees with Laney 
[09:50] <LocutusOfBorg> fixing testsuite with upstream cherry-picks and no upstream new code is PITA
[09:50]  * LocutusOfBorg "PITA<->SPANKS", pun intended
[09:51] <LocutusOfBorg> sadly I'm with mobile tethering, can't test in my chroot because of too many r dependencies to drag :/
[09:52] -queuebot:#ubuntu-release- Unapproved: accepted xdg-desktop-portal-gtk [sync] (zesty-proposed) [0.6-1]
[09:52] -queuebot:#ubuntu-release- Unapproved: accepted xdg-desktop-portal [sync] (zesty-proposed) [0.6-1]
[09:57] <Laney> Don't get that pun :P
[09:59] <LocutusOfBorg> (after a spank you can get Pain In The Ass) :)
[09:59] <Laney> oho
[10:02] <rbalint> infinity: no, i meant asking for opinion in advance
[10:03] <rbalint> infinity: i can open the LP bug as well for sync, but if it is rejected anyway there is no point
[10:04] <infinity> rbalint: I'm fine with it.
[10:04] <LocutusOfBorg> rbalint, sync from experimental?
[10:04] <rbalint> infinity: IMO kodi is a killer app both on Debian and Ubuntu and and releasing latest stable point release would be the best
[10:04] <rbalint> LocutusOfBorg: yes, for now
[10:04] <LocutusOfBorg> not sure if you have permissions or not, in case please ask :)
[10:05] <rbalint> LocutusOfBorg: i'm hoping to get it in Stretch, too, but this is another story
[10:05] <LocutusOfBorg> I know, I read the bug on debian-release before you posted it here :p
[10:06] <infinity> rbalint: Sync done.  Don't need a bug.
[10:06] <infinity> rbalint: Any other kodi-related bits that need to come with it, or just the base 'kodi' package?
[10:06] <rbalint> infinity:  no, addons are fine it seems
[10:06] <infinity> Kay.
[10:07] -queuebot:#ubuntu-release- Unapproved: kodi (zesty-proposed/universe) [2:17.0+dfsg1-3 => 2:17.1+dfsg1-1] (no packageset) (sync)
[10:08] -queuebot:#ubuntu-release- Unapproved: accepted kodi [sync] (zesty-proposed) [2:17.1+dfsg1-1]
[10:08] <rbalint> infinity: thanks!
[10:22] <Kaleo> Laney, you off today?
[10:22] <Kaleo> Laney, I still have https://bugs.launchpad.net/ubuntu/+source/ubuntu-terminal-app/+bug/1680114 :/
[10:23] <Laney> Kaleo: No, I'm working through the queue now
[10:23] <Laney> You can publish and get it in the queue if you want
[10:23] <Kaleo> Laney, you mean publish the silo?
[10:23] <Kaleo> I'm sorry I'm not familiar with the FFe process
[10:24] <Laney> It's fine at this point, since it'll get held in the queue and someone can review it there at the same time as they review the FFe
[10:24] <Laney> (since we are in freeze)
[10:24] <Kaleo> oh I see
[10:27] <jbicha> Kaleo: are you able to publish or do you need someone else to?
[10:28] -queuebot:#ubuntu-release- Unapproved: sssd (zesty-proposed/main) [1.15.0-3ubuntu4 => 1.15.2-1ubuntu1] (kubuntu, ubuntu-desktop, ubuntu-server)
[10:31] <tjaalton> ^ https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1680385
[10:35] <infinity> Laney: Should I infer from the above that you're looking at the silo landings in the queue?
[10:36] <Laney> infinity: Nope
[10:36] <Laney> although I've ticked two boxes
[10:36] <infinity> Laney: Oh. :)
[10:36] <infinity> Laney: If you were, I was just going to point out the oddity of unity8 landing twice from two silos, and that one should be sure that the second includes the first.
[10:37] <Laney> I will work through the queue but I would like it if I only had to do 50 or 33⅓% of it :P
[10:37] -queuebot:#ubuntu-release- Unapproved: accepted indicator-session [sync] (zesty-proposed) [17.3.20+17.04.20170403-0ubuntu1]
[10:37] -queuebot:#ubuntu-release- Unapproved: accepted unity8-desktop-session [sync] (zesty-proposed) [1.0.13+17.04.20170328.1-0ubuntu1]
[10:38] <infinity> Laney: Fair.  I can take 2668 and 2705 (ie: the two with unity8)
[10:39] <infinity> tjaalton: That's quite the diff for a "bugfix release".
[10:41] <tjaalton> infinity: the translations?
[10:41] <infinity> tjaalton: No, the code. :P
[10:41] <infinity> tjaalton: Not a NACK, but I do want to verify some of your assertions.
[10:43] <tjaalton> it added the files provider and socket responder helper, neither of which aren't used yet by default
[10:43] <tjaalton> they cut 1.15.0 for debian, without those features.. they were polished for .1
[10:44] <infinity> tjaalton: Without reading the 1MB diff, do you know off-hand where to point me to code that indicated the files provider isn't used by default?
[10:46] <tjaalton> it's not added to nsswitch.conf
[10:47] <tjaalton> libnss-sss postinst adds 'sss', but not 'files'
[10:48] <tjaalton> this has been in place for some time now
[10:48] <tjaalton> also there's no default sssd.conf installed
[10:48] <infinity> Right, okay.  And --enable-files-domain would universally enable it, I think, but you didn't add that to rules.
[10:48] <tjaalton> for buster & AA it'll probably happen
[10:48] <tjaalton> oh indeed
[10:49] <tjaalton> yeah that would probably mean no conffile needed
[10:49] <infinity> Sure, I'm all for sssd eventually obsoleting nscd to the point where we can remove it from glibc upstream and forget it ever happened, but today isn't that day.
[10:49] <tjaalton> didn't look yet
[10:49] <tjaalton> yep
[10:50] <infinity> I'm curious if we could actually do a reliable nscd->sssd migration path and just replace the nscd package with a migration stub.
[10:50] <infinity> Might be something to consider for a future LTS.
[10:50] <tjaalton> yeah
[10:50] <infinity> Though, nscd has had improvements for some of it's worse bugs, and it likely smaller.
[10:50] <infinity> So, ... *handwavy*
[10:51] <tjaalton> sssd daemon is split in smaller bits, so with just files it's smaller than when configured against ms ad
[10:52] <tjaalton> i haven't tested this theory though. and socket activation etc isn't enabled either
[10:52] <tjaalton> when that happens it'll only run what's needed
[10:52] <infinity> Socket activation for a resolver sounds like a really stupid idea.
[10:53] <infinity> Of all the things on my system that I want to respond INSTANTLY, the resolver is at the top of the list.
[10:53] <tjaalton> well, used for some of the bits
[10:55] -queuebot:#ubuntu-release- Unapproved: accepted sssd [source] (zesty-proposed) [1.15.2-1ubuntu1]
[10:57] <tjaalton> thanks
[10:59] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (yakkety-proposed/main) [4.8.0-47.50] (core, kernel)
[11:00] -queuebot:#ubuntu-release- Unapproved: ubuntu-themes (zesty-proposed/main) [16.10+17.04.20170309-0ubuntu1 => 16.10+17.04.20170406-0ubuntu1] (core) (sync)
[11:05] <ginggs> Laney: LP: #1676923 i think all the info is there now.  andt BTW tzdata 2017b-1 just uploaded https://packages.qa.debian.org/t/tzdata/news/20170406T100345Z.html
[11:05] <rbalint> infinity: could lxml be hinted to migrate despite snapcraft autopkgtest issues?
[11:05] <rbalint> infinity: they seem to be testbed network related problems
[11:05] <infinity> rbalint: "network related problems"?
[11:05] <rbalint> infinity: it keeps failing in different ways related to the proxy
[11:06] <rbalint> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/s/snapcraft/20170404_231948_bb766@/log.gz
[11:06] <rbalint> infinity:  now the wiki pull which used to be working: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/s/snapcraft/20170406_071511_dffe9@/log.gz
[11:07] <infinity> rbalint: We'll just retry it a few times and see if it fixes itself. :P
[11:07] <rbalint> infinity: ok
[11:08] <rbalint> infinity: i asked cyphermox to restart it 2 times alreade
[11:08] <rbalint> y
[11:08] <rbalint> infinity: what is the usual upper limit? :-)
[11:09] <infinity> rbalint: 37.
[11:09] <Laney> why is it so crap on armhf?
[11:10] <infinity> Different network?  lxd dropping connections prematurely?
[11:10] <rbalint> Laney: good question, maybe testbed location?
[11:10] <Laney> "socket.gaierror: [Errno -3] Temporary failure in name resolution"
[11:11] -queuebot:#ubuntu-release- Unapproved: accepted openssh [sync] (yakkety-proposed) [1:7.3p1-1ubuntu0.1]
[11:11] -queuebot:#ubuntu-release- Unapproved: greybird-gtk-theme (zesty-proposed/universe) [3.22.2-1 => 3.22.2-1ubuntu1] (xubuntu)
[11:12] <rbalint> infinity: 37: ok :-)
[11:15] -queuebot:#ubuntu-release- Unapproved: accepted openssh [sync] (xenial-proposed) [1:7.2p2-4ubuntu2.2]
[12:58] -queuebot:#ubuntu-release- Unapproved: adwaita-icon-theme (zesty-proposed/main) [3.23.91.1-0ubuntu1 => 3.24.0-0ubuntu1] (core)
[13:10] -queuebot:#ubuntu-release- Unapproved: ubuntu-terminal-app (zesty-proposed/main) [0.7.218ubuntu2 => 0.7.218+17.04.20170405.7-0ubuntu1] (ubuntu-desktop) (sync)
[13:21] -queuebot:#ubuntu-release- Unapproved: graphviz (trusty-proposed/main) [2.36.0-0ubuntu3.1 => 2.36.0-0ubuntu3.2] (core)
[13:27] <infinity> Laney: Where are ppc64el and s390x tests going?  It seems like they get queued, and the queue gets drained without tests actually happening.
[13:27] <Laney> can you give me an example?
[13:28] <apw> "    " <- :)
[13:28] -queuebot:#ubuntu-release- Unapproved: librsvg (zesty-proposed/main) [2.40.16-1 => 2.40.16-2~svn1] (core)
[13:32] -queuebot:#ubuntu-release- Unapproved: lazarus (zesty-proposed/universe) [1.6.2+dfsg-1 => 1.6.2+dfsg-2] (no packageset) (sync)
[13:32] -queuebot:#ubuntu-release- Unapproved: accepted lazarus [sync] (zesty-proposed) [1.6.2+dfsg-2]
[13:39] <infinity> Laney: All?
[13:39] <Laney> I get that
[13:39] <infinity> Laney: http://autopkgtest.ubuntu.com/packages/r-cran-curl
[13:39] <Laney> But it's much quicker for me to look up a specific request that you're noticing a problem with
[13:39] <Laney> Ta
[13:39] <infinity> Laney: I didn't make those requests, but I assume they included all arches.  I made other requests that seem to have similar "where did they go?" issues.
[13:40] <Laney> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/?format=plain&prefix=zesty/ppc64el/r/r-cran-curl/
[13:40] <Laney> There's results there that aren't in the web UI
[13:40] <infinity> Ah-ha.
[13:41] <Laney> I guess britney is seeing them okay?
[13:41] <infinity> Probably.
[13:41]  * infinity goes to look.
[13:41] <Laney> Right, so probably a problem there, let's see
[13:41] <infinity> Laney: Yep, as you suspected, britney has results for that.
[13:41] <Laney> if you want to know, this is juju ssh autopkgtest-web/0 from prod-ues-proposed-migration@wendigo
[13:42] <infinity> I feel like I won't remember that.
[13:42] <infinity> Is there a cheat sheet for casual autopkgtest maintenance?
[13:43] <Laney> somewhat: https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Administration
[13:43] <Laney> ERROR:root:Failure to fetch swift results from http://10.24.0.175:8080/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty?marker=zesty%2Farmhf%2Fc%2Fcinder%2F20161028_120634_e00b4%40&delimiter=%40: Remote end closed connection without response
[13:43] <Laney> Seems like some acid rain in the cloud
[13:48]  * Laney pinged a sysadmin and will go have lunch now while it gets looked at
[13:53] <Laney> I think it recovered itself
[13:54] -queuebot:#ubuntu-release- Unapproved: iproute2 (xenial-proposed/main) [4.3.0-1ubuntu3 => 4.3.0-1ubuntu3.16.04.1] (core)
[13:54] -queuebot:#ubuntu-release- Unapproved: iproute2 (yakkety-proposed/main) [4.3.0-1ubuntu3 => 4.3.0-1ubuntu3.16.10.1] (core)
[13:55] <LocutusOfBorg> will anybody merge systemd from Debian? I'm worried about the dnssec change mentioning zesty but apparently not uploaded there
[14:13] <smoser> bdmurray, i've updated those now. sorry for leaving them so sparse.
[14:23] -queuebot:#ubuntu-release- Unapproved: kdialog (zesty-proposed/universe) [16.12.1-0ubuntu1 => 16.12.3-0ubuntu1] (kubuntu)
[14:23] -queuebot:#ubuntu-release- Unapproved: kfind (zesty-proposed/universe) [4:16.12.1-0ubuntu1 => 4:16.12.3-0ubuntu1] (kubuntu)
[14:23] -queuebot:#ubuntu-release- Unapproved: keditbookmarks (zesty-proposed/universe) [16.12.1-0ubuntu1 => 16.12.3-0ubuntu1] (kubuntu)
[14:23] -queuebot:#ubuntu-release- Unapproved: konqueror (zesty-proposed/universe) [4:16.12.1-0ubuntu1 => 4:16.12.3-0ubuntu1] (kubuntu)
[14:30] -queuebot:#ubuntu-release- Unapproved: binutils (zesty-proposed/main) [2.28-2ubuntu1 => 2.28-3ubuntu1] (core)
[14:55] -queuebot:#ubuntu-release- Unapproved: bamf (zesty-proposed/main) [0.5.3+16.10.20160929-0ubuntu1 => 0.5.3+17.04.20170406-0ubuntu1] (kubuntu, ubuntu-desktop) (sync)
[15:32] <stgraber> can someone look at lxd and btrfs-progs in the queue, would like those fixes in the archive soon :)
[15:49] -queuebot:#ubuntu-release- Unapproved: accepted ubuntukylin-theme [source] (zesty-proposed) [1.7.0]
[15:51] -queuebot:#ubuntu-release- Unapproved: accepted btrfs-progs [source] (zesty-proposed) [4.9.1-1ubuntu1]
[15:51] <apw> stgraber, ^
[15:53] <Laney>  diff from 56.0.2924.76-0ubuntu2.1343 to 57.0.2987.98-0ubuntu1.1348 (48.4 MiB)
[15:53] <Laney> What. On. Earth.
[15:53] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (zesty-proposed) [2.12-0ubuntu3]
[15:53] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-app-launch [sync] (zesty-proposed) [0.12+17.04.20170404.2-0ubuntu1]
[15:53] -queuebot:#ubuntu-release- Unapproved: accepted mate-panel [source] (zesty-proposed) [1.18.1-0ubuntu1]
[15:53] -queuebot:#ubuntu-release- Unapproved: accepted unity-api [sync] (zesty-proposed) [8.7+17.04.20170404-0ubuntu1]
[15:53] <stgraber> apw: thanks
[15:57] -queuebot:#ubuntu-release- Unapproved: kfilereplace (zesty-proposed/universe) [4:16.12.1-0ubuntu1 => 4:16.12.3-0ubuntu1] (kubuntu)
[15:57] -queuebot:#ubuntu-release- Unapproved: klinkstatus (zesty-proposed/universe) [4:16.12.1-0ubuntu1 => 4:16.12.3-0ubuntu1] (kubuntu)
[15:57] -queuebot:#ubuntu-release- Unapproved: kimagemapeditor (zesty-proposed/universe) [4:16.12.1-0ubuntu1 => 4:16.12.3-0ubuntu1] (kubuntu)
[15:57] -queuebot:#ubuntu-release- Unapproved: kommander (zesty-proposed/universe) [4:16.12.1-0ubuntu1 => 4:16.12.3-0ubuntu1] (kubuntu)
[16:00] <Laney> barry: how come this python-requests-unixsocket is the same upstream version as is already in the archive but has different upstream contents?
[16:00] <Laney> Seems to only be metadata ...
[16:03] <Laney> I think it's okay otherwise. Not sure why all the empty dh_ overrides...
[16:04] <Laney> Someone else could accept that if they wanted to, if the explanation is sane
[16:04]  * Laney back in a couple of hours
[16:09] -queuebot:#ubuntu-release- New: rejected ubuntu-filemanager-app [sync] (zesty-proposed) [0.4+17.04.20170323-0ubuntu1]
[16:11] -queuebot:#ubuntu-release- Unapproved: accepted binutils [source] (zesty-proposed) [2.28-3ubuntu1]
[16:15] -queuebot:#ubuntu-release- Unapproved: rejected unity8 [sync] (zesty-proposed) [8.15+17.04.20170404.7-0ubuntu1]
[16:18] <barry>  
[16:18] <barry> Laney: that's weird.  it certainly shouldn't be different and i can't think of what i might have done to cause that
[16:18] -queuebot:#ubuntu-release- Unapproved: accepted librsvg [source] (zesty-proposed) [2.40.16-2~svn1]
[16:27] -queuebot:#ubuntu-release- Unapproved: accepted kdialog [source] (zesty-proposed) [16.12.3-0ubuntu1]
[16:30] -queuebot:#ubuntu-release- Unapproved: accepted keditbookmarks [source] (zesty-proposed) [16.12.3-0ubuntu1]
[16:32] -queuebot:#ubuntu-release- Unapproved: accepted kfind [source] (zesty-proposed) [4:16.12.3-0ubuntu1]
[16:36] -queuebot:#ubuntu-release- Unapproved: accepted konqueror [source] (zesty-proposed) [4:16.12.3-0ubuntu1]
[16:38] -queuebot:#ubuntu-release- Unapproved: accepted kfilereplace [source] (zesty-proposed) [4:16.12.3-0ubuntu1]
[16:40] -queuebot:#ubuntu-release- Unapproved: accepted kimagemapeditor [source] (zesty-proposed) [4:16.12.3-0ubuntu1]
[16:40] -queuebot:#ubuntu-release- Unapproved: nova-lxd (yakkety-proposed/main) [14.2.0-0ubuntu0.16.10.1 => 14.2.2-0ubuntu0.16.10.1] (ubuntu-server)
[16:41] -queuebot:#ubuntu-release- Unapproved: accepted klinkstatus [source] (zesty-proposed) [4:16.12.3-0ubuntu1]
[16:42] -queuebot:#ubuntu-release- Unapproved: accepted kommander [source] (zesty-proposed) [4:16.12.3-0ubuntu1]
[16:43] -queuebot:#ubuntu-release- Unapproved: libqapt (zesty-proposed/universe) [3.0.2-0ubuntu5 => 3.0.3-0ubuntu1] (kubuntu)
[16:44] -queuebot:#ubuntu-release- Unapproved: muon (zesty-proposed/universe) [4:5.6.0-0ubuntu2 => 4:5.7.0-0ubuntu1] (kubuntu)
[16:50] -queuebot:#ubuntu-release- Unapproved: keystone (xenial-proposed/main) [2:9.2.0-0ubuntu1 => 2:9.3.0-0ubuntu1] (openstack, ubuntu-server)
[16:52] -queuebot:#ubuntu-release- Unapproved: horizon (xenial-proposed/main) [2:9.1.1-0ubuntu1 => 2:9.1.2-0ubuntu1] (openstack, ubuntu-server)
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted qmenumodel [sync] (zesty-proposed) [0.2.12+17.04.20170404-0ubuntu1]
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted qtmir [sync] (zesty-proposed) [0.5.1+17.04.20170404-0ubuntu1]
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted qtubuntu [sync] (zesty-proposed) [0.64+17.04.20170404-0ubuntu1]
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted qtmir-gles [sync] (zesty-proposed) [0.5.1+17.04.20170404-0ubuntu1]
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted qtubuntu-gles [sync] (zesty-proposed) [0.64+17.04.20170404-0ubuntu1]
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted unity8 [sync] (zesty-proposed) [8.15+17.04.20170404.7-0ubuntu2]
[16:55] -queuebot:#ubuntu-release- Unapproved: accepted accounts-qml-module [sync] (zesty-proposed) [0.6+17.04.20170405-0ubuntu1]
[16:55] -queuebot:#ubuntu-release- Unapproved: accepted unity-action-api [sync] (zesty-proposed) [1.1.0+17.04.20170405-0ubuntu1]
[16:56] -queuebot:#ubuntu-release- Unapproved: accepted libarchive [sync] (zesty-proposed) [3.2.2-2]
[16:56] -queuebot:#ubuntu-release- Unapproved: accepted chromium-browser [source] (zesty-proposed) [57.0.2987.98-0ubuntu1.1348]
[16:57] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-themes [sync] (zesty-proposed) [16.10+17.04.20170406-0ubuntu1]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted bamf [sync] (zesty-proposed) [0.5.3+17.04.20170406-0ubuntu1]
[17:02] -queuebot:#ubuntu-release- Unapproved: accepted muon [source] (zesty-proposed) [4:5.7.0-0ubuntu1]
[17:03] <apw> acheronuk, are are pushing that freeze ...
[17:04] <acheronuk> apw: are are what?
[17:04] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-terminal-app [sync] (zesty-proposed) [0.7.218+17.04.20170405.7-0ubuntu1]
[17:04] <apw> s/are/you ...
[17:05] <apw> acheronuk, also i am hating on a 0.5MB diff for muon
[17:06] <acheronuk> apw: what are you asking? if I have more to upload? answer to that is no
[17:06] -queuebot:#ubuntu-release- Unapproved: accepted lm-sensors [sync] (zesty-proposed) [1:3.4.0-4]
[17:08] <apw> acheronuk, i am interested you are not indeed doing more, but i was just being exasperated :)
[17:09] -queuebot:#ubuntu-release- Unapproved: accepted adwaita-icon-theme [source] (zesty-proposed) [3.24.0-0ubuntu1]
[17:09] -queuebot:#ubuntu-release- Unapproved: accepted greybird-gtk-theme [source] (zesty-proposed) [3.22.2-1ubuntu1]
[17:10] <acheronuk> apw: apologies. never intend these things to be this late. then stuff happens.... or actually sometimes doesn't when you WANT it to
[17:11] -queuebot:#ubuntu-release- Unapproved: accepted libqapt [source] (zesty-proposed) [3.0.3-0ubuntu1]
[17:11] <apw> acheronuk, indeed
[18:06] <rbalint> python-boto autopkgtest has a lot of forbidden-s, while it is passing on Debian
[18:07] <rbalint> it does not let 2.44.0-1ubuntu1 to migrate to zesty
[18:07] <rbalint> should not those test results be ignored?
[18:11] <nacc> jgrimm: --^ ?
[18:13] <jgrimm> rbalint, i believe they can be ignored too
[18:13] <jgrimm> they were ignored/skipped on previous upload. not new
[18:14] <nacc> yeah, i think we decided that a hint update was needed
[18:14] <nacc> as the hint was versioned
[18:14] <nacc> in pitti's hints
[18:16] <rbalint> i think phyml autopkgtests should be ignored for everything other than amd64 and i386 since a dep is not available (pocl-opencl-icd)
[18:16] <rbalint> i think this can be unversioned
[18:41] -queuebot:#ubuntu-release- Unapproved: khmer (zesty-proposed/universe) [2.0+dfsg-9 => 2.0+dfsg-9ubuntu1] (no packageset)
[18:41] -queuebot:#ubuntu-release- Unapproved: accepted khmer [source] (zesty-proposed) [2.0+dfsg-9ubuntu1]
[18:57] <rbalint> it looks like many R packages have circular autopkgtest blocks
[18:57] <rbalint> adding versioned dependencies where they are missing may clean up the picture a bit
[18:58] <rbalint> or a set could be hinted in together
[18:58] <rbalint> should i start adding patches for the missing dependencies or hinting is the usual resolution
[18:58] <rbalint> ?
[19:00] <rbalint> example: r-bioc-summarizedexperiment 1.4.0-2 is waiting for r-bioc-iranges but lists r-bioc-summarizedexperiment/1.2.0-1 test failure as a regression
[19:14] -queuebot:#ubuntu-release- Unapproved: cockpit (zesty-proposed/universe) [134-1 => 137-3] (no packageset) (sync)
[19:14] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [sync] (zesty-proposed) [137-3]
[19:26] <ginggs> rbalint: you can re-run the tests with additional triggers
[19:27] <rbalint> ginggs: how?
[19:27] <rbalint> ginggs: when i tried it failed due to not having upload rights yet
[19:27] <ginggs> rbalint: are you looking at update_excuses.html ?
[19:27] <rbalint> ginggs: yes
[19:28] <ginggs> rbalint: ah, then you are going to have to ask someone
[19:28] <ginggs> but you can make it easy for them by crafting the URL and just asking them to click on it
[19:28] <nacc> https://wiki.ubuntu.com/ProposedMigration#How_to_re-run_autopkgtests_with_dependencies_on_other_packages_in_the_proposed_pocket
[19:29] <nacc> rbalint: if you can generate the URL you need, i can run them
[19:29] <ginggs> rbalint: so let's look at your example
[19:29] <rbalint> nacc: thanks
[19:29] <nacc> rbalint: np
[19:30] <rbalint> ginggs: i think it does not help because iranges from proposed is tested with summarizedexperiment from zesty which fails
[19:31] <rbalint> ginggs: but when they enter together they will both pass
[19:31] <ginggs> rbalint: this will help for that
[19:31] <nacc> right, you basically need to hint hat for excuses purposes -- and then update_output will dtrt for the actual migration
[19:31] <nacc> (aiui)
[19:31] <rbalint> ginggs: reading the link
[19:32] <rbalint> ginggs: got that, thanks
[19:32] <Laney> barry: Maybe one is from a git tag and one's from somewhere else?
[19:32] <nacc> rbalint: basically each trigger you add is a srcpkg to use from -proposed for the test
[19:33] <ginggs> https://autopkgtest.ubuntu.com/request.cgi?release=zesty&arch=amd64&package=r-bioc-summarizedexperiment&trigger=r-bioc-biocgenerics%2F0.20.0-1&trigger=r-bioc-iranges%2f2.8.1-1
[19:34] <ginggs> i've just requested this ^
[19:34] <Laney> If this indicates a problem with dependencies, that should also be fixed imho
[19:34] <ginggs> i manually added &trigger=r-bioc-iranges%2f2.8.1-1
[19:34] <rbalint> i have to follow all cycles to see if all the packages are only blocked by this problem
[19:34] <barry> Laney: possibly.  maybe my tool to gitify apt-get source is wonky (tho it's always worked until now).  gotta walk the dog then i'll try to do straight up a-g source and apply the patch that way.  maybe 20m
[19:38] <rbalint> ginggs: please try that one, too: https://autopkgtest.ubuntu.com/request.cgi?release=zesty&arch=amd64&package=r-cran-treescape&trigger=rcpp%2F0.12.9-1&trigger=r-cran-phangorn=%2F2.1.1-1
[19:39] <ginggs> You submitted an invalid request: Malformed trigger
[19:40] <ginggs> you want &trigger=r-cran-phangorn%2F2.1.1-1 there
[19:40] <ginggs> requested
[19:40] <rbalint> ginggs: yes, thanks
[19:41] <ginggs> rbalint: watch out for versions with '+' in them, replace with %2B
[19:41] <rbalint> ginggs: yes, I'll encode the links
[19:42] <rbalint> ginggs: i think I'll compile a list after i see the results
[19:42] <rbalint> ginggs: there are several dozen triggers which will be needed
[19:43] <ginggs> paste.ubuntu.com
[19:46] <ginggs> rbalint: do you by any chance know what is happening with LP: #1640320 ?  It would be really nice to kick out boost1.61
[19:51] <rbalint> ginggs: AFAIK location-service fix is merged, l-s devs need to release new version
[19:52] <ginggs> rbalint: thanks
[19:52] <rbalint> ginggs: removed the misleasing assignmet to me since I can't release and a different patch got accepted
[20:05] <barry> Laney: could it be an tar.gz/tar.xz thing?
[20:05] <barry>  
[20:24] <ginggs> rbalint: http://autopkgtest.ubuntu.com/packages/r/r-bioc-summarizedexperiment/zesty/amd64 success
[20:26] <ginggs> i've requested that combination on the other arches
[20:36] <Laney> barry: Well, that's why it's allowed to change I presume - I don't know why it *did* change though...
[20:36] <Laney> Did one of you generate the tarball yourselves or something?
[20:37] <Laney> I suppose if you eyeball the changes and make sure they're all okay then we can roll with this
[20:37] <barry> Laney: no, i just syncpackaged it from unstable (sorry, i previously got it mixed up with a few other packages i've been ftbfs-fixing).
[20:37] <barry> % syncpackage -f -b 1679842 python-requests-unixsocket
[20:38] <Laney> ok, maybe not *you*, but the maintainer or whoever uploaded it to Ubuntu the first time
[20:38]  * barry looks at zul :)
[20:38] <Laney> like maybe someone used one of the auto-tarballs from github and the other person found a released version on a website
[20:39] <slangasek> infinity: around?
[20:39] <barry> Laney: do you have a link to a page for exactly the differences you're seeing?  i'm happy to eyeball them, but i want to make sure i'm looking at what you're looking at
[20:39] <Laney> barry: Download the two packages and debdiff them
[20:39] <barry> Laney: ack
[20:40] <slangasek> infinity: discussing subiquity livefs builds with cyphermox; I'm suggesting this should be PROJECT=ubuntu-server, SUBPROJECT=live, since there is already an ubuntu-server livefs build which differs (and must do).  Opinions?
[20:41] <Laney> barry: Suggest you give your findings to slangasek or infinity if they're around when you get them - I'm off for the night now
[20:41] <Laney> see you!
[20:41] <barry> Laney: thanks!
[20:46] -queuebot:#ubuntu-release- Unapproved: libmatekbd (zesty-proposed/universe) [1.18.0-0ubuntu1 => 1.18.1-0ubuntu1] (ubuntu-mate, ubuntukylin)
[20:57] <barry> Laney, slangasek, infinity oh, yeah, i bet that's exactly this.  zul probably got 0.1.5 from pypi, but zigo spins openstack packages from git so the two don't match.  :( :(  have i mentioned how much i disagree with that approach?
[20:58] <slangasek> can't imagine anyone ever finding anything objectionable about any of the 15 different approaches to openstack packaging
[20:59] <barry> fortunately there is broad consensus that all those general python library packages should be folded back into dpmt and use the consistent workflow.  that'll happen after stretch most likely
[21:03] <barry> slangasek: so yeah, outside of debian/ it looks like metadata only differences, e.g. some files missing (e.g. AUTHORS, ChangeLog, PKG-INFO).  http://paste.ubuntu.com/24330003/
[21:04] <barry> looks okay to me, and local builds had no problem
[21:11] <infinity> slangasek: I'm not overburdened with opinion on the matter.
[21:17] <barry> i'm also totally fine waiting until aardvark.  this mostly just fixes a ftbfs in doko's rebuild
[21:19] <valorie> aha, so it *will* be aardvark!
[21:19] <barry> valorie: well, if it were up to me, which it rarely is <wink>
[21:19] <barry> aamazing aardvark
[21:19] <valorie> \o/
[21:20] <valorie> love it
[21:20] <valorie> I can already see the artwork in my mind
[21:21]  * acheronuk is still hoping for an Anaconda
[21:22] <barry> oh, i got a million of them.  bbubbly bbabboon, ccrazy ccougar, ddangerous ddingo.  i really don't understand why mark never uses my suggestions
[21:23] <barry> although i did get yakkety right (but it was the obvious choice :)
[21:24] <jbicha> barry: I helped pick maverick! https://wiki.ubuntu.com/DevelopmentCodeNames?action=diff&rev1=594&rev2=595
[21:25] <barry> jbicha: :)
[21:25] <barry> there should be some kind of prize!
[22:48] -queuebot:#ubuntu-release- Unapproved: keepass2 (zesty-proposed/universe) [2.35+dfsg-1 => 2.35+dfsg-2] (cli-mono) (sync)
[23:07] <doko> slangasek, infinity: please could you review the binutils update in the unapproved queue?
[23:34] <slangasek> doko: there isn't one; there was one accepted 7 hours before your ping?