[07:15] <acheronuk> xnox: daily isos fail with 'cpio: premature end of archive' again after the 'fix' in initramfs-tools 0.133ubuntu8
[07:52] -queuebot:#ubuntu-release- Unapproved: gcc-defaults-ports (cosmic-proposed/universe) [1.178ubuntu1.1 => 1.178ubuntu1.18.10.1] (no packageset) (sync)
[08:10] -queuebot:#ubuntu-release- Unapproved: accepted gcc-defaults-ports [sync] (cosmic-proposed) [1.178ubuntu1.18.10.1]
[08:22] <sil2100> cjwatson: 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 anymore
[08:28] <cjwatson> thanks
[08:37] <doko> cjwatson, sil2100: I think your upload won't help
[08:37] <doko> I'm trying to understand why this only shows up with gcc-defaults-ports, and not with the other cross packages
[08:37] <cjwatson> That upload does help
[08:38] <cjwatson> I mean, maybe not permanently, but its binary versioning scheme is such that it won't collide
[08:38] <doko> how? it
[08:38] <doko> hmm
[08:38] <cjwatson> Because it has .18.10.1 on the end
[08:38] <sil2100> I don't understand the build process, but I did try to make sure the ubuntu part of the version is non-collidable with bionic
[08:39] <doko> ahh, ok, such a version bump would not help for gcc-N-cross and gcc-N-cross-ports
[08:53] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1041.46]
[09:01] -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:02] -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:03] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.39.2]
[09:32] <LocutusOfBorg> what is preventing src:papi from being accepted? it is not built on s390x, but neither the previous version is...
[09:33] <cjwatson> nothing?
[09:33] <ginggs> @LocutusOfBorg new binaries
[09:34] -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] <ginggs> cjwatson: thanks :)
[09:34] <LocutusOfBorg> cjwatson, 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] <cjwatson> auto-accept is not a thing for NEW
[09:34] <LocutusOfBorg> thanks for accepting :D
[09:35] <LocutusOfBorg> oh, I remember you talking about some half made auto accept script, but I admit I lost the context probably
[09:35] <cjwatson> there is new-binary-debian-universe, but that's a helper that archive admins can run by hand
[09:35] <cjwatson> just saves a bit of time when processing the obvious bulk stuff in NEW
[09:36] <apw> the other auto accept bot is for unapproved late in the cycle
[09:36] <cjwatson> and it has no particular architecture checks
[09:36] <LocutusOfBorg> yeah probably that one, but does it work if some arch is not built yet?
[09:36] <cjwatson> it works fine, I just ran it
[09:37] <LocutusOfBorg> how does it work if some of the stuff in new is built on some arch and is not yet built on others?
[09:37] <cjwatson> it cares not
[09:37] <cjwatson> proposed-migration will sort that sort of thing out
[09:37] <LocutusOfBorg> sure thing :D thanks!
[09:38] <cjwatson> also, it prompts - if there's some kind of complicated layered rebuild in process then an archive admin can choose to wait
[09:38] <cjwatson> but it's up to the human in the loop
[09:41] <LocutusOfBorg> ack thanks
[10:44] -queuebot:#ubuntu-release- Unapproved: kazam (disco-proposed/universe) [1.4.5-2.1 => 1.4.5-2.1ubuntu0.1] (no packageset)
[11:38] -queuebot:#ubuntu-release- Unapproved: u-boot (disco-proposed/main) [2018.07~rc3+dfsg1-0ubuntu2 => 2018.07~rc3+dfsg1-0ubuntu3] (core)
[11:40] -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:41] -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:49] -queuebot:#ubuntu-release- Unapproved: u-boot (xenial-proposed/main) [2016.01+dfsg1-2ubuntu3 => 2016.01+dfsg1-2ubuntu4] (desktop-core, ubuntu-server)
[12:15] -queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (disco-proposed) [2018.07~rc3+dfsg1-0ubuntu3]
[12:24] -queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (cosmic-proposed) [2018.07~rc3+dfsg1-0ubuntu3~18.10.1]
[12:25] -queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (bionic-proposed) [2018.07~rc3+dfsg1-0ubuntu3~18.04.1]
[12:49] -queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (xenial-proposed) [2016.01+dfsg1-2ubuntu4]
[13:04] <ahasenack> hi 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] <ahasenack> hm, but why did it fail only on armhf, and not the other arches...
[13:04]  * ahasenack puzzled now
[13:05] <ahasenack> huh
[13:06] <ahasenack> armhf is on lxd, others are vms?
[13:06]  * ahasenack switches to #ubuntu-devel
[13:07] <LocutusOfBorg> ahasenack, hey!
[13:07] <LocutusOfBorg> I 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/201
[13: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 internally
[13:08] <ahasenack> LocutusOfBorg: oh, thx
[13:08] <ahasenack> LocutusOfBorg: but it worked in the other arches,
[13:08] <ahasenack> LocutusOfBorg: it looks like our armhf lxd just can't resolve squid.internal
[13:08] <ahasenack> the other arches can
[13:08] <ahasenack> https://pastebin.ubuntu.com/p/RVQFSwXS8F/ for a good run, same version
[13:09] <ahasenack> oh, you reported a build failure
[13:09] <ahasenack> something different
[13:24] <ahasenack> LocutusOfBorg: MP for the diaspora-installer armhf hint: https://code.launchpad.net/~ahasenack/britney/diaspora-installer-armhf-hint/+merge/368655
[13:26] <ahasenack> oh, hm, dns was just a temporary issue
[13:43] <xnox> acheronuk:  of course they are! because the fix needs to be on the nusakan.
[13:46] <acheronuk> xnox: 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 there
[13:51] <xnox> acheronuk:  it is a bit of a mess
[13:57] -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)
[14:40] -queuebot:#ubuntu-release- Unapproved: debian-installer (disco-proposed/main) [20101020ubuntu570 => 20101020ubuntu570.1] (core)
[15:31] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (disco-proposed/main) [0.131ubuntu19 => 0.131ubuntu19.1] (core)
[15:33] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (cosmic-proposed/main) [0.131ubuntu15.2 => 0.131ubuntu15.3] (core)
[15:39] <xnox> acheronuk:  we upgraded nusakan, so tomorrow's build should be fine.
[15:39] <xnox> acheronuk:  thank you for paying attention.
[15:39] <xnox> and thank you sil2100 for fixing everything.
[15:40] <acheronuk> xnox & sil2100: thank you!
[15:50] -queuebot:#ubuntu-release- Unapproved: debian-installer (bionic-proposed/main) [20101020ubuntu543.7 => 20101020ubuntu543.8] (core)
[16:40] <blackboxsw> bdmurray: 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/1831772
[16:40] <blackboxsw> if either of you get a chance to peek at it. that'd be excellent
[16:40] -queuebot:#ubuntu-release- Unapproved: keystone (cosmic-proposed/main) [2:14.0.1-0ubuntu3 => 2:14.1.0-0ubuntu1] (openstack, ubuntu-server)
[17:50] -queuebot:#ubuntu-release- Unapproved: debian-installer (cosmic-proposed/main) [20101020ubuntu557.1 => 20101020ubuntu557.2] (core)
[17:59] -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)
[18:53] <coreycb> hello, 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.
[19:48] -queuebot:#ubuntu-release- Unapproved: systemd (bionic-proposed/main) [237-3ubuntu10.22 => 237-3ubuntu10.23] (core)
[20:59] <vorlon> coreycb: done
[20:59] <coreycb> vorlon: thanks
[22:20] <xnox> vorlon:  https://code.launchpad.net/~ahasenack/britney/diaspora-installer-armhf-hint/+merge/368655