[02:20] -queuebot:#ubuntu-release- New source: gallery-dl (focal-backports/primary) [1.20.0-1~bpo20.04.1]
[08:31] <cpaelzer> didrocks: good morning, could I bother you with my AA-pings of yesterday? It seems most AAs are still in the deserved winter-break
[08:32] <didrocks> cpaelzer: oh sure, let me backlog
[08:33] <didrocks> ah, there were an autodemote
[08:36] <didrocks> interesting, change-override is telling me that everything is already in main (fuse3 source and binary packages), while rmadison disagrees and only list the source as being in main
[08:36] <cpaelzer> yeah and open-vm-tools is stuck in an component mismatch missing fuse3 binary
[08:37] <cpaelzer> maybe one of those -proposed vs -release cases?
[08:37] <cpaelzer> hmm, no it seems there is no -proposed of fuse3 right now
[08:38] <didrocks> cpaelzer: well, it wouldn’t explain the rmadison vs change-override mismatch
[08:38] <didrocks> either someone promoted it in between and we are missing a publisher cycle
[08:38] <didrocks> either… I don’t really know. Unfortunately, those changes are not reflected in the publishing history: https://launchpad.net/ubuntu/+source/fuse3/3.10.5-1/+publishinghistory
[08:39] <didrocks> but yeah:
[08:39] <didrocks> rmadison -s jammy fuse3
[08:39] <didrocks>  fuse3 | 3.10.5-1 | jammy          | source
[08:39] <didrocks>  fuse3 | 3.10.5-1 | jammy/universe | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
[08:39] <cpaelzer> well, we can wait and re-check on monday for fuse3
[08:39] <didrocks> I would say let’s wait for a few hours and recheck, indeed
[08:39] <didrocks> if we still see the mismatch on Monday, we can check with the launchpad team
[08:40]  * cpaelzer hopes that DPDK isn't also exposing odd behavior
[08:40] <didrocks> FYI: "fuse3 3.10.5-1 in jammy amd64 remained the same" which matches "fuse3 3.10.5-1 in jammy amd64: main/utils/optional/100% -> main"
[08:40] <didrocks> (so, definitively in main already from the launchpad standpoint)
[08:40] <cpaelzer> thanks for checking, I'll have a look later and on monday then
[08:41] <didrocks> keep me posted!
[08:50] <cpaelzer> didrocks: did accepting DPDK from new queue and promoting the new binaries cause trouble as well?
[08:56] <didrocks> cpaelzer: there are a lot of binary packages to check, all done now. Just before accepting, some binary packages are intended for universe, is that correct? librte-meta-event_21.11-1_arm64.deb,  librte-meta-all_21.11-1_arm64.deb,   librte-meta-net_21.11-1_arm64.deb… Basically all non new ones… Where should they end?
[09:02] -queuebot:#ubuntu-release- New binary: box2d [amd64] (jammy-proposed/universe) [2.4.1-2ubuntu1] (no packageset)
[09:03] -queuebot:#ubuntu-release- New binary: box2d [ppc64el] (jammy-proposed/universe) [2.4.1-2ubuntu1] (no packageset)
[09:03] -queuebot:#ubuntu-release- New binary: box2d [s390x] (jammy-proposed/universe) [2.4.1-2ubuntu1] (no packageset)
[09:15] -queuebot:#ubuntu-release- New binary: box2d [arm64] (jammy-proposed/universe) [2.4.1-2ubuntu1] (no packageset)
[09:15] -queuebot:#ubuntu-release- New binary: box2d [armhf] (jammy-proposed/universe) [2.4.1-2ubuntu1] (no packageset)
[09:17] <cpaelzer> didrocks: yes some binaries are for universe
[09:18] <didrocks> cpaelzer: ack, I let the default promotions on all new binaries for main and then, if we need to demote, we can
[09:18] <didrocks> sounds good to you?
[09:20] <cpaelzer> yes that should be ok
[09:20] <cpaelzer> thanks didrocks
[09:25] -queuebot:#ubuntu-release- New: accepted dpdk [amd64] (jammy-proposed) [21.11-1]
[09:25] -queuebot:#ubuntu-release- New: accepted dpdk [ppc64el] (jammy-proposed) [21.11-1]
[09:25] -queuebot:#ubuntu-release- New: accepted dpdk [arm64] (jammy-proposed) [21.11-1]
[09:25] <didrocks> yw, done ^
[09:36] -queuebot:#ubuntu-release- New binary: box2d [riscv64] (jammy-proposed/universe) [2.4.1-2ubuntu1] (no packageset)
[10:56] -queuebot:#ubuntu-release- Unapproved: openvswitch (focal-proposed/main) [2.13.3-0ubuntu0.20.04.2 => 2.13.5-0ubuntu1] (ubuntu-server)
[10:56] -queuebot:#ubuntu-release- Unapproved: openvswitch (hirsute-proposed/main) [2.15.0-0ubuntu3.1 => 2.15.2-0ubuntu1] (core)
[11:19] -queuebot:#ubuntu-release- New binary: ipmctl [amd64] (jammy-proposed/universe) [03.00.00.0423-1] (no packageset)
[12:30] -queuebot:#ubuntu-release- New: accepted capnproto [riscv64] (jammy-proposed) [0.8.0-2]
[12:30] -queuebot:#ubuntu-release- New: accepted ipmctl [amd64] (jammy-proposed) [03.00.00.0423-1]
[15:38] <sergiodj> cjwatson: ubuntu-archive: it took more time than I expected, but I dropped armhf from the list of supported arches for kmerresistance, which should unblock kma in -proposed once the old armhf binaries are removed for both packages.  could you please do it?
[15:41] <cjwatson> sergiodj: done for both
[15:41] <sergiodj> cjwatson: thank you
[17:21] -queuebot:#ubuntu-release- New binary: astroml [amd64] (jammy-proposed/none) [1.0.2~a1-1] (no packageset)
[21:19] -queuebot:#ubuntu-release- Unapproved: cpuset (focal-proposed/universe) [1.6-3.1 => 1.6-3.1ubuntu1] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: asdf-coordinates-schemas [amd64] (jammy-proposed/none) [0.1.0-1] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: asdf-transform-schemas [amd64] (jammy-proposed/none) [0.2.0-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: asdf-astropy [amd64] (jammy-proposed/none) [0.1.2-1] (no packageset)