[00:12] -queuebot:#ubuntu-release- New binary: nageru [ppc64el] (zesty-proposed/universe) [1.3.4-2] (no packageset) [00:13] -queuebot:#ubuntu-release- Unapproved: golang-go.crypto (xenial-proposed/main) [1:0.0~git20151201.0.7b85b09-2 => 1:0.0~git20161012.0.5f31782-1ubuntu0.16.04.1] (kubuntu, ubuntu-desktop) [00:15] -queuebot:#ubuntu-release- New binary: nageru [amd64] (zesty-proposed/universe) [1.3.4-2] (no packageset) [00:15] -queuebot:#ubuntu-release- New binary: nageru [armhf] (zesty-proposed/universe) [1.3.4-2] (no packageset) [00:18] -queuebot:#ubuntu-release- New binary: nageru [arm64] (zesty-proposed/universe) [1.3.4-2] (no packageset) [00:18] -queuebot:#ubuntu-release- New binary: nageru [i386] (zesty-proposed/universe) [1.3.4-2] (no packageset) [00:18] -queuebot:#ubuntu-release- New binary: nageru [s390x] (zesty-proposed/universe) [1.3.4-2] (no packageset) [00:20] -queuebot:#ubuntu-release- New binary: nageru [powerpc] (zesty-proposed/universe) [1.3.4-2] (no packageset) [01:28] -queuebot:#ubuntu-release- New binary: libdrumstick [ppc64el] (zesty-proposed/universe) [1.0.2-1] (no packageset) [01:28] -queuebot:#ubuntu-release- New binary: libdrumstick [s390x] (zesty-proposed/universe) [1.0.2-1] (no packageset) [01:34] -queuebot:#ubuntu-release- New binary: libdrumstick [i386] (zesty-proposed/universe) [1.0.2-1] (no packageset) [01:34] -queuebot:#ubuntu-release- New binary: libdrumstick [powerpc] (zesty-proposed/universe) [1.0.2-1] (no packageset) [01:35] -queuebot:#ubuntu-release- New binary: libdrumstick [amd64] (zesty-proposed/universe) [1.0.2-1] (no packageset) [01:35] -queuebot:#ubuntu-release- New binary: libdrumstick [armhf] (zesty-proposed/universe) [1.0.2-1] (no packageset) [01:35] -queuebot:#ubuntu-release- New binary: libdrumstick [arm64] (zesty-proposed/universe) [1.0.2-1] (no packageset) [06:07] -queuebot:#ubuntu-release- New: accepted libdrumstick [amd64] (zesty-proposed) [1.0.2-1] [06:07] -queuebot:#ubuntu-release- New: accepted libdrumstick [armhf] (zesty-proposed) [1.0.2-1] [06:07] -queuebot:#ubuntu-release- New: accepted libdrumstick [powerpc] (zesty-proposed) [1.0.2-1] [06:07] -queuebot:#ubuntu-release- New: accepted libdrumstick [s390x] (zesty-proposed) [1.0.2-1] [06:07] -queuebot:#ubuntu-release- New: accepted libdrumstick [arm64] (zesty-proposed) [1.0.2-1] [06:07] -queuebot:#ubuntu-release- New: accepted libdrumstick [ppc64el] (zesty-proposed) [1.0.2-1] [06:07] -queuebot:#ubuntu-release- New: accepted libdrumstick [i386] (zesty-proposed) [1.0.2-1] [06:07] -queuebot:#ubuntu-release- New: accepted nageru [amd64] (zesty-proposed) [1.3.4-2] [06:07] -queuebot:#ubuntu-release- New: accepted nageru [armhf] (zesty-proposed) [1.3.4-2] [06:07] -queuebot:#ubuntu-release- New: accepted nageru [powerpc] (zesty-proposed) [1.3.4-2] [06:07] -queuebot:#ubuntu-release- New: accepted nageru [s390x] (zesty-proposed) [1.3.4-2] [06:07] -queuebot:#ubuntu-release- New: accepted nageru [arm64] (zesty-proposed) [1.3.4-2] [06:07] -queuebot:#ubuntu-release- New: accepted nageru [ppc64el] (zesty-proposed) [1.3.4-2] [06:07] -queuebot:#ubuntu-release- New: accepted nageru [i386] (zesty-proposed) [1.3.4-2] [06:08] -queuebot:#ubuntu-release- New: accepted firebird3.0 [arm64] (zesty-proposed) [3.0.1.32609.ds4-8] [06:08] -queuebot:#ubuntu-release- New: accepted firebird3.0 [i386] (zesty-proposed) [3.0.1.32609.ds4-8] [06:08] -queuebot:#ubuntu-release- New: accepted firebird3.0 [armhf] (zesty-proposed) [3.0.1.32609.ds4-8] [06:08] -queuebot:#ubuntu-release- New: accepted firebird3.0 [powerpc] (zesty-proposed) [3.0.1.32609.ds4-8] [06:08] -queuebot:#ubuntu-release- New: accepted firebird3.0 [amd64] (zesty-proposed) [3.0.1.32609.ds4-8] [06:08] -queuebot:#ubuntu-release- New: accepted firebird3.0 [s390x] (zesty-proposed) [3.0.1.32609.ds4-8] [06:08] -queuebot:#ubuntu-release- New: accepted firebird3.0 [ppc64el] (zesty-proposed) [3.0.1.32609.ds4-8] [08:32] -queuebot:#ubuntu-release- New binary: pcp [amd64] (zesty-proposed/universe) [3.11.5] (no packageset) === seb128_ is now known as seb128 [09:16] FTR: britney isn't being updated because swift keeps running into "proxy errors" or timeouts [09:16] Laney: ^ [09:16] I'll watch it and notify IS if this persists [09:17] pitti: I think I saw robr_u asking about swift problems yesterday also [09:17] Laney: yeah, for "the" bileto ticket [09:18] failing to upload files [09:18] so already persisted for some time if it's the same problem [09:19] it's the download direction for me [09:29] nice, the next run seems to have finished, and so did my local (~pitti) run to test the new branch [09:30] impressive queue size [09:30] Laney: and that's only the s390x mass-retries for perl.. [09:30] (I didn't yet do it for the other arches as they are still catching up) [09:33] pitti: Yeah, quite a lot of red on there [09:33] * Laney is going through local failures now [09:34] might fire them at a PPA though so others can see (and maybe some will randomly work on launchpad) [09:35] Laney, pitti: out of interest how long before there are daily iso's for z I assume not too long right? [09:37] davmor2: there's nothing fundamental that would block those; not sure what it takes to switch them on [10:30] -queuebot:#ubuntu-release- Unapproved: ubuntu-themes (xenial-proposed/main) [14.04+16.04.20160804-0ubuntu1 => 14.04+16.04.20161024-0ubuntu1] (kubuntu, ubuntu-desktop) (sync) [12:20] Laney: wrt. http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#perl, it seems there are two metric tons of packages which need no-change rebuilds or syncs; is anyone working on that? [12:20] pitti: Have you been watching zesty-changes? :-) [12:21] http://people.canonical.com/~ubuntu-archive/transitions/html/perl5.24.html is getting more green [12:21] Laney: no, I haven't; just looked at some random samples of uninstallability [12:21] Laney: but if you are on it, great, I just wanted to know whether anyone is :) [12:21] transition tracker> nice, so much easier [12:21] soon it will be just the really broken things left [12:22] I'll kill my retries then, not much point in those [12:22] Laney, wow, thats improved hugely [12:22] apw: yeh, getting there [12:23] levels 1 and 2 are basically now things that are actual problems [12:23] I think the ones that are all red are removals that Debian did too [12:23] and mysql must be about half the rest :/ [12:24] (we should probably follow those) [12:25] Laney: want me to go through process-removals? [12:25] pitti: Not sure that tracks testing removals? [12:25] * pitti ran it a week before release, I suppose most of the recent stuff since then is legit [12:25] ah no, it's not [12:25] If you find perl things in there though then go for it [12:25] I'll file a bug later or tomorrow === mhall119_ is now known as mhall119 [12:50] pitti, Laney: imho we should follow testing removals, with demotions to proposed. [12:51] and an auto-bug filed "block-proposed" for those, to prevent migration straight back. [12:58] Laney: through with process-removals; no perl stuff there [12:59] yeah, not surprised [12:59] thanks for doing a pass anyway [12:59] -queuebot:#ubuntu-release- New: accepted emacs25 [sync] (zesty-proposed) [25.1+1-1] [13:02] -queuebot:#ubuntu-release- New binary: fonts-tiresias [amd64] (zesty-proposed/none) [0.1-3] (no packageset) [13:06] -queuebot:#ubuntu-release- New: accepted fonts-tiresias [amd64] (zesty-proposed) [0.1-3] [13:31] -queuebot:#ubuntu-release- New binary: emacs25 [s390x] (zesty-proposed/universe) [25.1+1-2] (no packageset) [13:32] -queuebot:#ubuntu-release- New binary: emacs25 [ppc64el] (zesty-proposed/universe) [25.1+1-2] (no packageset) === tyhicks` is now known as tyhicks [13:37] -queuebot:#ubuntu-release- New binary: emacs25 [powerpc] (zesty-proposed/universe) [25.1+1-2] (no packageset) [13:39] -queuebot:#ubuntu-release- New binary: emacs25 [i386] (zesty-proposed/universe) [25.1+1-2] (no packageset) [13:44] -queuebot:#ubuntu-release- New binary: emacs25 [amd64] (zesty-proposed/universe) [25.1+1-2] (no packageset) [13:58] -queuebot:#ubuntu-release- New binary: emacs25 [armhf] (zesty-proposed/universe) [25.1+1-2] (no packageset) [14:03] -queuebot:#ubuntu-release- Unapproved: accepted fwts [source] (xenial-proposed) [16.03.00-0ubuntu1.1] [14:28] -queuebot:#ubuntu-release- Unapproved: rejected fwts [source] (trusty-proposed) [14.03.01-0ubuntu4] [14:29] -queuebot:#ubuntu-release- New: accepted emacs25 [amd64] (zesty-proposed) [25.1+1-2] [14:29] -queuebot:#ubuntu-release- New: accepted emacs25 [i386] (zesty-proposed) [25.1+1-2] [14:29] -queuebot:#ubuntu-release- New: accepted emacs25 [ppc64el] (zesty-proposed) [25.1+1-2] [14:29] -queuebot:#ubuntu-release- New: accepted libirman [amd64] (zesty-proposed) [0.5.2-0.2~build1] [14:29] -queuebot:#ubuntu-release- New: accepted libirman [armhf] (zesty-proposed) [0.5.2-0.2~build1] [14:29] -queuebot:#ubuntu-release- New: accepted libirman [powerpc] (zesty-proposed) [0.5.2-0.2~build1] [14:29] -queuebot:#ubuntu-release- New: accepted libirman [s390x] (zesty-proposed) [0.5.2-0.2~build1] [14:29] -queuebot:#ubuntu-release- New: accepted emacs25 [armhf] (zesty-proposed) [25.1+1-2] [14:29] -queuebot:#ubuntu-release- New: accepted emacs25 [s390x] (zesty-proposed) [25.1+1-2] [14:29] -queuebot:#ubuntu-release- New: accepted libirman [i386] (zesty-proposed) [0.5.2-0.2~build1] [14:29] -queuebot:#ubuntu-release- New: accepted pcp [amd64] (zesty-proposed) [3.11.5] [14:29] -queuebot:#ubuntu-release- New: accepted emacs25 [powerpc] (zesty-proposed) [25.1+1-2] [14:29] -queuebot:#ubuntu-release- New: accepted libirman [ppc64el] (zesty-proposed) [0.5.2-0.2~build1] [14:29] -queuebot:#ubuntu-release- New: accepted libirman [arm64] (zesty-proposed) [0.5.2-0.2~build1] [14:30] bagel/s390x builds "fine" locally. however it runs and ignores test-suite results. [14:30] which appear to get stuck on launchpad. hitting retry, if that gets stuck as well, I shall disable running the test-suite on s390x. [14:33] xnox: Lemme go watch the build in progress. [14:37] -queuebot:#ubuntu-release- Unapproved: fwts (trusty-proposed/universe) [14.03.01-0ubuntu3 => 14.03.01-0ubuntu4] (no packageset) [16:19] xnox: Looks like bagel went fine on the retry. [16:20] hmmm.... bagels [16:47] bah [16:47] * ogra_ looks for food [17:35] is there anyone I could talk to about accepting new KDE packages for upload? [17:42] clivejo: if they are brand new packages, it's really better to get them accepted into Debian first [17:43] otherwise you're asking the Ubuntu archive team members to duplicate the "new package review" that is already being done by the Debian ftp masters team [17:43] but we'll like to work on them in the time it takes Debian to publish them [17:44] sgclark: how did you get new packages into Ubuntu in the past? [17:44] you could try pinging one of the Debian ftp masters… [17:44] (hint: ScottK can do Debian NEW review, and also cares about KDE) [17:45] Im trying to get kirigami into zesty [17:45] and will have lot of PIM related packages when we get that far [17:46] could someone please reject golang-go.crypto in xenial queue, it's wrong [17:46] Anyhow, it's not impossible to get a NEW package into Ubuntu, you just need someone to sponsor the upload. [17:46] cyphermox: Done. [17:46] ta [17:47] -queuebot:#ubuntu-release- Unapproved: rejected golang-go.crypto [source] (xenial-proposed) [1:0.0~git20161012.0.5f31782-1ubuntu0.16.04.1] [17:47] who can I get to sponsor it? [17:48] clivejo: I didn't. Had to beg. Try shadeslayer or ScottK [17:48] its the begging I dont like! [17:48] well then study up for MOTD :) [17:49] well then study up for MOTU rather [17:49] LOL, you first! [17:50] I probably should. So much to do, so little time. [17:50] then I can beg you :) [17:52] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (xenial-proposed/universe) [0.9+16.04ubuntu1 => 0.10+16.04ubuntu1] (no packageset) [17:53] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (yakkety-proposed/universe) [0.9+16.10ubuntu1 => 0.10+16.10ubuntu1] (no packageset) [18:05] -queuebot:#ubuntu-release- Unapproved: lxcfs (trusty-backports/universe) [2.0.3-0ubuntu1~ubuntu14.04.1 => 2.0.4-0ubuntu1~ubuntu14.04.1] (no packageset) [18:12] -queuebot:#ubuntu-release- Unapproved: lxc (trusty-backports/main) [2.0.4-0ubuntu1~ubuntu14.04.1 => 2.0.5-0ubuntu1~ubuntu14.04.1] (ubuntu-server) [18:16] -queuebot:#ubuntu-release- Unapproved: lxd (trusty-backports/universe) [2.0.4-0ubuntu1~ubuntu14.04.1 => 2.0.5-0ubuntu1~ubuntu14.04.1] (no packageset) [18:22] -queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (trusty-backports) [2.0.5-0ubuntu1~ubuntu14.04.1] [18:22] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (trusty-backports) [2.0.5-0ubuntu1~ubuntu14.04.1] [18:22] -queuebot:#ubuntu-release- Unapproved: accepted lxcfs [source] (trusty-backports) [2.0.4-0ubuntu1~ubuntu14.04.1] [18:38] -queuebot:#ubuntu-release- Unapproved: lxd (xenial-backports/main) [2.0.5-0ubuntu1~ubuntu16.04.1 => 2.4.1-0ubuntu1~ubuntu16.04.1] (edubuntu, ubuntu-server) [18:40] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (xenial-backports) [2.4.1-0ubuntu1~ubuntu16.04.1] [19:12] who could speak to debconf prompting being broken on Ubuntu-GNOME? jbicha ? LP: #1605376, LP: #1636597 [19:12] Launchpad bug 1605376 in shim-signed (Ubuntu) "(Ubuntu-GNOME, debconf passthrough) package shim-signed 1.17~15.10.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128" [High,New] https://launchpad.net/bugs/1605376 [19:12] Launchpad bug 1636597 in shim-signed (Ubuntu) "(Ubuntu-GNOME, debconf passthrough) package shim-signed 1.18~16.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128" [Undecided,New] https://launchpad.net/bugs/1636597 [19:36] slangasek: Ubuntu GNOME shouldn't be doing anything with debconf different than Ubuntu (Unity) [19:37] -queuebot:#ubuntu-release- Unapproved: lightdm (yakkety-proposed/main) [1.19.5-0ubuntu1 => 1.20.0-0ubuntu2] (kubuntu, ubuntu-desktop) [19:40] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (yakkety-proposed/main) [1:16.10.7 => 1:16.10.8] (core) [19:40] jbicha: well, that's definitely not the case, because Ubuntu-GNOME users get this error and nobody else does [19:40] jbicha: aptdaemon? packagekit? [19:41] -queuebot:#ubuntu-release- Unapproved: rejected lightdm [source] (yakkety-proposed) [1.20.0-0ubuntu2] [19:41] but Ubuntu GNOME 16.04 uses the exact same update tools as Ubuntu (Unity) [19:42] I was fairly sure libgtk2-perl was required to make debconf popups DTRT, but I note it's not in ubuntu-desktop either... [19:43] it may be the same tools, but they're clearly wired up differently [19:43] Or does update-manager do its own magic? [19:43] Ubuntu GNOME users get this error, Ubuntu Desktop users do not [19:43] infinity: no, update-manager passes through to debconf [19:44] slangasek: Which would then imply that without libgtk2-perl, people are getting text prompts in the little terminal window... [19:44] I think. [19:44] hmm I have libgtk2-perl installed here, maybe that's why /my/ debconf is broken ;P [19:45] it feels like a stretch to me to say based on 2 bug reports that there's a major problem with Ubuntu GNOME's debconf… [19:47] it's not 2 bugs, those are the two I happened to have the numbers to hand for [19:47] oh ok, well I don't know anything about debconf :( [19:48] I'm having a hard time seeing how this would differ between Ubuntu and Ubuntu GNOME, other than dumb luck. [19:48] And "dumb luck" is never a good engineering strategy. [19:48] #1605376 #1605977 #1636597; so three bugs ;) [19:48] (which is 3 out of 16 open bugs) [19:49] there are also bugs with similar symptoms for Ubuntu Desktop, but only on trusty [19:49] slangasek: Conclusion, all our users reinstalled with GNOME after trusty. [19:49] lol [19:50] all 3 of them! [19:50] (Probably not) [19:52] Unrelated: daily ISOs are cronned again and should start hitting the tracker over the next 24h. [19:52] (base is there already, as it was the testcase) [20:09] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (xenial-proposed/main) [1:16.04.17 => 1:16.04.18] (core) [20:25] pitti: it's a bit offtopic here but I have the impression I found a bug in autopktest, if you have a minute we could have a brief chat about it [20:30] infinity: if there's an nginx in zesty-proposed (held thanks to Perl migration), is there a problem with me putting another package into proposed that has a higher version that includes a fix for a CVE that was fixed by the Security team? Ahead of the planned merge I'm working on from Debian, that is. Or should I wait for my 'merge' to be ready for review (after the Perl migration, probably) [20:54] teward: the perl transition is going to take a while to finish up; if the new nginx merge doesn't bring other dependency issues, that should be ok [20:54] teward: I mean that merging the new one should be ok [20:56] slangasek: the merge is weeks away - the headache of switching from the static-binary builds to dynamic modules *and* a static binary is... treacherous [20:57] teward: oh, you mean an upload that just adds the security fix. yeah, there's absolutely no reason for you to not do that here [20:57] the upload that'd be done now is basically borrowing the changes done by mdeslaur to the Yakkety package and apply that to the Zesty package, until such time it's in debian and get absorbed into the merge. [20:57] yeah [20:57] slangasek: wanted to make sure it wouldn't torpedo anything [20:57] i want that security fix in, not the merge, at this point. [20:57] assuming the Security team has no objection. cc: mdeslaur [21:10] -queuebot:#ubuntu-release- Unapproved: golang-go.crypto (yakkety-proposed/main) [1:0.0~git20161012.0.5f31782-1ubuntu0.16.10.1 => 1:0.0~git20161012.0.5f31782-1ubuntu0.16.10.2] (kubuntu, ubuntu-desktop) [21:33] slangasek, can you force boost1.60 & boost1.61 to become valid candidates; such that openmpi doom migrates; and i start boost1.62 transition, please =) [21:33] slangasek, also mongodb 3.2 does not build on armhf, could you please remove mongodb/armhf from zesty-release pocket? [21:34] missing build on armhf: mongodb, mongodb-clients, mongodb-server (from 1:2.6.11-1ubuntu1) [22:42] xnox: boost1.6x are not the cause of openmpi not being a candidate; but let's look at them anyway. can you give me details about why the autopkgtest regressions should be overridden?