/srv/irclogs.ubuntu.com/2017/07/04/#ubuntu-release.txt

-queuebot:#ubuntu-release- New binary: sundials [s390x] (artful-proposed/universe) [2.5.0-4] (no packageset)05:17
-queuebot:#ubuntu-release- New binary: sundials [ppc64el] (artful-proposed/universe) [2.5.0-4] (no packageset)05:18
-queuebot:#ubuntu-release- New: accepted sundials [ppc64el] (artful-proposed) [2.5.0-4]05:25
-queuebot:#ubuntu-release- New: accepted sundials [s390x] (artful-proposed) [2.5.0-4]05:25
-queuebot:#ubuntu-release- New binary: sundials [arm64] (artful-proposed/universe) [2.5.0-4] (no packageset)05:25
-queuebot:#ubuntu-release- New binary: sundials [armhf] (artful-proposed/universe) [2.5.0-4] (no packageset)05:27
-queuebot:#ubuntu-release- New: accepted sundials [arm64] (artful-proposed) [2.5.0-4]05:29
-queuebot:#ubuntu-release- New: accepted sundials [armhf] (artful-proposed) [2.5.0-4]05:29
-queuebot:#ubuntu-release- Unapproved: accepted mutter [source] (zesty-proposed) [3.24.2-0ubuntu0.1]06:52
-queuebot:#ubuntu-release- Unapproved: rejected apt [source] (yakkety-proposed) [1.3.7]06:54
-queuebot:#ubuntu-release- Unapproved: rejected mythtv [source] (yakkety-proposed) [2:0.28.0+fixes.20160413.15cf421-0ubuntu2.16.10.1]06:54
-queuebot:#ubuntu-release- Unapproved: rejected apt [source] (yakkety-proposed) [1.3.8]06:54
apw^ 3 duplicate in the queue06:58
-queuebot:#ubuntu-release- Unapproved: accepted sudo [source] (zesty-proposed) [1.8.19p1-1ubuntu1.2]07:05
apwtjaalton, it looks like your sudo fix for LP: #1686803 got lost in yakkety with the upload of a security update.07:21
ubot5Launchpad bug 1686803 in sudo (Ubuntu Yakkety) "sudo returns exit code 0 if child is killed with SIGTERM" [Undecided,New] https://launchpad.net/bugs/168680307:21
tjaaltonapw: bah, noone cares at this point :)07:22
tjaaltonI think07:22
apwtjaalton, bah that should be: bug #160766607:22
ubot5bug 1607666 in sudo (Ubuntu Yakkety) "sudo fails with host netgroup returned from freeipa" [Undecided,Fix committed] https://launchpad.net/bugs/160766607:22
tjaaltonlooks like it wouldn't get verified anyway07:23
* apw idly wonders how long yakkety has before EOL07:23
apwtjaalton, well it did in xenial and zesty i assume, and is released in those i think07:24
apwso we are left i in a bit of a muddle07:24
flocculantmorning - -running artful with kernel from -proposed, seem to have an issue with alsa and that kernel, can't report issue with ubuntu-bug (proposed I assume) not sure of best way to proceed (reported at least to alsa)07:24
flocculantapw: Ubuntu 16.10 will reach end of life on Wednesday, July 20, 201707:24
tjaaltonapw: I think it's fine to wontfix it, the guy says they don't deploy yakkety so can't test it07:24
tjaaltonzesty got the new upstream version07:25
-queuebot:#ubuntu-release- Unapproved: accepted sudo [source] (yakkety-proposed) [1.8.16-0ubuntu3.3]07:31
-queuebot:#ubuntu-release- Unapproved: accepted sudo [source] (xenial-proposed) [1.8.16-0ubuntu1.5]07:31
-queuebot:#ubuntu-release- Unapproved: accepted telegram-desktop [source] (zesty-proposed) [1.0.29-1ubuntu1.17.04.1]07:36
-queuebot:#ubuntu-release- Unapproved: accepted postfix [source] (zesty-proposed) [3.1.4-4ubuntu1]07:45
-queuebot:#ubuntu-release- Unapproved: accepted postfix [source] (yakkety-proposed) [3.1.0-5ubuntu1]07:46
-queuebot:#ubuntu-release- Unapproved: systemd (yakkety-proposed/main) [231-9ubuntu5 => 231-9ubuntu6] (core)11:06
sil2100jamespage: hey!11:27
jamespagesil2100: hello11:27
sil2100jamespage: I'm looking at releasing some of the packages that we have in -proposed - was looking at the ones frome LP: #169613911:28
ubot5Launchpad bug 1696139 in neutron-fwaas (Ubuntu Zesty) "[SRU] ocata stable releases" [Undecided,New] https://launchpad.net/bugs/169613911:28
sil2100jamespage: my question here is - do we need for all of them to be released at once?11:28
jamespagesil2100: ideally yes as we tested proposed, rather than individual parts11:29
sil2100jamespage: ok, in that case would you be able to test/get someone to test the two bugs that are still not verified? LP: #1649616 and LP: #167508811:32
ubot5Launchpad bug 1649616 in keystone (Ubuntu) "Keystone Token Flush job does not complete in HA deployed environment" [High,In progress] https://launchpad.net/bugs/164961611:32
ubot5Launchpad bug 1675088 in horizon (Ubuntu Zesty) "Restrict permissions on Openstack installation" [Medium,Triaged] https://launchpad.net/bugs/167508811:32
sil2100jamespage: once those are marked as verified I'll be able to flush the whole stack from -proposed at once11:32
sil2100Thanks!11:32
sil2100(those two bugs were included in the uploads of heat and keystone along with the 'new upstream release' bug)11:33
jamespagesil2100: that matches my expectations!11:37
sil2100jamespage: could you give me a ping once those two bugs are green?11:52
jamespagesil2100: can do12:08
LocutusOfBorgautopkgtest for apt/unknown: armhf: Regression ♻12:17
LocutusOfBorgWTF? armhf, you so sad12:17
apwLocutusOfBorg, retry it, i am starting to think we have a sad runner in the pool12:18
apwhave not had a chance to investigate it yet12:18
LocutusOfBorgapw, I already retried them, I'm having a look about how it goes12:18
apwi had a lot of those over the weekend i think it was, and retried them and most came out ok12:19
-queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (trusty-proposed) [20170622-0ubuntu1~14.04.0]12:19
LocutusOfBorgwonderful, I'll keep retry/check then12:20
LocutusOfBorgnot a good timing to upload perl :(12:20
LocutusOfBorgqueues were empty12:21
LocutusOfBorgapw, can we have libreoffice/i386 forced bad? I don't like that "ignore/retry" continuous kick12:22
LocutusOfBorgtestsuite sucks, and wasting power cycles for that is just useless12:22
-queuebot:#ubuntu-release- New binary: gce-compute-image-packages [amd64] (trusty-proposed/universe) [20170622-0ubuntu1~14.04.0] (ubuntu-cloud)12:22
-queuebot:#ubuntu-release- New binary: gce-compute-image-packages [ppc64el] (trusty-proposed/universe) [20170622-0ubuntu1~14.04.0] (ubuntu-cloud)12:22
-queuebot:#ubuntu-release- New binary: gce-compute-image-packages [i386] (trusty-proposed/universe) [20170622-0ubuntu1~14.04.0] (ubuntu-cloud)12:22
-queuebot:#ubuntu-release- New binary: gce-compute-image-packages [arm64] (trusty-proposed/universe) [20170622-0ubuntu1~14.04.0] (ubuntu-cloud)12:23
-queuebot:#ubuntu-release- New binary: gce-compute-image-packages [powerpc] (trusty-proposed/universe) [20170622-0ubuntu1~14.04.0] (ubuntu-cloud)12:23
LocutusOfBorgdoko, hello, do you want me to upload ghc building with bfd on arm64?12:24
-queuebot:#ubuntu-release- New binary: gce-compute-image-packages [armhf] (trusty-proposed/universe) [20170622-0ubuntu1~14.04.0] (ubuntu-cloud)12:25
-queuebot:#ubuntu-release- New: accepted gce-compute-image-packages [amd64] (trusty-proposed) [20170622-0ubuntu1~14.04.0]12:33
-queuebot:#ubuntu-release- New: accepted gce-compute-image-packages [armhf] (trusty-proposed) [20170622-0ubuntu1~14.04.0]12:33
-queuebot:#ubuntu-release- New: accepted gce-compute-image-packages [powerpc] (trusty-proposed) [20170622-0ubuntu1~14.04.0]12:33
-queuebot:#ubuntu-release- New: accepted gce-compute-image-packages [arm64] (trusty-proposed) [20170622-0ubuntu1~14.04.0]12:33
-queuebot:#ubuntu-release- New: accepted gce-compute-image-packages [ppc64el] (trusty-proposed) [20170622-0ubuntu1~14.04.0]12:33
-queuebot:#ubuntu-release- New: accepted gce-compute-image-packages [i386] (trusty-proposed) [20170622-0ubuntu1~14.04.0]12:33
-queuebot:#ubuntu-release- Unapproved: smartshine (zesty-proposed/universe) [0.36-0ubuntu2 => 0.36-0ubuntu2.17.04.1] (no packageset)13:09
-queuebot:#ubuntu-release- Unapproved: smartshine (xenial-proposed/universe) [0.36-0ubuntu2 => 0.36-0ubuntu2.16.04.1] (no packageset)13:11
-queuebot:#ubuntu-release- Unapproved: smartshine (trusty-proposed/universe) [0.36-0ubuntu2 => 0.36-0ubuntu2.14.04.1] (no packageset)13:12
sil2100Hello! Looking at the zesty NEW queue, I see someone approved the new gce-compute-image-packages binary for amd64 but not for all the other arches - does anyone know why it's like that?13:28
sil2100The xenial and yakkety binaries got accepted for all arches, same for trusty13:28
LocutusOfBorgapw, please make doxygen and freetype migrate? hinting libreoffice/i386 should be enough13:45
LocutusOfBorggstreamer, pango, cairo13:45
LocutusOfBorgall of them waiting for that libreoffice13:45
-queuebot:#ubuntu-release- Unapproved: accepted freeipa [source] (zesty-proposed) [4.4.3-3ubuntu2.1]14:09
-queuebot:#ubuntu-release- Unapproved: accepted libepoxy [source] (zesty-proposed) [1.3.1-1ubuntu1.17.04.2]14:35
-queuebot:#ubuntu-release- Unapproved: accepted libepoxy [source] (xenial-proposed) [1.3.1-1ubuntu0.16.04.2]14:36
-queuebot:#ubuntu-release- Unapproved: xorg-server-hwe-16.04 (xenial-proposed/main) [2:1.18.4-1ubuntu6.1~16.04.1 => 2:1.19.3-1ubuntu1~16.04.1] (no packageset)14:41
Saviqhi team, we got an email about mir/miral being stuck in artful-proposed for a few days now, are we in Alpha1 freeze or so?14:44
apwSaviq, nope14:45
Saviqany idea why those don't migrate then http://people.canonical.com/~ubuntu-archive/proposed-migration/artful/update_excuses.html#mir ?14:45
jbichaSaviq: thanks for asking, you need to rebuild unity-system-compositor14:46
jbichaafter that page, there's https://people.canonical.com/~ubuntu-archive/proposed-migration/artful/update_output.txt14:46
jbichawhich is a bit hard to read14:46
Saviqyeah, I can't parse that, sorry :D14:46
cjwatsonhttps://wiki.ubuntu.com/ProposedMigration has some advice on learning how to do so14:46
apwSaviq, from the huge list of things which are broken by those promoting, i assume they are creating an ABI break and you have not rebuilt everything that uses those ?14:47
cjwatsonalso, if the problem is that we're in a freeze, then update_excuses will say so explicitly14:47
apwhttp://paste.ubuntu.com/25018646/14:47
apwSaviq, ^ those are the relevant bits14:47
Saviqyup, thanks14:47
jbichaSaviq: I recommend rebuilding unity-system-compositor, that might be all you need14:48
Saviqjbicha, yeah I'm not sure that should happen, we'll look into it, thanks14:50
jbichaSaviq: libmirserver43 was bumped to 44 so everything that depends on 43 needs to be rebuilt14:52
-queuebot:#ubuntu-release- Unapproved: accepted hw-detect [source] (xenial-proposed) [1.117ubuntu2.2]14:53
apwSaviq, what jbicha said ... unity-system-compositor is linked against libmirserver43 so is broken if that mir migrates14:54
jbichaqtmir and qtmir-gles too14:54
-queuebot:#ubuntu-release- Unapproved: accepted hw-detect [source] (yakkety-proposed) [1.117ubuntu3.1]14:54
Saviqyeah, I'm not sure why those weren't part of that upload, we'll take care of that, thanks14:55
-queuebot:#ubuntu-release- Unapproved: rejected apt [source] (xenial-proposed) [1.2.23]14:55
TrevinhoHey, can someone from the SRU team promote https://launchpad.net/ubuntu/+source/unity-control-center/15.04.0+16.04.20170214-0ubuntu1 ?15:14
TrevinhoAs it's blocking the upcoming SRU15:14
-queuebot:#ubuntu-release- Unapproved: accepted sssd [source] (xenial-proposed) [1.13.4-1ubuntu1.6]15:27
slashdvtapia ^15:28
slashdsil2100, doing SRU today related work today ?15:45
slashddoing SRU related work today lol15:45
-queuebot:#ubuntu-release- Unapproved: lxcfs (xenial-proposed/main) [2.0.7-0ubuntu1~16.04.1 => 2.0.7-0ubuntu1~16.04.2] (edubuntu, ubuntu-server)15:45
sil2100slashd: yes, a bit, I didn't have time yesterday + the US guys are off15:47
sil2100But I'm finishing in a bit15:48
slashdsil2100, ok I'll ping the vanguard tomorrow then15:48
sil2100slashd: what's up? You need some action on something?15:48
slashdsil2100, was wondering if you could move multipath-tools from trusty-proposed to trusty-updates, if everything look good to you. I checked and everything lgtm15:50
sil2100I was looking at that today, need to remind myself what were my thoughts about that one15:50
slashdNote that pending SRU still shows LP:  1687004 has not verified, but it is, it simply that we did it a couples minutes ago and it didn't refresh the page yet.15:50
sil2100One moment15:50
ubot5Launchpad bug 1687004 in multipath-tools (Ubuntu Trusty) "multipath crash generating core dump" [Medium,Fix committed] https://launchpad.net/bugs/168700415:50
sil2100Ah15:50
slashdsil2100, sure15:50
sil2100Ok, yeah, probably wasn't verified back then15:51
slashdsil2100, yeah that was probably it, there is no clear way to reproduce it, as mentioned it is base on dump analysis15:51
slashdbut knowing Rafael he did a lot of testing using valgrind, etc ....15:52
slashdsil2100, they are both mark as green now in pending SRU15:53
sil2100Will take care of that one in a minute15:54
slashdsil2100, much appreciated15:54
slashdsil2100, and sorry for the changelog lp thing, I have took a note for next time.15:54
slashdre: sssd ^15:54
sil2100slashd: no worries, I didn't expect it to cause any issues with the tooling, but I guess it should be good now15:57
slashdsil2100, ack15:57
sil2100slashd: multipath-tools released o/16:00
slashdsil2100, thanks for this last minute request16:01
slashdtinoco, ^^16:01
sil2100np!16:02
tinocotau =)16:05
tinocotku =)16:05
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-85.108] (core, kernel)17:45
-queuebot:#ubuntu-release- Unapproved: lxcfs (yakkety-proposed/main) [2.0.7-0ubuntu1~16.10.1 => 2.0.7-0ubuntu1~16.10.2] (edubuntu, ubuntu-server)18:31
-queuebot:#ubuntu-release- Unapproved: lxcfs (zesty-proposed/main) [2.0.7-0ubuntu1~17.04.1 => 2.0.7-0ubuntu1~17.04.2] (edubuntu, ubuntu-server)18:31
slashdHi, Does someone with upload rights in devel release who has some cycle to sponsor a debdiff https://launchpadlibrarian.net/326769765/artful-ksh_93u+20120801-3.2.debdiff ? Once in Artful, I can sponsor the SRU myself.18:51
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-85.108]18:52
mitya57slashd, the correct version number would be 93u+20120801-3.1ubuntu118:56
mitya57Otherwise, will upload to artful now.18:56
slashdmitya57, much appreciated, you'll do the correction or want me to re-generate a new debdiff ?18:58
mitya57I will do.18:58
slashdmitya57, thanks much18:58
mitya57slashd, uploaded.19:00
slashdmitya57, thanks you very much19:00
slashdmitya57, you were right about the version, I think I misread when I saw, it I was under the impression it was ubuntu3.1, thanks for catching this19:01
slashdneed some glasses19:01
slangasekxnox: do you know why udev is failing to configure on armhf for autopkgtests? (e.g. http://autopkgtest.ubuntu.com/packages/l/lazarus/artful/armhf)20:16
infinityslangasek: Going to assume it's less to do with armhf and more to do with lxd.20:35
slangasekinfinity: s390x didn't show the problem, and this is certainly a regression in the behavior20:50
infinityslangasek: s390x is lxc, not lxd, just to be confusing.20:50
slangasekah right20:50
slangasekwell anyway. still a behavior regression :)20:50
infinityNot saying it's not a problem, just guessing it's not arch-specific.20:50
slangasekand nagios3 autopkgtest is failing cross-arch because Error: The new file apt.cfg does not exist!20:56
xnoxslangasek, hahahahah elipsised logs are useful - Jul 04 12:23:38 autopkgtest-lxd-qemhph systemd[1]: systemd-udevd.service: Fai…ed22:12
xnoxslangasek, also why is that calling invoke-rc.d on ubuntu?! initscript udev?!22:13
xnoxwtf.22:13
xnoxwhat is this?! 2004?22:13
xnoxslangasek, there is also an upgrade bug where open-vm-tools tries to call udevadm trigger or settle and that is not allowed whilst udev is upgrading. that is from trusty->xenial do-release-upgrade of EC2 instance.22:14
xnoxslangasek, do we do cloud lts-lts upgrade testing in all the clouds?22:14
slangasekxnox: invoke-rc.d is the policy interface and always has been22:24
slangaseklts-lts upgrade testing in "all the clouds" - I'm sure not22:24
xnoxsorry for rebooting my irc bouncer.22:25
=== enick_370 is now known as RAOF

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