[00:22] -queuebot:#ubuntu-release- New: rejected dmarc-cat [amd64] (eoan-proposed) [0.9.2-1ubuntu1]
[00:22] -queuebot:#ubuntu-release- New: rejected dmarc-cat [armhf] (eoan-proposed) [0.9.2-1ubuntu1]
[00:22] -queuebot:#ubuntu-release- New: rejected dmarc-cat [ppc64el] (eoan-proposed) [0.9.2-1ubuntu1]
[00:22] -queuebot:#ubuntu-release- New: rejected dmarc-cat [arm64] (eoan-proposed) [0.9.2-1ubuntu1]
[00:22] -queuebot:#ubuntu-release- New: rejected dmarc-cat [s390x] (eoan-proposed) [0.9.2-1ubuntu1]
[00:22] -queuebot:#ubuntu-release- New: rejected dmarc-cat [i386] (eoan-proposed) [0.9.2-1ubuntu1]
[00:29] -queuebot:#ubuntu-release- New: accepted hy [source] (eoan-proposed) [0.16.0-0ubuntu1]
[00:35] -queuebot:#ubuntu-release- New: accepted ubiquity [amd64] (eoan-proposed) [19.10.2]
[00:35] -queuebot:#ubuntu-release- New: accepted ubiquity [armhf] (eoan-proposed) [19.10.2]
[00:35] -queuebot:#ubuntu-release- New: accepted ubiquity [ppc64el] (eoan-proposed) [19.10.2]
[00:35] -queuebot:#ubuntu-release- New: accepted ubiquity [arm64] (eoan-proposed) [19.10.2]
[00:36] -queuebot:#ubuntu-release- New: accepted ubiquity [i386] (eoan-proposed) [19.10.2]
[05:13] -queuebot:#ubuntu-release- New binary: r-cran-webgestaltr [ppc64el] (eoan-proposed/universe) [0.4.0-1] (no packageset)
[05:13] -queuebot:#ubuntu-release- New binary: r-cran-webgestaltr [s390x] (eoan-proposed/universe) [0.4.0-1] (no packageset)
[05:13] -queuebot:#ubuntu-release- New binary: r-cran-webgestaltr [amd64] (eoan-proposed/universe) [0.4.0-1] (no packageset)
[05:13] -queuebot:#ubuntu-release- New binary: r-cran-webgestaltr [i386] (eoan-proposed/universe) [0.4.0-1] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: r-cran-webgestaltr [arm64] (eoan-proposed/universe) [0.4.0-1] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: r-cran-webgestaltr [armhf] (eoan-proposed/universe) [0.4.0-1] (no packageset)
[08:35] -queuebot:#ubuntu-release- Unapproved: accepted gcc-9 [sync] (disco-proposed) [9.1.0-2ubuntu2~19.04]
[08:36] -queuebot:#ubuntu-release- Unapproved: accepted gcc-9-cross [sync] (disco-proposed) [4ubuntu4.1]
[08:37] -queuebot:#ubuntu-release- Unapproved: accepted gcc-9-cross-ports [sync] (disco-proposed) [3ubuntu4.1]
[09:11] -queuebot:#ubuntu-release- Unapproved: yaru-theme (disco-proposed/main) [19.04.2 => 19.04.3] (desktop-core)
[09:25] -queuebot:#ubuntu-release- Unapproved: accepted yaru-theme [source] (disco-proposed) [19.04.3]
[09:49] <LocutusOfBorg> any AA can please remove hy 0.16.0-0ubuntu1 from eoan-proposed? I want to do some testing with the old version before updating... never built
[09:50] <LocutusOfBorg> I don't know why but today the old version seems building
[09:58] -queuebot:#ubuntu-release- Unapproved: update-notifier (bionic-proposed/main) [3.192.1.6 => 3.192.1.7] (ubuntu-desktop, ubuntu-server)
[10:00] <tjaalton> vorlon: do you want to handle fwupd* et al on bionic queue/NEW? fwupd is still on unapproved for some reason, while libxmlb and fwupd-signed are already on NEW..
[10:01] <seb128> tjaalton, there is no "some reason/while" here, those 2 are packages that don't exist today in bionic so  uploading them hit sourceNEW and not unapproved
[10:02] <tjaalton> seb128: oh, source NEW?
[10:02] <tjaalton> even more reason for an AA to review them in tandem
[10:03] <seb128> tjaalton, yes, the first one is a new library that is needed by the new fwupd version
[10:03] <seb128> right
[10:03] <seb128> I don't expect that to be an easy SRU, maybe best for vorlon to review :)
[10:04] <tjaalton> right, I'll do the easier ones then :)
[10:11] <LocutusOfBorg> apw, please kick hy out from eoan...
[10:12] <LocutusOfBorg> I want to replace with a copy from cosmic
[10:12] <LocutusOfBorg> and then do a no-change rebuild
[10:12] <LocutusOfBorg> and fix failures with single patches on top of 0.12 because the new version requires lots of other library updates
[10:20] <tjaalton> xnox: why is openssl targeted for 'disco-updates' instead of proposed? the sru tooling doesn't see the diff so it's harder to review
[10:24] <Laney> worse than that, that means that when you accept it it'll go straight to -updates
[10:24] <Laney> (AIUI)
[10:30] <tjaalton> sigh
[10:31] <Laney> reject it :>
[10:31] <tjaalton> done
[10:32] -queuebot:#ubuntu-release- Unapproved: rejected openssl [source] (disco-updates) [1.1.1b-1ubuntu2.1]
[10:39] -queuebot:#ubuntu-release- Unapproved: accepted dkms [source] (disco-proposed) [2.6.1-4ubuntu2.1]
[10:39] -queuebot:#ubuntu-release- Unapproved: accepted dkms [source] (cosmic-proposed) [2.3-3ubuntu11.1]
[10:40] -queuebot:#ubuntu-release- Unapproved: accepted dkms [source] (bionic-proposed) [2.3-3ubuntu9.3]
[10:40] -queuebot:#ubuntu-release- Unapproved: accepted dkms [source] (xenial-proposed) [2.2.0.3-2ubuntu11.7]
[11:16] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (bionic-proposed) [3.192.1.7]
[12:00] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (disco-proposed/main) [5.0.0-1007.7] (core, kernel)
[14:00] -queuebot:#ubuntu-release- Unapproved: rejected software-properties [source] (bionic-proposed) [0.96.24.32.9]
[14:20] <sil2100> Laney: ok, I finally had a moment to sit down on the britney SRU regression thingy - fixed a few things regarding state record and read, but in besides that it seems to be working correctly
[14:20] <sil2100> Laney: for instance yeah, it doesn't send a message for libseccomp for bionic because that upload has no launchpad bugs in its .changes
[14:20] <sil2100> Laney: for bionic at least it seems that for all the others it did the 'right thing'
[14:21] <Laney> sil2100: oh! thanks, I didn't consider that possibliity :-O
[15:06] -queuebot:#ubuntu-release- Unapproved: software-properties (bionic-proposed/main) [0.96.24.32.8 => 0.96.24.32.9] (desktop-core, ubuntu-server)
[15:13] <Laney> vorlon: Looks like bos02 randomly healed itself... going to turn it back on
[15:24] -queuebot:#ubuntu-release- Unapproved: accepted software-properties [source] (bionic-proposed) [0.96.24.32.9]
[15:24] <vorlon> Laney: heh ok
[15:25] <Laney> such reliable
[16:09] <LocutusOfBorg> any AA please remove hy from eoan, and let me copy the previous binary from cosmic
[16:09] <LocutusOfBorg> vorlon, ^^ :D
[16:09] <LocutusOfBorg> pleeeeeeease
[16:09] <LocutusOfBorg> (rationale above)
[16:09] <vorlon> mm
[16:09] <LocutusOfBorg> the new release can't build...
[16:09] <LocutusOfBorg> and the old one seems to build fine now
[16:10] <LocutusOfBorg> I spent three days trying to make the new one work, but requires lots of more changes, in other python libs
[16:10] <LocutusOfBorg> better stick with cosmic and cherry-pick fixes
[16:10] <vorlon> removed
[16:10] <LocutusOfBorg> or let debian do it :D
[16:10] <LocutusOfBorg> <3
[16:10] <vorlon> but why was it uploaded to eoan if it wasn't buildable?
[16:11] <LocutusOfBorg> mistake, it was directed to ppa!
[16:11] <LocutusOfBorg> I asked to not accept few times, and I gave up...
[16:11] <LocutusOfBorg> anyway, ./copy-package --from=ubuntu --from-suite=cosmic hy --to=ubuntu --to-suite=eoan-proposed -b
[16:11] <LocutusOfBorg> correct?
[16:11]  * LocutusOfBorg tries and goes catching a train
[16:12] -queuebot:#ubuntu-release- New sync: hy (eoan-proposed/primary) [0.12.1-2]
[16:12] <vorlon> LocutusOfBorg: syntactically correct, but I'm not happy to accept a binary sync from cosmic to eoan of a package that was dropped in disco
[16:14] -queuebot:#ubuntu-release- New: rejected hy [sync] (eoan-proposed) [0.12.1-2]
[16:17] -queuebot:#ubuntu-release- New: accepted r-cran-webgestaltr [amd64] (eoan-proposed) [0.4.0-1]
[16:17] -queuebot:#ubuntu-release- New: accepted r-cran-webgestaltr [armhf] (eoan-proposed) [0.4.0-1]
[16:18] -queuebot:#ubuntu-release- New: accepted r-cran-webgestaltr [ppc64el] (eoan-proposed) [0.4.0-1]
[16:18] -queuebot:#ubuntu-release- New: accepted r-cran-webgestaltr [arm64] (eoan-proposed) [0.4.0-1]
[16:18] -queuebot:#ubuntu-release- New: accepted r-cran-webgestaltr [s390x] (eoan-proposed) [0.4.0-1]
[16:18] -queuebot:#ubuntu-release- New: accepted r-cran-webgestaltr [i386] (eoan-proposed) [0.4.0-1]
[16:18] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (disco-proposed) [5.0.0-1007.7]
[16:20] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1039.44] (kernel)
[16:21] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1039.44]
[16:27] <LocutusOfBorg> ok, so better now?
[16:27] <LocutusOfBorg> I or should I upload a build1 version?
[16:28] -queuebot:#ubuntu-release- New sync: hy (eoan-proposed/primary) [0.12.1-2]
[16:28] <LocutusOfBorg> I uploaded both :D
[16:41] <vorlon> LocutusOfBorg: I don't mean that you should sync it from a different release, I mean that I'm not accepting a forward-sync of a package that was dropped in disco.  sourceful upload.
[16:42] <vorlon> LocutusOfBorg: and I only see your sync, not your build1 upload
[16:42] <vorlon> (I did write that in the reject comment before, which I guess you didn't see before re-syncing)
[16:43] -queuebot:#ubuntu-release- New: rejected hy [sync] (eoan-proposed) [0.12.1-2]
[17:00] <LocutusOfBorg> vorlon, I think I did it now, the build1 was "ENONET" interrupted
[17:01] -queuebot:#ubuntu-release- New source: hy (eoan-proposed/primary) [0.12.1-2build1]
[17:02] -queuebot:#ubuntu-release- New: accepted hy [source] (eoan-proposed) [0.12.1-2build1]
[17:03] <LocutusOfBorg> and no, sorry I didn't receive the reject email, even now
[17:06] -queuebot:#ubuntu-release- New binary: hy [amd64] (eoan-proposed/universe) [0.12.1-2build1] (no packageset)
[17:06] <LocutusOfBorg> strange that it built without touching it... meh
[17:07] <LocutusOfBorg> I suppose autopkgtests will be sad
[17:11] <LocutusOfBorg> vorlon, please accept it? :)
[17:12] <LocutusOfBorg> so I can start my weekend having fixed itk4  poppler elastix lintian hy and deken from proposed :D
[17:12] <LocutusOfBorg> acorn is ongoing upstream work
[17:16] -queuebot:#ubuntu-release- New: accepted hy [amd64] (eoan-proposed) [0.12.1-2build1]
[17:18] <jdstrand> sil2100, Laney: note that the libseccomp is there for wider testing before the security team publishes a USN. it isn't a normal SRU
[17:46] -queuebot:#ubuntu-release- New binary: deken [amd64] (eoan-proposed/universe) [0.5.1-1] (no packageset)
[20:18] -queuebot:#ubuntu-release- Unapproved: ec2-hibinit-agent (bionic-proposed/universe) [1.0.0-0ubuntu4~18.04.0 => 1.0.0-0ubuntu4~18.04.1] (no packageset)
[20:18] -queuebot:#ubuntu-release- Unapproved: ec2-hibinit-agent (disco-proposed/universe) [1.0.0-0ubuntu4 => 1.0.0-0ubuntu4.19.04.0] (no packageset)
[20:18] -queuebot:#ubuntu-release- Unapproved: ec2-hibinit-agent (cosmic-proposed/universe) [1.0.0-0ubuntu4~18.10.0 => 1.0.0-0ubuntu4~18.10.1] (no packageset)
[20:18] -queuebot:#ubuntu-release- Unapproved: ec2-hibinit-agent (xenial-proposed/universe) [1.0.0-0ubuntu4~16.04.0 => 1.0.0-0ubuntu4~16.04.1] (no packageset)
[20:28] <rbalint> tjaalton, vorlon could you please accept those packages? ^
[20:28] <rbalint> the diff is tiny :-)
[20:34] <vorlon> rbalint: I don't understand why the test case involves a long-running process. is that to prove that the instance resumed, as opposed to something else (auto-killed by the hypervisor due to networking not coming up?)
[20:35] <vorlon> haha I feel we should really take a closer look at the interaction between this hook, and the hook in lizardfs-chunkserver
[20:36] <rbalint>  vorlon yes, just to prove that the instance is resumed
[20:37] <vorlon> ok
[20:37] <rbalint> i just use screen top
[20:38] -queuebot:#ubuntu-release- Unapproved: accepted ec2-hibinit-agent [source] (disco-proposed) [1.0.0-0ubuntu4.19.04.0]
[20:42] -queuebot:#ubuntu-release- Unapproved: accepted ec2-hibinit-agent [source] (cosmic-proposed) [1.0.0-0ubuntu4~18.10.1]
[20:48] -queuebot:#ubuntu-release- Unapproved: accepted ec2-hibinit-agent [source] (bionic-proposed) [1.0.0-0ubuntu4~18.04.1]
[23:50] -queuebot:#ubuntu-release- Unapproved: rejected geary [source] (bionic-proposed) [0.12.4-4~ubuntu0.18.04.1]