[07:00] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (bionic-proposed/main) [5.0.0-21.22~18.04.1] (kernel)
[07:00] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (bionic-proposed/main) [5.0.0-21.22~18.04.1] (kernel)
[07:01] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [arm64] (bionic-proposed/main) [5.0.0-21.22~18.04.1] (kernel)
[07:04] <LocutusOfBorg> hello, is autosync having a sad day?
[07:16] <Ukikie> I believe that debian-archive-keyring needed an update.
[07:57] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (bionic-proposed) [5.0.0-21.22~18.04.1]
[07:57] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (bionic-proposed) [5.0.0-21.22~18.04.1]
[07:57] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [arm64] (bionic-proposed) [5.0.0-21.22~18.04.1]
[08:26] <LocutusOfBorg> general question: docker.io i386 test started failing because of "lxc launch ubuntu-daily:eoan/i386 docker -c security.nesting=true"
[08:26] <LocutusOfBorg> is that normal? maybe daily i386 builds are not ship anymore? so can we skip such test?
[08:28] <Laney> LocutusOfBorg: Talk to stgrabe_r or the LXD team, and find out. If it's dropped, stop running that test on i386 IMHO.
[08:33] <LocutusOfBorg> I think mapreri rbalint or amurray might want to ask ^^ (you all have some packages that are failing that test in -proposed) :)
[08:34]  * Laney sees the work slide off LocutusOfBorg's shoulders
[08:36] <LocutusOfBorg> meh, I'm getting usually blamed for trying to fix other people's uploads :) but I pinged him on -devel, my question here in -release channel wanted to be more general, such as "will we badtest all i386 in the next days, or something similar?"
[08:41] <Laney> I dunno what the i386 plan is with respect to autopkgtest actually
[08:41] <Laney> nobody's talked to me about it
[08:42] <Laney> so carry on for now
[08:42] <LocutusOfBorg> maybe this is not an issue, not sure... we might have a bunch of stuff migrating if we badtest i386
[08:45] <sil2100> Laney: hey! This might be nothing, but I noticed that the pending-sru report hasn't been updated since Saturday - could you log into snakefruit for me and check if all is good with sru-report there?
[08:45] <Laney> sil2100: ok, but I don't know where that's logged
[08:46] <sil2100> Laney: I guess it should be ran via cron? I don't know if the output is logged anywhere, hmm
[08:46] <sil2100> Laney: since sru-report usually just outputs the html webpage to stdout
[08:46] <Laney> we get cron spam in the mailbox
[08:46] <Laney> let me see
[08:46] <Laney> if not I can just run it I guess
[08:47] <cjwatson> LocutusOfBorg,Ukikie: yes, this is on my list to sort out today
[08:47] <cjwatson> (autosync)
[08:48] <cjwatson> Laney: it wouldn't be surprising if some stuff on snakefruit hung during Friday's network outage
[08:48] <cjwatson> check start times and kill them if they're ancient
[08:48] <Laney> I think there's a stuck process
[08:48]  * Laney nods cjwatson 
[08:48] <Laney> we had that with proposed-migration too
[08:49] <sil2100> Laney, cjwatson: thanks guys o/
[08:49] <sil2100> Since sru-report ran fine when I was running it locally
[08:50] <Ukikie> cjwatson: That's what your remarks in -devel seemed to indicate, thanks btw. :)
[08:55] <Laney> sil2100: Let's see if it works in 15 minutes
[10:18] <sil2100> Laney: it works o/
[11:42] <doko> finally, gcc-8 doesn't try to promote again \o/
[13:02] <stgraber> Laney, LocutusOfBorg: if it's using ubuntu-daily, then those are the official cloud images, not the images that the LXD team generates, so not much I can do about those
[13:02] <stgraber> for the ones that we generate ourselves, we do have i386 for eoan still (images:ubuntu/eoan/i386)
[13:27] <Laney> ah right
[13:34] <Laney> of course I can't generate an i386 autopkgtest image myself now for the same reason
[13:35] <Laney> so like should we turn off i386 testing for eoan?
[13:53] <Laney> this does feel a bit cart before horse though
[13:55] -queuebot:#ubuntu-release- Unapproved: lazr.restfulclient (xenial-proposed/main) [0.13.4-5ubuntu1 => 0.13.4-5ubuntu2] (core)
[14:12] -queuebot:#ubuntu-release- Unapproved: accepted lazr.restfulclient [source] (xenial-proposed) [0.13.4-5ubuntu2]
[14:54] -queuebot:#ubuntu-release- Unapproved: accepted libfm-qt [source] (disco-proposed) [0.14.1-0ubuntu2.1]
[15:24] -queuebot:#ubuntu-release- New source: openjdk-14 (eoan-proposed/primary) [14~4-0ubuntu1]
[15:25] -queuebot:#ubuntu-release- New: accepted openjdk-14 [source] (eoan-proposed) [14~4-0ubuntu1]
[15:36] -queuebot:#ubuntu-release- Unapproved: cinder (bionic-proposed/main) [2:12.0.7-0ubuntu1 => 2:12.0.7-0ubuntu2] (openstack, ubuntu-server)
[15:43] -queuebot:#ubuntu-release- Unapproved: accepted aptdaemon [source] (xenial-proposed) [1.1.1+bzr982-0ubuntu14.1]
[16:14] <vorlon> Laney: based on conversations w/ LP team, I expect we will want to use an amd64 image with i386 binaries installed via multiarch for testing; this of course isn't viable for all the packages that exist today and want testing
[16:44] <Laney> vorlon: Something like that sounds good, if that is how we're to be using i386, yes. That'd require work to make possible, of course. I'm still worried that stopping image production before we've really got going on any of the work for this was premature...
[17:23] <cjwatson> I thought I remembered us saying in London that the autopkgtest work needed to be done before the images were dropped
[17:24] <cjwatson> ICBW but it would seem like the sort of thing I'd say :)
[17:28] -queuebot:#ubuntu-release- New binary: openjdk-14 [s390x] (eoan-proposed/universe) [14~4-0ubuntu1] (no packageset)
[17:31] -queuebot:#ubuntu-release- New binary: openjdk-14 [armhf] (eoan-proposed/universe) [14~4-0ubuntu1] (no packageset)
[17:53] <vorlon> Laney: certainly; in practice the images were dropped per the original plan, before we changed course
[18:10] -queuebot:#ubuntu-release- New binary: openjdk-14 [i386] (eoan-proposed/universe) [14~4-0ubuntu1] (no packageset)
[18:40] -queuebot:#ubuntu-release- New: accepted openjdk-14 [armhf] (eoan-proposed) [14~4-0ubuntu1]
[18:40] -queuebot:#ubuntu-release- New: accepted openjdk-14 [s390x] (eoan-proposed) [14~4-0ubuntu1]
[18:40] -queuebot:#ubuntu-release- New: accepted openjdk-14 [i386] (eoan-proposed) [14~4-0ubuntu1]
[18:42] -queuebot:#ubuntu-release- Unapproved: base-files (disco-proposed/main) [10.1ubuntu9 => 10.1ubuntu9.1] (core)
[18:42] -queuebot:#ubuntu-release- Unapproved: base-files (cosmic-proposed/main) [10.1ubuntu7 => 10.1ubuntu7.1] (core)
[18:45] -queuebot:#ubuntu-release- Unapproved: base-files (bionic-proposed/main) [10.1ubuntu2.4 => 10.1ubuntu2.5] (core)
[18:53] -queuebot:#ubuntu-release- Unapproved: designate (bionic-proposed/main) [1:6.0.1-0ubuntu1 => 1:6.0.1-0ubuntu1.1] (openstack, ubuntu-server)
[18:57] -queuebot:#ubuntu-release- New binary: openjdk-14 [amd64] (eoan-proposed/universe) [14~4-0ubuntu1] (no packageset)
[19:22] <Laney> vorlon: ok, cool, so is there a chance they can be put back on then?
[19:22] <Laney> (afk now; attempting a crossgrade - if you never see me again it was nice to work with you all)
[19:23] <vorlon> Laney: in principle, though rcj might shoot me
[19:34] -queuebot:#ubuntu-release- Unapproved: base-files (xenial-proposed/main) [9.4ubuntu4.8 => 9.4ubuntu4.9] (core)
[19:36] -queuebot:#ubuntu-release- Unapproved: edk2 (cosmic-proposed/universe) [0~20180803.dd4cae4d-1ubuntu1 => 0~20180803.dd4cae4d-1ubuntu1.1] (no packageset)
[19:37] -queuebot:#ubuntu-release- New: accepted openjdk-14 [amd64] (eoan-proposed) [14~4-0ubuntu1]
[19:38] -queuebot:#ubuntu-release- Unapproved: rejected base-files [source] (xenial-proposed) [9.4ubuntu4.9]
[19:45] -queuebot:#ubuntu-release- Unapproved: edk2 (bionic-proposed/universe) [0~20180205.c0d9813c-2 => 0~20180205.c0d9813c-2ubuntu0.1] (no packageset)
[20:02] <infinity> vorlon: Being shot is a small price to pay.
[21:17] -queuebot:#ubuntu-release- Unapproved: nova (disco-proposed/main) [2:19.0.1-0ubuntu1 => 2:19.0.1-0ubuntu2] (openstack, ubuntu-server)
[21:42] <vorlon> ok so what's going on with ppc64el auotpkgtests?
[21:52] <vorlon> Laney: I see that there are no bos01 runner units on the master, but I see no commits related to this in autopkgtest-cloud, no local changes to the checkout, and no discussion of this in scrollback
[21:52] <vorlon> juliank: ^^ do you know anything?
[21:55] <Laney> vorlon: bos01 is busted, see cRT #119339
[21:55] <Laney> sorry if I forgot to document it
[21:55] <vorlon> ok
[21:55] <Laney> I was going to go to IS office hours tomorrow and ask for it to be worked on
[21:56] <Laney> but feel free to give it a 999999999999 or whatever
[21:57] <vorlon> well, it seems I can only set a deadline on that queue :P
[21:57] <vorlon> which is not the most helpful
[22:01] <Eickmeyer> bdmurray: I further updated the test case on bug 183370 per sil2100's request. I have further updated the test case since you seem to be confused (or have confused me), so I hope it's crystal clear now.
[22:01] <Eickmeyer> er... bug 1833740
[22:01] <Eickmeyer> bdmurray: ^
[22:01]  * Eickmeyer accidentally a number
[22:05] <bdmurray> Eickmeyer: I'm not confused about the test case I'm curious what you did to verify that the bug is fixed which lead you to tagging it verification-done-disco.
[22:05] <Eickmeyer> bdmurray: I did exactly what I just commented.
[22:06] <bdmurray> Eickmeyer: Generally I expect to see something like "I installed ubuntustudio-installer version 1.2.3 from -proposed and I saw that ubuntustudio-gnome-branding was no longer an option".
[22:07] <Eickmeyer> bdmurray: ack, do you need that exact comment?
[22:08] <bdmurray> No, this conversation will do for me but do you under the distinction between the test case and the verification process?
[22:11] <Eickmeyer> bdmurray: I do understand. Comment #5 was in reference to comment #3.
[22:59] -queuebot:#ubuntu-release- Unapproved: accepted mu-editor [source] (disco-proposed) [1.0.2+dfsg-2ubuntu0.1]
[23:05] -queuebot:#ubuntu-release- Unapproved: accepted pulseaudio [source] (disco-proposed) [1:12.2-2ubuntu3.1]