/srv/irclogs.ubuntu.com/2019/06/11/#ubuntu-release.txt

acheronukxnox: daily isos fail with 'cpio: premature end of archive' again after the 'fix' in initramfs-tools 0.133ubuntu807:15
-queuebot:#ubuntu-release- Unapproved: gcc-defaults-ports (cosmic-proposed/universe) [1.178ubuntu1.1 => 1.178ubuntu1.18.10.1] (no packageset) (sync)07:52
-queuebot:#ubuntu-release- Unapproved: accepted gcc-defaults-ports [sync] (cosmic-proposed) [1.178ubuntu1.18.10.1]08:10
sil2100cjwatson: hey! Thanks for pointing out and dealing with the gcc-defaults-ports binary issues, I just pushed a new version that hopefully shouldn't conflict anymore08:22
cjwatsonthanks08:28
dokocjwatson, sil2100: I think your upload won't help08:37
dokoI'm trying to understand why this only shows up with gcc-defaults-ports, and not with the other cross packages08:37
cjwatsonThat upload does help08:37
cjwatsonI mean, maybe not permanently, but its binary versioning scheme is such that it won't collide08:38
dokohow? it08:38
dokohmm08:38
cjwatsonBecause it has .18.10.1 on the end08:38
sil2100I don't understand the build process, but I did try to make sure the ubuntu part of the version is non-collidable with bionic08:38
dokoahh, ok, such a version bump would not help for gcc-N-cross and gcc-N-cross-ports08:39
-queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1041.46]08:53
-queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (disco-proposed) [2.39.2+19.04]09:01
-queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (cosmic-proposed) [2.39.2+18.10]09:01
-queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (bionic-proposed) [2.39.2+18.04]09:02
-queuebot:#ubuntu-release- Unapproved: rejected snapd [source] (xenial-proposed) [2.39.1]09:02
-queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.39.2]09:03
LocutusOfBorgwhat is preventing src:papi from being accepted? it is not built on s390x, but neither the previous version is...09:32
cjwatsonnothing?09:33
ginggs@LocutusOfBorg new binaries09:33
-queuebot:#ubuntu-release- New: accepted papi [amd64] (eoan-proposed) [5.7.0+dfsg-1]09:34
-queuebot:#ubuntu-release- New: accepted papi [armhf] (eoan-proposed) [5.7.0+dfsg-1]09:34
-queuebot:#ubuntu-release- New: accepted papi [ppc64el] (eoan-proposed) [5.7.0+dfsg-1]09:34
-queuebot:#ubuntu-release- New: accepted papi [arm64] (eoan-proposed) [5.7.0+dfsg-1]09:34
-queuebot:#ubuntu-release- New: accepted papi [i386] (eoan-proposed) [5.7.0+dfsg-1]09:34
ginggscjwatson: thanks :)09:34
LocutusOfBorgcjwatson, the question is: does the "auto accept tool" check if all archs are built, and becomes manual if some of them are missing, or does check if previous version were missing too?09:34
cjwatsonauto-accept is not a thing for NEW09:34
LocutusOfBorgthanks for accepting :D09:34
LocutusOfBorgoh, I remember you talking about some half made auto accept script, but I admit I lost the context probably09:35
cjwatsonthere is new-binary-debian-universe, but that's a helper that archive admins can run by hand09:35
cjwatsonjust saves a bit of time when processing the obvious bulk stuff in NEW09:35
apwthe other auto accept bot is for unapproved late in the cycle09:36
cjwatsonand it has no particular architecture checks09:36
LocutusOfBorgyeah probably that one, but does it work if some arch is not built yet?09:36
cjwatsonit works fine, I just ran it09:36
LocutusOfBorghow does it work if some of the stuff in new is built on some arch and is not yet built on others?09:37
cjwatsonit cares not09:37
cjwatsonproposed-migration will sort that sort of thing out09:37
LocutusOfBorgsure thing :D thanks!09:37
cjwatsonalso, it prompts - if there's some kind of complicated layered rebuild in process then an archive admin can choose to wait09:38
cjwatsonbut it's up to the human in the loop09:38
LocutusOfBorgack thanks09:41
-queuebot:#ubuntu-release- Unapproved: kazam (disco-proposed/universe) [1.4.5-2.1 => 1.4.5-2.1ubuntu0.1] (no packageset)10:44
-queuebot:#ubuntu-release- Unapproved: u-boot (disco-proposed/main) [2018.07~rc3+dfsg1-0ubuntu2 => 2018.07~rc3+dfsg1-0ubuntu3] (core)11:38
-queuebot:#ubuntu-release- Unapproved: u-boot (cosmic-proposed/main) [2018.07~rc3+dfsg1-0ubuntu2~18.10.1 => 2018.07~rc3+dfsg1-0ubuntu3~18.10.1] (core)11:40
-queuebot:#ubuntu-release- Unapproved: u-boot (bionic-proposed/main) [2018.07~rc3+dfsg1-0ubuntu2~18.04.1 => 2018.07~rc3+dfsg1-0ubuntu3~18.04.1] (core)11:41
-queuebot:#ubuntu-release- Unapproved: u-boot (xenial-proposed/main) [2016.01+dfsg1-2ubuntu3 => 2016.01+dfsg1-2ubuntu4] (desktop-core, ubuntu-server)11:49
-queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (disco-proposed) [2018.07~rc3+dfsg1-0ubuntu3]12:15
-queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (cosmic-proposed) [2018.07~rc3+dfsg1-0ubuntu3~18.10.1]12:24
-queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (bionic-proposed) [2018.07~rc3+dfsg1-0ubuntu3~18.04.1]12:25
-queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (xenial-proposed) [2016.01+dfsg1-2ubuntu4]12:49
ahasenackhi release team, diaspora-installer cannot be installed in the machines used for autopkgtests because its postinst actually downloads diaspora at install time: https://pastebin.ubuntu.com/p/N9MqVKvN4Q/13:04
ahasenackhm, but why did it fail only on armhf, and not the other arches...13:04
* ahasenack puzzled now13:04
ahasenackhuh13:05
ahasenackarmhf is on lxd, others are vms?13:06
* ahasenack switches to #ubuntu-devel13:06
LocutusOfBorgahasenack, hey!13:07
LocutusOfBorgI reported it already!13:07
LocutusOfBorg[16:32:41] <LocutusOfBorg> hello, can we please have diaspora-installer/0.7.6.1+debian1/armhf hinted? it is regressed in release (it is just a downloader), and I have reported it upstream https://github.com/codahale/bcrypt-ruby/issues/20113:07
LocutusOfBorg[16:33:05] <LocutusOfBorg> but not something we can easily fix in Ubuntu side, since gems are handled on rubygems.org website, not internally13:07
ahasenackLocutusOfBorg: oh, thx13:08
ahasenackLocutusOfBorg: but it worked in the other arches,13:08
ahasenackLocutusOfBorg: it looks like our armhf lxd just can't resolve squid.internal13:08
ahasenackthe other arches can13:08
ahasenackhttps://pastebin.ubuntu.com/p/RVQFSwXS8F/ for a good run, same version13:08
ahasenackoh, you reported a build failure13:09
ahasenacksomething different13:09
ahasenackLocutusOfBorg: MP for the diaspora-installer armhf hint: https://code.launchpad.net/~ahasenack/britney/diaspora-installer-armhf-hint/+merge/36865513:24
ahasenackoh, hm, dns was just a temporary issue13:26
xnoxacheronuk:  of course they are! because the fix needs to be on the nusakan.13:43
acheronukxnox: makes sense. I'm not really too familiar with what gets pulled in on the fly in each build on that, and what needs to be already there13:46
xnoxacheronuk:  it is a bit of a mess13:51
-queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (bionic-proposed/partner) [1:20190514.1-0ubuntu0.18.04.1 => 1:20190611.1-0ubuntu0.18.04.1] (no packageset)13:57
-queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (disco-proposed/partner) [1:20190514.1-0ubuntu0.19.04.1 => 1:20190611.1-0ubuntu0.19.04.1] (no packageset)13:57
-queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (cosmic-proposed/partner) [1:20190514.1-0ubuntu0.18.10.1 => 1:20190611.1-0ubuntu0.18.10.1] (no packageset)13:57
-queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (xenial-proposed/partner) [1:20190514.1-0ubuntu0.16.04.1 => 1:20190611.1-0ubuntu0.16.04.1] (no packageset)13:57
=== cpaelzer__ is now known as cpaelzer
-queuebot:#ubuntu-release- Unapproved: debian-installer (disco-proposed/main) [20101020ubuntu570 => 20101020ubuntu570.1] (core)14:40
-queuebot:#ubuntu-release- Unapproved: initramfs-tools (disco-proposed/main) [0.131ubuntu19 => 0.131ubuntu19.1] (core)15:31
-queuebot:#ubuntu-release- Unapproved: initramfs-tools (cosmic-proposed/main) [0.131ubuntu15.2 => 0.131ubuntu15.3] (core)15:33
xnoxacheronuk:  we upgraded nusakan, so tomorrow's build should be fine.15:39
xnoxacheronuk:  thank you for paying attention.15:39
xnoxand thank you sil2100 for fixing everything.15:39
acheronukxnox & sil2100: thank you!15:40
-queuebot:#ubuntu-release- Unapproved: debian-installer (bionic-proposed/main) [20101020ubuntu543.7 => 20101020ubuntu543.8] (core)15:50
blackboxswbdmurray: or RAOF  if there is availability today, there is a curtin SRU queued in unapproved for xenial, bionic, cosmic and disco https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/183177216:40
ubot5Launchpad bug 1831772 in curtin (Ubuntu Disco) "sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1" [Undecided,New]16:40
blackboxswif either of you get a chance to peek at it. that'd be excellent16:40
-queuebot:#ubuntu-release- Unapproved: keystone (cosmic-proposed/main) [2:14.0.1-0ubuntu3 => 2:14.1.0-0ubuntu1] (openstack, ubuntu-server)16:40
-queuebot:#ubuntu-release- Unapproved: debian-installer (cosmic-proposed/main) [20101020ubuntu557.1 => 20101020ubuntu557.2] (core)17:50
-queuebot:#ubuntu-release- Unapproved: bash (bionic-proposed/main) [4.4.18-2ubuntu1.1 => 4.4.18-2ubuntu1.2~bionic1] (core)17:59
-queuebot:#ubuntu-release- Unapproved: bash (cosmic-proposed/main) [4.4.18-2ubuntu3 => 4.4.18-2ubuntu3.1~cosmic1] (core)17:59
coreycbhello, can an archive admin please remove python-oslo.log 3.44.0-0ubuntu2 from eoan-proposed? we have some circulary dependency issues and this is the easiest resolution.18:53
-queuebot:#ubuntu-release- Unapproved: systemd (bionic-proposed/main) [237-3ubuntu10.22 => 237-3ubuntu10.23] (core)19:48
=== katamo- is now known as katamo
vorloncoreycb: done20:59
coreycbvorlon: thanks20:59
xnoxvorlon:  https://code.launchpad.net/~ahasenack/britney/diaspora-installer-armhf-hint/+merge/36865522:20

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