[05:53] -queuebot:#ubuntu-release- Unapproved: cockpit (disco-backports/universe) [194-1~ubuntu19.04.1 => 195-1~ubuntu19.04.1] (no packageset)
[06:06] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (disco-backports) [195-1~ubuntu19.04.1]
[06:07] -queuebot:#ubuntu-release- Unapproved: cockpit (bionic-backports/universe) [194-1~ubuntu18.04.1 => 195-1~ubuntu18.04.1] (no packageset)
[06:07] -queuebot:#ubuntu-release- Unapproved: cockpit (cosmic-backports/universe) [194-1~ubuntu18.10.1 => 195-1~ubuntu18.10.1] (no packageset)
[06:07] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (bionic-backports) [195-1~ubuntu18.04.1]
[06:07] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (cosmic-backports) [195-1~ubuntu18.10.1]
[08:09] -queuebot:#ubuntu-release- Unapproved: accepted xorg-server [source] (bionic-proposed) [2:1.19.6-1ubuntu4.3]
[08:41] -queuebot:#ubuntu-release- Unapproved: libreoffice (bionic-proposed/main) [1:6.0.7-0ubuntu0.18.04.6 => 1:6.0.7-0ubuntu0.18.04.7] (kubuntu, ubuntu-desktop)
[08:43] -queuebot:#ubuntu-release- Unapproved: libreoffice-l10n (bionic-proposed/main) [1:6.0.7-0ubuntu0.18.04.4 => 1:6.0.7-0ubuntu0.18.04.7] (ubuntu-desktop)
[08:48] <Laney> sil2100: (just flipped gnome-shell back to v-done now you've released yaru [thanks for that])
[08:49] <sil2100> Laney: ACK o/
[08:49]  * sil2100 looks at gnome-shell and mutter then
[08:49] <Laney> 😘
[08:52] -queuebot:#ubuntu-release- Unapproved: libreoffice (cosmic-proposed/main) [1:6.1.6-0ubuntu0.18.10.2 => 1:6.1.6-0ubuntu0.18.10.3] (kubuntu, ubuntu-desktop)
[08:53] -queuebot:#ubuntu-release- Unapproved: libreoffice-l10n (cosmic-proposed/main) [1:6.1.6-0ubuntu0.18.10.2 => 1:6.1.6-0ubuntu0.18.10.3] (ubuntu-desktop)
[10:18] -queuebot:#ubuntu-release- New source: indicator-notifications (eoan-proposed/primary) [0.3.3-0ubuntu1]
[10:19] -queuebot:#ubuntu-release- New: rejected indicator-notifications [source] (eoan-proposed) [0.3.3-0ubuntu1]
[10:19] -queuebot:#ubuntu-release- New: accepted indicator-notifications [source] (eoan-proposed) [0.3.3-0ubuntu1]
[10:21] -queuebot:#ubuntu-release- New binary: indicator-notifications [amd64] (eoan-proposed/none) [0.3.3-0ubuntu1] (no packageset)
[10:21] -queuebot:#ubuntu-release- New binary: indicator-notifications [ppc64el] (eoan-proposed/none) [0.3.3-0ubuntu1] (no packageset)
[10:21] -queuebot:#ubuntu-release- New binary: indicator-notifications [i386] (eoan-proposed/none) [0.3.3-0ubuntu1] (no packageset)
[10:21] -queuebot:#ubuntu-release- New binary: indicator-notifications [s390x] (eoan-proposed/none) [0.3.3-0ubuntu1] (no packageset)
[10:22] -queuebot:#ubuntu-release- New binary: indicator-notifications [arm64] (eoan-proposed/none) [0.3.3-0ubuntu1] (no packageset)
[10:22] -queuebot:#ubuntu-release- New binary: indicator-notifications [armhf] (eoan-proposed/none) [0.3.3-0ubuntu1] (no packageset)
[11:08] -queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (xenial-proposed/universe) [20190521-0ubuntu1~16.04.0 => 20190522-0ubuntu1~16.04.0] (ubuntu-cloud)
[11:08] -queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (bionic-proposed/universe) [20190521-0ubuntu1~18.04.0 => 20190522-0ubuntu1~18.04.0] (ubuntu-cloud)
[11:08] -queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (disco-proposed/main) [20190521-0ubuntu1~19.04.0 => 20190522-0ubuntu1~19.04.0] (core, ubuntu-cloud)
[11:09] -queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (cosmic-proposed/main) [20190521-0ubuntu1~18.10.0 => 20190522-0ubuntu1~18.10.0] (ubuntu-cloud)
[11:12] <rbalint> sil2100, ^ please accept the gce-compute-image-packages when you have time
[11:27] -queuebot:#ubuntu-release- Unapproved: libgeo-coder-googlev3-perl (bionic-proposed/universe) [0.16-1 => 0.16-1ubuntu0.1] (no packageset)
[11:51] -queuebot:#ubuntu-release- Unapproved: qemu (disco-proposed/main) [1:3.1+dfsg-2ubuntu3.1 => 1:3.1+dfsg-2ubuntu3.2] (ubuntu-server, virt)
[11:52] -queuebot:#ubuntu-release- Unapproved: qemu (bionic-proposed/main) [1:2.11+dfsg-1ubuntu7.14 => 1:2.11+dfsg-1ubuntu7.15] (ubuntu-server, virt)
[11:53] -queuebot:#ubuntu-release- Unapproved: qemu (cosmic-proposed/main) [1:2.12+dfsg-3ubuntu8.8 => 1:2.12+dfsg-3ubuntu8.9] (ubuntu-server, virt)
[11:55] -queuebot:#ubuntu-release- Unapproved: libvirt (xenial-proposed/main) [1.3.1-1ubuntu10.26 => 1.3.1-1ubuntu10.27] (ubuntu-server, virt)
[11:57] -queuebot:#ubuntu-release- Unapproved: libvirt (bionic-proposed/main) [4.0.0-1ubuntu8.10 => 4.0.0-1ubuntu8.11] (ubuntu-server, virt)
[11:58] -queuebot:#ubuntu-release- Unapproved: libvirt (cosmic-proposed/main) [4.6.0-2ubuntu3.5 => 4.6.0-2ubuntu3.6] (ubuntu-server, virt)
[12:04] <cpaelzer> hi, things are mostly good, but I have to ask to cancel the just appeared libvirt (xenial-proposed/main) [1.3.1-1ubuntu10.26 => 1.3.1-1ubuntu10.27]
[12:04] <cpaelzer> sil2100: rbasak: could one of you do that?
[12:04] <cpaelzer> the others are good but for just this particular one I need another round of test/dev/verify to be sure the upload does the right thing
[12:51] <cpaelzer> I'd want to repeat my request for someone to please cancel  libvirt xenial-proposed 1.3.1-1ubuntu10.27 from -unapproved
[12:56] <sil2100> cpaelzer: you mean, reject it?
[12:56] <sil2100> On it o/
[12:58] -queuebot:#ubuntu-release- Unapproved: rejected libvirt [source] (xenial-proposed) [1.3.1-1ubuntu10.27]
[13:00] -queuebot:#ubuntu-release- New: accepted indicator-notifications [amd64] (eoan-proposed) [0.3.3-0ubuntu1]
[13:00] -queuebot:#ubuntu-release- New: accepted indicator-notifications [armhf] (eoan-proposed) [0.3.3-0ubuntu1]
[13:00] -queuebot:#ubuntu-release- New: accepted indicator-notifications [ppc64el] (eoan-proposed) [0.3.3-0ubuntu1]
[13:00] -queuebot:#ubuntu-release- New: accepted indicator-notifications [arm64] (eoan-proposed) [0.3.3-0ubuntu1]
[13:00] -queuebot:#ubuntu-release- New: accepted indicator-notifications [s390x] (eoan-proposed) [0.3.3-0ubuntu1]
[13:01] -queuebot:#ubuntu-release- New: accepted indicator-notifications [i386] (eoan-proposed) [0.3.3-0ubuntu1]
[13:25] <cpaelzer> thank you sil2100
[14:06] <sil2100> huh, is qa.ubuntuwire.org down?
[14:30] <Laney> looks like it
[14:31] -queuebot:#ubuntu-release- Unapproved: apport (xenial-proposed/main) [2.20.1-0ubuntu2.18 => 2.20.1-0ubuntu2.19] (core)
[14:40] <mparillo> It finally came up for me. I wonder if the google problems are affecting many seemingly-unrelated sites
[14:54] <jamespage> afternoon
[14:54] <jamespage> pls can the neutron upload in bionic proposed be rejected; need to include a cherry pick for a functional regression
[15:24] <xnox> vorlon:  would you please look at https://bugs.launchpad.net/ubuntu/bionic/+source/libgeo-coder-googlev3-perl/+bug/1831443 ? is that an ok way to request hints? or review/accept the sru that effectively skips the offending online tests.
[15:28]  * Laney is making progress on a juju-2-ified autopkgtest-cloud
[15:32] -queuebot:#ubuntu-release- Unapproved: accepted glusterfs [source] (bionic-proposed) [3.13.2-1ubuntu1]
[15:35] <slashd> sil2100, thanks for glusterfs approval ^
[15:37] <sil2100> o/
[15:56] -queuebot:#ubuntu-release- Unapproved: accepted cups [source] (disco-proposed) [2.2.10-4ubuntu2]
[16:06] -queuebot:#ubuntu-release- Unapproved: accepted cups [source] (cosmic-proposed) [2.2.8-5ubuntu1.4]
[16:11] -queuebot:#ubuntu-release- Unapproved: accepted cups [source] (bionic-proposed) [2.2.7-1ubuntu2.6]
[16:12] -queuebot:#ubuntu-release- Unapproved: accepted cups [source] (xenial-proposed) [2.1.3-4ubuntu0.9]
[16:15] <ddstreet> sil2100 i see you retried the corosync failure in disco - it looks like that's failing because it can't find/download the corosync src in disco?  Could that be because there is only a corosync pkg in disco-release, and the corosync pkgs in disco-proposed were superceded and then the last one deleted when it was moved to eoan?
[16:22] -queuebot:#ubuntu-release- New: accepted ubuntustudio-look [amd64] (eoan-proposed) [0.61]
[16:27] <teward> sil2100: thanks for ^ that I'm sure Eickmeyer is very happy that was binNEW ACCEPTED
[16:27] <teward> :)
[16:27] <Eickmeyer> YEP!
[16:27] <Eickmeyer> \o/
[16:27] <teward> (assuming that was you sil2100 since I poked earlier xD)
[16:29] <sil2100> yw!
[16:31] <sil2100> ddstreet: I remember retrying it once because I was a bit surprised with the 'unknown' field, in the end I didn't find the time to track down the actual reason
[16:46] <ddstreet> sil2100 yeah adt couldn't find a src for it to download, so it didn't know what version it was trying to test
[16:47] <ddstreet> i'll try to repro locally, i think it's because there are corosync packages in disco-proposed that were superceded and the last disco-proposed version was deleted when it moved into eoan
[16:47] <ddstreet> but not really sure
[16:49] <sil2100> Eickmeyer: I'm reviewing your lsp-plugins upload right now - is there any NEW-package bug for that where I could leave feedback?
[16:49] <Eickmeyer> sil2100: Yes, hang on...
[16:49] <sil2100> ddstreet: hm, might be possible, didn't see that happening before though
[16:50] <Eickmeyer> sil2100: bug 1827288
[16:51] <teward> sil2100: correct me if i'm wrong but that should also be filed against bare Ubuntu too right?
[16:52] <sil2100> teward: probably, but I don't think that's a strict requirement
[16:52] <teward> just thought i'd ask :p
[16:52] <sil2100> What I do like is when the NEW package bug is attached to the changelog, if possible
[16:52] <sil2100> ;)
[16:53] <teward> :P
[16:53] <teward> true statement i see that's missing here
[16:59] <Eickmeyer> sil2100, teward: Just filed it against bare Ubuntu.
[17:01] <Eickmeyer> I can fix that changelog too, sil2100. Do we want to do a re-upload once I do?
[17:01]  * Eickmeyer can't upload that one
[17:04] <sil2100> Eickmeyer: I left some comments on the bug
[17:04] <Eickmeyer> Ok
[17:04] <sil2100> Eickmeyer: I need to EOD soon, but let's touch base tomorrow
[17:04] <Eickmeyer> sil2100: Works for me.
[17:05] <sil2100> Eickmeyer: take a look at those and respond on the bug, and then I can re-upload + approve it tomorrow if needed ;)
[17:05] <Eickmeyer> sil2100: Sounds good. :)
[17:05] <sil2100> Eickmeyer: ...but in case I forget myself, please do poke me about it
[17:05] <sil2100> o/
[17:06] <Eickmeyer> sil2100: Will do. Have a good one!
[17:06] <teward> sil2100: thanks for looking at them anyways
[17:06] <teward> enjoy your night :)
[17:06] <sil2100> Thanks!
[17:12] -queuebot:#ubuntu-release- New binary: swaybg [amd64] (eoan-proposed/none) [1.0-1] (no packageset)
[17:12] -queuebot:#ubuntu-release- New binary: swaybg [i386] (eoan-proposed/none) [1.0-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: swaybg [ppc64el] (eoan-proposed/none) [1.0-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: swaybg [s390x] (eoan-proposed/none) [1.0-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: swaybg [arm64] (eoan-proposed/none) [1.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: swaybg [armhf] (eoan-proposed/none) [1.0-1] (no packageset)
[17:30] <rbalint> infinity, please accept the gce-compute-image-packages srus if you have time today
[17:32] <vorlon> xnox: I'd still really prefer MPs instead of bugs, but yeah that looks fine, I'll land the hint (for bionic only; http://autopkgtest.ubuntu.com/packages/libg/libgeo-coder-googlev3-perl shows no tests for xenial).  also do you know about retry-autopkgtest-regressions --no-proposed?
[17:32] <infinity> rbalint: I'll have a look later today.
[17:36] -queuebot:#ubuntu-release- Unapproved: rejected libgeo-coder-googlev3-perl [source] (bionic-proposed) [0.16-1ubuntu0.1]
[17:36] <vorlon> xnox: please also transfer https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/52 into the sru bug description (i.e. fix up 'regression potential')
[19:08] <Eickmeyer> vorlon: Regarding lsp-plugins, the upstream developer made a few fixes. Do you think this would fix the test issue? https://github.com/sadko4u/lsp-plugins/issues/50
[19:08] <gitbot> sadko4u issue 50 in lsp-plugins "Tests fail on debian/ubuntu build " [Hotfix, Feature Request, Open]
[19:16] <vorlon> Eickmeyer: try it and see? :)
[19:17] <Eickmeyer> vorlon: Ok
[19:19] <ddstreet> xnox looks like you got corosync-qdevice version 3 into disco-release, but it seems corosync itself version 3 didn't make it into disco-release...you or vorlon want to comment on lp #1831492, as i'm not sure how to fix that mismatch
[19:20] <ddstreet> besides the obvious 'release corosync version 3 to match, into disco-updates'
[19:51] -queuebot:#ubuntu-release- Unapproved: dahdi-linux (bionic-proposed/universe) [1:2.11.1~dfsg-1ubuntu4 => 1:2.11.1~dfsg-1ubuntu4.1] (no packageset)
[19:56] -queuebot:#ubuntu-release- Unapproved: sysdig (bionic-proposed/universe) [0.19.1-1ubuntu1 => 0.19.1-1ubuntu1.1] (no packageset)
[20:18] <Eickmeyer> vorlon: We have a successful build including tests. \o/
[20:24] <vorlon> ddstreet: so I appreciate that corosync is not in particularly good shape in disco (cf LP: #1826045), but I'm not sure why we should care about this for a non-LTS release; if what you're after is getting systemd through, we should demonstrate that this test is broken in the release pocket, update the hints to reflect that, and move on
[20:25] <vorlon> Eickmeyer: the "build twice, test this one, ship that one" you commented in the bug, or something better?
[20:26] <Eickmeyer> vorlon: no, the upstream developer fixed the test suite, I added patches. Builds with test, no errors.
[20:26] <vorlon> ah nice
[20:29] <Eickmeyer> vorlon: I removed your comments (and the override_dh_auto_test:) line from debian/rules since it's no longer necessary.
[20:44] -queuebot:#ubuntu-release- New binary: u-boot [arm64] (eoan-proposed/main) [2019.04+dfsg-2ubuntu1] (core)
[20:55] <ddstreet> vorlon we shouldn't care about corosync, pacemaker, pcs in disco?  i mean this isn't just autopkgtest failures, this is actual problems with the packages...if the opinion is we don't care about the packages in disco, then why not just upgrade both pacemaker and corosync to the next major version, which will fix both problems?
[21:01] <vorlon> ddstreet: because that's more work than doing nothing
[21:01] <vorlon> so why is it worth doing more work?
[21:02] <ddstreet> er, because it's broken?
[21:02] <vorlon> and nothing in that autopkgtest log reads to me as saying anything about the state of the corosync package
[21:02] <ddstreet> well i explained it in the lp bug
[21:03] <ddstreet> corosync-qdevice was split out from corosync at version 3
[21:03] <ddstreet> so it will now be actually literally impossible to release any more version <3 corosync builds for disco
[21:03] <vorlon> ok but what does that have to do with 'apt-source corosync' apparently failing in the autopkgtest log?
[21:04] <ddstreet> did you read my bug?  it explains it in detail
[21:04] <vorlon> your bug does not explain the answer to the question I just asked
[21:04] <ddstreet> about what is has to do with 'apt-source corosync' in the adt log?
[21:04] <vorlon> "because the testbed can't find the corosync source" the corosync source hasn't gone anywhere
[21:05] <ddstreet> there is no corosync source for the corosync-qdevice version
[21:05] <ddstreet> vorlon if you read the 'other info' section i think it explains it
[21:05] <ddstreet> if you still aren't clear, please let me know
[21:06] <vorlon> ok
[21:07] <vorlon> so, that still doesn't say to me that the corosync package is broken
[21:08] <vorlon> it says that the package can't be SRUed without also dropping those binaries from the source
[21:08] <ddstreet> well, anyone installing corosync-qdevice and/or corosync-qnetd will get the wrong (version 3) binaryies
[21:08] <ddstreet> i don't know if you consider that broken or not, but it's certainly not right in my book
[21:09] <ddstreet> anyway, i'm about eod, if you have more thoughts on it or want to just hint britney and wontfix the bug, feel free
[21:10] <vorlon> it also looks to me like runner/autopkgtest is not buggy in the way you describe, but instead does a bidirectional check so it is only comparing versions of binary packages that list this source package as their source
[21:11] <ddstreet> vorlon it's not buggy, i don't say that adt is buggy anywhere
[21:11] <ddstreet> it's doing exactly what it should be
[21:11] <ddstreet> the problem is corosync-qdevice at v3 along with corosync at v2, both existing together
[21:12] <ddstreet> anywho, add q to the bug if you still don't understand - i'm eod
[21:12] <vorlon> if it's doing what you say, that's certainly not what it's supposed to be doing
[21:13] <ddstreet> vorlon i think you still don't understand what the problem is, because adt is doing things right
[21:13] -queuebot:#ubuntu-release- Unapproved: mesa (bionic-proposed/main) [19.0.2-1ubuntu1~18.04.1 => 19.0.2-1ubuntu1.1~18.04.1] (core, xorg)
[21:13] -queuebot:#ubuntu-release- Unapproved: mesa (disco-proposed/main) [19.0.2-1ubuntu1 => 19.0.2-1ubuntu1.1] (core, xorg)
[21:14] <vorlon> ddstreet: there's nothing right about mapping source to binaries to source and coming up with a source package version number for a different package
[21:14] <vorlon> and there is code in here to /guard against that case/
[21:15] <ddstreet> well, it found this problem, didn't it ;-)
[21:40] <vorlon> ddstreet: runner/autopkgtest, line 469, is intended to filter out binaries that are listed in this source package but whose current source is not this source package.  It fails because it's using \b to bound the package name and that matches the boundary between c and - in 'corosync-qdevice'.
[21:44] <vorlon> ddstreet: correction, it doesn't fail because the bit above that already filters it out (show=$(apt-cache show $pkg=$pkg_candidate | grep "^Source:" || true) <-- empty because src_pkg == bin_pkg and there's no Source: line)
[21:45] <vorlon> ddstreet: but then it hits corosync-qnetd, which does fail in the manner described
[23:48] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (disco-proposed) [2.578.5]
[23:49] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (cosmic-proposed) [2.542.5]
[23:50] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (bionic-proposed) [2.525.26]