/srv/irclogs.ubuntu.com/2017/02/06/#ubuntu-release.txt

-queuebot:#ubuntu-release- New: accepted selectors34 [amd64] (zesty-proposed) [1.1.0-1]06:16
-queuebot:#ubuntu-release- New binary: ciphersaber [amd64] (zesty-proposed/universe) [1.01-2ubuntu1] (no packageset)06:27
ginggswould somebody please 'force-badtest monkeysign/2.2.3/i386 monkeysign/2.2.3/ppc64el' - it seems to have accidentally passed once on those07:10
apwginggs, done07:38
ginggsapw: thanks!07:38
-queuebot:#ubuntu-release- New source: kirigami2 (zesty-proposed/primary) [2.0.0-0ubuntu1]07:42
-queuebot:#ubuntu-release- New source: mozjs38 (zesty-proposed/primary) [38.2.1~rc0-0ubuntu1]10:24
xnoxwill 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)10:55
davmor2xnox: oh I hope not I was hoping to start testing it once I knew if the new kernel landed or not :)11:12
xnoxdavmor2, 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.8411:19
xnoxthus i'm going to work under assumption that we will have d-i respin.11:20
=== jamespag` is now known as jamespage
davmor2xnox: I'd say a full resping to be honest I think that is the kernel we are waiting on potentially11:30
apwxnox, would assume infinity has some extensive work for the dual kernel enablement somewhere11:46
-queuebot:#ubuntu-release- Unapproved: accepted ndiswrapper [source] (xenial-proposed) [1.60-3~ubuntu16.04.1]11:53
acheronuk.11:53
acheronukHi. 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
acheronuknamely minuet, konqueror, kommander, klinkstatus, kimagemapeditor,kfind, kfilereplace, keditbookmarks, kdialog11:53
acheronukthanks11:53
acheronukmost of those are actually OLD packages, but KDE have now split the sources11:53
acheronuk.11:53
acheronukminuet 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 archive11:53
acheronuksee: https://www.kde.org/announcements/announce-applications-16.04.0.php11:53
acheronukin 16.12 KDE app we are now doing...11:54
acheronukkde-baseapps (split into kdialog, keditbookmarks, kfind, konqueror)11:54
acheronukkdewebdev (split into kfilereplace, kimagemapeditor, klinkstatus, kommander)11:54
acheronukhence these are nothing new per se. just split and some ported to KF511:54
acheronuksee: https://community.kde.org/Applications/16.12_Release_Notes#Tarballs_that_we_have_split11:54
acheronuk.11:54
acheronukkirigami2 is a new plasma 5.9 dependency that debian have packaging for, but not done yet as they are still on plasma 5.811:54
acheronukthanks :)11:54
-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:04
apwrbasak, is there a yakkety coming for that too ?12:07
rbasakapw: not planned.12:08
rbasakapw: 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:09
rbasak(also we have to slot in the SRUs between security updates)12:10
apwrbasak, and zesty is already fixed for these at least ?12:15
rbasakapw: yes, Zesty is fixed for all.12:25
rbasak(of the bugs)12:25
rbasakapw: oh, if you're reviewing, we have broken down git commits if that makes it easier.12:26
rbasakapw: https://anonscm.debian.org/cgit/pkg-mysql/mysql.git/log/?h=mysql-5.7/rbasak/ubuntu/xenial12:28
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-63.84]12:31
=== marcusto_ is now known as marcustomlinson
apwrbasak, well the diff looks ok to me, i am a little supprised we could not apply these changes to yakkety too, but12:52
-queuebot:#ubuntu-release- Unapproved: accepted mysql-5.7 [source] (xenial-proposed) [5.7.17-0ubuntu0.16.04.2]13:06
cpaelzerHi, could one of the SRU Team take a look at moving the libvirt in bug 1637601 forward?13:29
ubot5bug 1637601 in libvirt (Ubuntu Xenial) "UbuntuKVM: migration using NFS mount fails #190" [Medium,Fix committed] https://launchpad.net/bugs/163760113:29
apwcpaelzer, for xenial ?  that has a failing ADT test ...13:30
apwcpaelzer, a nova test failure with it13:31
cpaelzerapw: really, thanks for the info13:31
cpaelzerapw: that nova failure sounds familiar from another place (where it isn't fixed either)13:32
cpaelzermight be a good info to add to the other discussion - checking13:32
apwcpaelzer, if it is a nova issue rather than a libvirt issue then that can be ignored ... if13:32
cpaelzerapw: the libvirt change is totally unrelated, yet I like to have them green or really understood - taking a look13:34
apwcpaelzer, i will also throw it at the wall and confirm it is reproducible13:35
apwcpaelzer, so that looks to retry ok, so ... i'll wait for the regression to go away in the reports and we can release it13:41
apwcpaelzer, well of course other than the fact it is seeded, and we are preparing a point release13:46
apwcpaelzer, will confer with the point release release coordinator and find out, it is at least elidgable now13:51
cpaelzerapw: I hit rerun as this never occurred to me in about 10 related builds in bileto + dep8 tests13:52
cpaelzerapw: it now passed as expected13:52
cpaelzerapw: the log itself of the issue was not pointing to anything related with the change13:52
apwcpaelzer, yeah both passed so it is even reliably passing13:52
cpaelzerapw: do you see anything else in the SRU process that might stall it I should look into?13:53
apwcpaelzer, it is now eligable to release as far as i can see, it is just need to check on the point release13:55
cpaelzerapw: 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:57
apwcpaelzer, i believe we are frozen for the point release so any promotions need an ack from adam13:58
cpaelzerok, thanks13:59
ginggsLaney: fyi, ncbi-tools6 (the package that no longer has autopkgtests) has another upload (still without tests)14:02
=== santa is now known as Guest38912
=== Guest38912 is now known as santa_
=== ara_ is now known as ara
=== ara is now known as Guest93169
-queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [0.7.9-0ubuntu1~16.04.1]15:43
-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:09
-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:10
Laneyginggs: nobody reviewed my branch yet16:45
Laney(please feel free!)16:48
-queuebot:#ubuntu-release- New binary: prison-kf5 [ppc64el] (zesty-proposed/universe) [5.30.0-0ubuntu1] (no packageset)18:21
-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:22
clivejo^ Can someone please accept those new binaries for prison-kf5?18:41
apwclivejo, should there not be an actual library in those prison-kf5 binaries?19:55
clivejoapw: yes, libkf5prison520:03
clivejohttps://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/prison/tree/debian/control?h=kubuntu_zesty_archive20:06
clivejousr/lib/*/libKF5Prison.so.5.30.020:09
apwclivejo, does not appear to be in the package ....20:10
apw$ less ~/Downloads/libkf5prison-dev_5.30.0-0ubuntu1_amd64.deb | grep libKF5Prison.so20:10
apwlrwxrwxrwx root/root         0 2017-02-06 16:33 ./usr/lib/x86_64-linux-gnu/libKF5Prison.so -> libKF5Prison.so.520:10
apw$20:10
apwoh dammit, what is that doing there20:11
clivejohttps://launchpadlibrarian.net/305376446/buildlog_ubuntu-zesty-amd64.prison-kf5_5.30.0-0ubuntu1_BUILDING.txt.gz20:11
clivejo-rw-r--r-- root/root     43536 2017-02-06 16:33 ./usr/lib/x86_64-linux-gnu/libKF5Prison.so.5.30.020:11
apwsorry dirty Downloads directory, let me do that again20:11
acheronukhttps://launchpad.net/ubuntu/+source/prison-kf5/5.30.0-0ubuntu1/+build/1197304820:11
acheronukhttp://i.imgur.com/WFR23Lw.png20:12
apwok there it is, all is as it should be, ignore me20:12
acheronukah, ok20:12
clivejoapw: will you accept it?20:12
apwclivejo, looking20:12
slangasekinfinity, 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 migrations20:14
-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:18
clivejoapw: could you take a look at our other packages in the queue please?20:19
apwclivejo, 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:20
apwclivejo, do we have buy in from the Debian KDE maintainers for the source split packaging ?20:21
clivejowell I cant see how they could not split them, as upstream have split the git repo's20:22
apwclivejo, they could (in theory) have no epoch on the source and still ahve an epoch on the binaries, which does seem mad, but ...20:22
clivejoIve never seen them do that20:23
clivejothey are annoying, but thats asking for trouble20:23
jbichafor instance, bsdutils has an epoch but the rest of the util-linux binaries and source do not20:26
jbichahttps://sources.debian.net/src/util-linux/2.29-1/debian/rules/?hl=138#L13820:27
clivejois there one instance in particular is concerning?20:28
apwrelease-team people by definition are risk averse, and epoch-en are essentially impossible to remove20:30
clivejoapw: kirigami2 is essential for us right now, would you look at it please?20:32
clivejodiscover = KDE Plasma sofware install centre20:32
clivejoand we need kirigami2 for it, both build and runtime20:33
clivejowhy do we need kirigami and kirigami2 I bet you are thinking!20:36
clivejohttps://dot.kde.org/2017/01/12/kde-releases-kirigami-ui-2020:36
bdmurrayslangasek: the phased-updater code looks at the launchpad signer and fallsback to parsing the changes file for Changed-By20:59
naccjbicha: is that because bsdutils changed src packages (based upon 2.9i-1 entry in d/changelog)?21:02
slangasekrobru: ^^ so that answer from bdmurray is probably what you want as a best-practices starting point21:09
robrubdmurray: slangasek thanks21:10
acheronukyes, 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 moment21: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
acheronukwe cannot choose to use v1 even if we wished to21:26
acheronukditto for the other new queue items.21:28
acheronukkirigami2 ins debian git: https://anonscm.debian.org/cgit/pkg-kde/kde-extras/kirigami2.git/21:31
acheronukkirigami2 in arch https://www.archlinux.org/packages/extra/x86_64/kirigami2/21:31
acheronukkirigami2 in opensuse https://software.opensuse.org/package/kirigami221:32
-queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [0.7.9-0ubuntu1~16.04.2]21:33
-queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (yakkety-proposed) [0.7.9-0ubuntu1~16.10.1]21:37
-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:39
acheronukplasma-discover is sitting patently waiting for it's kirigami2 here: https://launchpad.net/ubuntu/+source/plasma-discover/5.9.0-0ubuntu121:43
* acheronuk will shut up now21:43
acheronukapw: please see: http://paste.ubuntu.com/23943739/21:55
acheronukapw: from debian kde-qt devs in #debian-qt-kde on OFTC22:00
jgrimmtjaalton, 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:02
jgrimmtjaalton, wondering if you'd attempted to get an AA's attention to help sort?22:03
tjaaltonjgrimm: kinda, sent an email to ubuntu-release22:05
jgrimmtjaalton, ah.. :)   ok, didn't want to double-nag folks22:06
=== wxl_ is now known as wxl
=== Logan_ is now known as Logan
=== mapreri_ is now known as mapreri
=== andyrock_ is now known as andyrock
=== tai271828_ is now known as tai271828
=== Dmitrii-Sh_ is now known as Dmitrii-Sh
=== mpontillo_ is now known as mpontillo
=== wolsen_ is now known as wolsen
=== plars_ is now known as plars
=== DalekSec_ is now known as DalekSec

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!