[06:16] -queuebot:#ubuntu-release- New: accepted selectors34 [amd64] (zesty-proposed) [1.1.0-1]
[06:27] -queuebot:#ubuntu-release- New binary: ciphersaber [amd64] (zesty-proposed/universe) [1.01-2ubuntu1] (no packageset)
[07:10] <ginggs> would somebody please 'force-badtest monkeysign/2.2.3/i386 monkeysign/2.2.3/ppc64el' - it seems to have accidentally passed once on those
[07:38] <apw> ginggs, done
[07:38] <ginggs> apw: thanks!
[07:42] -queuebot:#ubuntu-release- New source: kirigami2 (zesty-proposed/primary) [2.0.0-0ubuntu1]
[10:24] -queuebot:#ubuntu-release- New source: mozjs38 (zesty-proposed/primary) [38.2.1~rc0-0ubuntu1]
[10:55] <xnox> will there be a d-i rebuild for 16.04.2?
[10:55] -queuebot:#ubuntu-release- Unapproved: ndiswrapper (xenial-proposed/universe) [1.59-6 => 1.60-3~ubuntu16.04.1] (no packageset)
[11:12] <davmor2> xnox: oh I hope not I was hoping to start testing it once I knew if the new kernel landed or not :)
[11:19] <xnox> davmor2, well, xenial d-i is at "Move master kernels to 4.4.0-31." yet latest -security and -updates abi is 4.4.0-62 and latest -proposed is 4.4.0-63.84
[11:20] <xnox> thus i'm going to work under assumption that we will have d-i respin.
[11:30] <davmor2> xnox: I'd say a full resping to be honest I think that is the kernel we are waiting on potentially
[11:46] <apw> xnox, would assume infinity has some extensive work for the dual kernel enablement somewhere
[11:53] -queuebot:#ubuntu-release- Unapproved: accepted ndiswrapper [source] (xenial-proposed) [1.60-3~ubuntu16.04.1]
[11:53] <acheronuk> .
[11:53] <acheronuk> Hi. Can someone please review and accept our sources in the NEW queue please? they are needed before we can our packageset refresh done.
[11:53] <acheronuk> namely minuet, konqueror, kommander, klinkstatus, kimagemapeditor,kfind, kfilereplace, keditbookmarks, kdialog
[11:53] <acheronuk> thanks
[11:53] <acheronuk> most of those are actually OLD packages, but KDE have now split the sources
[11:53] <acheronuk> .
[11:53] <acheronuk> minuet is part of the full KDE applications 16.04.0 release that we were unable to get into yakkety, due to not have some build depends for it in the archive
[11:53] <acheronuk> see: https://www.kde.org/announcements/announce-applications-16.04.0.php
[11:54] <acheronuk> in 16.12 KDE app we are now doing...
[11:54] <acheronuk> kde-baseapps (split into kdialog, keditbookmarks, kfind, konqueror)
[11:54] <acheronuk> kdewebdev (split into kfilereplace, kimagemapeditor, klinkstatus, kommander)
[11:54] <acheronuk> hence these are nothing new per se. just split and some ported to KF5
[11:54] <acheronuk> see: https://community.kde.org/Applications/16.12_Release_Notes#Tarballs_that_we_have_split
[11:54] <acheronuk> .
[11:54] <acheronuk> kirigami2 is a new plasma 5.9 dependency that debian have packaging for, but not done yet as they are still on plasma 5.8
[11:54] <acheronuk> thanks :)
[12:04] -queuebot:#ubuntu-release- Unapproved: mysql-5.7 (xenial-proposed/main) [5.7.17-0ubuntu0.16.04.1 => 5.7.17-0ubuntu0.16.04.2] (core)
[12:04] <rbasak> ^ sponsored by me, so I can't SRU review.
[12:07] <apw> rbasak, is there a yakkety coming for that too ?
[12:08] <rbasak> apw: not planned.
[12:09] <rbasak> apw: we're prioritising Xenial, and there's another important bug we want to focus on for Xenial first, just a bit more involved to fix so we didn't want to delay these fixes to Xenial any further. By the time we get that sorted, it probably won't be worth doing Yakkety.
[12:10] <rbasak> (also we have to slot in the SRUs between security updates)
[12:15] <apw> rbasak, and zesty is already fixed for these at least ?
[12:25] <rbasak> apw: yes, Zesty is fixed for all.
[12:25] <rbasak> (of the bugs)
[12:26] <rbasak> apw: oh, if you're reviewing, we have broken down git commits if that makes it easier.
[12:28] <rbasak> apw: https://anonscm.debian.org/cgit/pkg-mysql/mysql.git/log/?h=mysql-5.7/rbasak/ubuntu/xenial
[12:31] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-63.84]
[12:52] <apw> rbasak, well the diff looks ok to me, i am a little supprised we could not apply these changes to yakkety too, but
[13:06] -queuebot:#ubuntu-release- Unapproved: accepted mysql-5.7 [source] (xenial-proposed) [5.7.17-0ubuntu0.16.04.2]
[13:29] <cpaelzer> Hi, could one of the SRU Team take a look at moving the libvirt in bug 1637601 forward?
[13:30] <apw> cpaelzer, for xenial ?  that has a failing ADT test ...
[13:31] <apw> cpaelzer, a nova test failure with it
[13:31] <cpaelzer> apw: really, thanks for the info
[13:32] <cpaelzer> apw: that nova failure sounds familiar from another place (where it isn't fixed either)
[13:32] <cpaelzer> might be a good info to add to the other discussion - checking
[13:32] <apw> cpaelzer, if it is a nova issue rather than a libvirt issue then that can be ignored ... if
[13:34] <cpaelzer> apw: the libvirt change is totally unrelated, yet I like to have them green or really understood - taking a look
[13:35] <apw> cpaelzer, i will also throw it at the wall and confirm it is reproducible
[13:41] <apw> cpaelzer, so that looks to retry ok, so ... i'll wait for the regression to go away in the reports and we can release it
[13:46] <apw> cpaelzer, well of course other than the fact it is seeded, and we are preparing a point release
[13:51] <apw> cpaelzer, will confer with the point release release coordinator and find out, it is at least elidgable now
[13:52] <cpaelzer> apw: I hit rerun as this never occurred to me in about 10 related builds in bileto + dep8 tests
[13:52] <cpaelzer> apw: it now passed as expected
[13:52] <cpaelzer> apw: the log itself of the issue was not pointing to anything related with the change
[13:52] <apw> cpaelzer, yeah both passed so it is even reliably passing
[13:53] <cpaelzer> apw: do you see anything else in the SRU process that might stall it I should look into?
[13:55] <apw> cpaelzer, it is now eligable to release as far as i can see, it is just need to check on the point release
[13:57] <cpaelzer> apw: I beg a pardon - what is "need to check on the point release" - ensuring it doesn't pull in other dependencies to the point release?
[13:58] <apw> cpaelzer, i believe we are frozen for the point release so any promotions need an ack from adam
[13:59] <cpaelzer> ok, thanks
[14:02] <ginggs> Laney: fyi, ncbi-tools6 (the package that no longer has autopkgtests) has another upload (still without tests)
[15:43] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [0.7.9-0ubuntu1~16.04.1]
[16:09] -queuebot:#ubuntu-release- Unapproved: multipath-tools (yakkety-proposed/main) [0.5.0+git1.656f8865-5ubuntu7.1 => 0.5.0+git1.656f8865-5ubuntu7.2] (core)
[16:10] -queuebot:#ubuntu-release- Unapproved: multipath-tools (xenial-proposed/main) [0.5.0+git1.656f8865-5ubuntu2.3 => 0.5.0+git1.656f8865-5ubuntu2.4] (core)
[16:45] <Laney> ginggs: nobody reviewed my branch yet
[16:48] <Laney> (please feel free!)
[18:21] -queuebot:#ubuntu-release- New binary: prison-kf5 [ppc64el] (zesty-proposed/universe) [5.30.0-0ubuntu1] (no packageset)
[18:22] -queuebot:#ubuntu-release- New binary: prison-kf5 [amd64] (zesty-proposed/universe) [5.30.0-0ubuntu1] (no packageset)
[18:22] -queuebot:#ubuntu-release- New binary: prison-kf5 [armhf] (zesty-proposed/universe) [5.30.0-0ubuntu1] (no packageset)
[18:22] -queuebot:#ubuntu-release- New binary: prison-kf5 [powerpc] (zesty-proposed/universe) [5.30.0-0ubuntu1] (no packageset)
[18:22] -queuebot:#ubuntu-release- New binary: prison-kf5 [arm64] (zesty-proposed/universe) [5.30.0-0ubuntu1] (no packageset)
[18:22] -queuebot:#ubuntu-release- New binary: prison-kf5 [s390x] (zesty-proposed/universe) [5.30.0-0ubuntu1] (no packageset)
[18:22] -queuebot:#ubuntu-release- New binary: prison-kf5 [i386] (zesty-proposed/universe) [5.30.0-0ubuntu1] (no packageset)
[18:41] <clivejo> ^ Can someone please accept those new binaries for prison-kf5?
[19:55] <apw> clivejo, should there not be an actual library in those prison-kf5 binaries?
[20:03] <clivejo> apw: yes, libkf5prison5
[20:06] <clivejo> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/prison/tree/debian/control?h=kubuntu_zesty_archive
[20:09] <clivejo> usr/lib/*/libKF5Prison.so.5.30.0
[20:10] <apw> clivejo, does not appear to be in the package ....
[20:10] <apw> $ less ~/Downloads/libkf5prison-dev_5.30.0-0ubuntu1_amd64.deb | grep libKF5Prison.so
[20:10] <apw> lrwxrwxrwx root/root         0 2017-02-06 16:33 ./usr/lib/x86_64-linux-gnu/libKF5Prison.so -> libKF5Prison.so.5
[20:10] <apw> $
[20:11] <apw> oh dammit, what is that doing there
[20:11] <clivejo> https://launchpadlibrarian.net/305376446/buildlog_ubuntu-zesty-amd64.prison-kf5_5.30.0-0ubuntu1_BUILDING.txt.gz
[20:11] <clivejo> -rw-r--r-- root/root     43536 2017-02-06 16:33 ./usr/lib/x86_64-linux-gnu/libKF5Prison.so.5.30.0
[20:11] <apw> sorry dirty Downloads directory, let me do that again
[20:11] <acheronuk> https://launchpad.net/ubuntu/+source/prison-kf5/5.30.0-0ubuntu1/+build/11973048
[20:12] <acheronuk> http://i.imgur.com/WFR23Lw.png
[20:12] <apw> ok there it is, all is as it should be, ignore me
[20:12] <acheronuk> ah, ok
[20:12] <clivejo> apw: will you accept it?
[20:12] <apw> clivejo, looking
[20:14] <slangasek> infinity, bdmurray: what's the existing best implementation we have of figuring out who to email about a given upload?  So that robru can leverage this for p-m to email uploaders about stuck migrations
[20:18] -queuebot:#ubuntu-release- New: accepted prison-kf5 [amd64] (zesty-proposed) [5.30.0-0ubuntu1]
[20:18] -queuebot:#ubuntu-release- New: accepted prison-kf5 [armhf] (zesty-proposed) [5.30.0-0ubuntu1]
[20:18] -queuebot:#ubuntu-release- New: accepted prison-kf5 [powerpc] (zesty-proposed) [5.30.0-0ubuntu1]
[20:18] -queuebot:#ubuntu-release- New: accepted prison-kf5 [s390x] (zesty-proposed) [5.30.0-0ubuntu1]
[20:18] -queuebot:#ubuntu-release- New: accepted prison-kf5 [arm64] (zesty-proposed) [5.30.0-0ubuntu1]
[20:18] -queuebot:#ubuntu-release- New: accepted prison-kf5 [ppc64el] (zesty-proposed) [5.30.0-0ubuntu1]
[20:18] -queuebot:#ubuntu-release- New: accepted prison-kf5 [i386] (zesty-proposed) [5.30.0-0ubuntu1]
[20:19] <clivejo> apw: could you take a look at our other packages in the queue please?
[20:20] <apw> clivejo, the main blocker on those (for me) is that some of them have epoch's which though they seem very reasonable to us, could be avoided in debian and create a missmatch ...
[20:21] <apw> clivejo, do we have buy in from the Debian KDE maintainers for the source split packaging ?
[20:22] <clivejo> well I cant see how they could not split them, as upstream have split the git repo's
[20:22] <apw> clivejo, they could (in theory) have no epoch on the source and still ahve an epoch on the binaries, which does seem mad, but ...
[20:23] <clivejo> Ive never seen them do that
[20:23] <clivejo> they are annoying, but thats asking for trouble
[20:26] <jbicha> for instance, bsdutils has an epoch but the rest of the util-linux binaries and source do not
[20:27] <jbicha> https://sources.debian.net/src/util-linux/2.29-1/debian/rules/?hl=138#L138
[20:28] <clivejo> is there one instance in particular is concerning?
[20:30] <apw> release-team people by definition are risk averse, and epoch-en are essentially impossible to remove
[20:32] <clivejo> apw: kirigami2 is essential for us right now, would you look at it please?
[20:32] <clivejo> discover = KDE Plasma sofware install centre
[20:33] <clivejo> and we need kirigami2 for it, both build and runtime
[20:36] <clivejo> why do we need kirigami and kirigami2 I bet you are thinking!
[20:36] <clivejo> https://dot.kde.org/2017/01/12/kde-releases-kirigami-ui-20
[20:59] <bdmurray> slangasek: the phased-updater code looks at the launchpad signer and fallsback to parsing the changes file for Changed-By
[21:02] <nacc> jbicha: is that because bsdutils changed src packages (based upon 2.9i-1 entry in d/changelog)?
[21:09] <slangasek> robru: ^^ so that answer from bdmurray is probably what you want as a best-practices starting point
[21:10] <robru> bdmurray: slangasek thanks
[21:26] <acheronuk> yes, plasma-discover, our software centre, now requires kirigami2, which can only be a separate source due to v1 and v2 being incompatible, and KDE applications/plasma in requiring both at the moment
[21:26] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [0.7.9-0ubuntu1~16.04.1 => 0.7.9-0ubuntu1~16.04.2] (edubuntu, ubuntu-cloud, ubuntu-server)
[21:26] <acheronuk> we cannot choose to use v1 even if we wished to
[21:28] <acheronuk> ditto for the other new queue items.
[21:31] <acheronuk> kirigami2 ins debian git: https://anonscm.debian.org/cgit/pkg-kde/kde-extras/kirigami2.git/
[21:31] <acheronuk> kirigami2 in arch https://www.archlinux.org/packages/extra/x86_64/kirigami2/
[21:32] <acheronuk> kirigami2 in opensuse https://software.opensuse.org/package/kirigami2
[21:33] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [0.7.9-0ubuntu1~16.04.2]
[21:37] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (yakkety-proposed) [0.7.9-0ubuntu1~16.10.1]
[21:39] -queuebot:#ubuntu-release- Unapproved: cloud-init (yakkety-proposed/main) [0.7.8-68-gca3ae67-0ubuntu1~16.10.1 => 0.7.9-0ubuntu1~16.10.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[21:43] <acheronuk> plasma-discover is sitting patently waiting for it's kirigami2 here: https://launchpad.net/ubuntu/+source/plasma-discover/5.9.0-0ubuntu1
[21:43]  * acheronuk will shut up now
[21:55] <acheronuk> apw: please see: http://paste.ubuntu.com/23943739/
[22:00] <acheronuk> apw: from debian kde-qt devs in #debian-qt-kde on OFTC
[22:02] <jgrimm> tjaalton, dogtag-pki update-excuses failures discussion last week.. iirc you felt it was tomcat issue, needing some AA help to hold-back/clean-out tomcat?
[22:03] <jgrimm> tjaalton, wondering if you'd attempted to get an AA's attention to help sort?
[22:05] <tjaalton> jgrimm: kinda, sent an email to ubuntu-release
[22:06] <jgrimm> tjaalton, ah.. :)   ok, didn't want to double-nag folks