=== pieq_ is now known as pieq
=== cpaelzer__ is now known as cpaelzer
[06:15] -queuebot:#ubuntu-release- Unapproved: libvirt (eoan-proposed/main) [5.4.0-0ubuntu5.1 => 5.4.0-0ubuntu5.2] (ubuntu-server, virt)
=== guiverc2 is now known as guiverc
[10:42] -queuebot:#ubuntu-release- Unapproved: linux-meta-oracle-5.0 (bionic-security/main) [5.0.0.1013.14 => 5.0.0.1013.14] (no packageset) (sync)
[10:42] -queuebot:#ubuntu-release- Unapproved: linux-meta-oracle-5.0 (bionic-updates/main) [5.0.0.1013.14 => 5.0.0.1013.14] (no packageset) (sync)
[10:44] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-oracle-5.0 [sync] (bionic-security) [5.0.0.1013.14]
[10:44] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-oracle-5.0 [sync] (bionic-updates) [5.0.0.1013.14]
[10:53] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-92.93~16.04.1] (kernel)
[10:54] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-92.93~16.04.1] (kernel)
[10:59] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-92.93~16.04.1]
[10:59] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-92.93~16.04.1]
[11:14] <cpaelzer> Hiho, what would we need to check if dbgsym packages are out of date?
[11:14] <cpaelzer> he build is 4 days ago, it migrated 3 days ago https://launchpad.net/ubuntu/+source/qemu/1:4.2-3ubuntu2
[11:15] <cpaelzer> https://launchpad.net/ubuntu/+source/qemu/1:4.2-3ubuntu2/+build/18833916 shows nothing odd in regard to dbgsym
[11:15] <cpaelzer> never the less "apt-cache policy qemu-system-x86-dbgsym qemu-system-x86" tells me that the dbgsym are still on 1:4.2-3ubuntu1
[11:15] <cpaelzer> might there be a part of the publishing infrastructure that needs a bump ?
[11:15] <cpaelzer> ubuntu-archive ^^ ?
[11:16] <locutus_> any AA please accept yagf from new queue, removed because of qt4 removal, now the new version is qt5
[11:19] -queuebot:#ubuntu-release- Unapproved: linux-base (eoan-proposed/main) [4.5ubuntu2 => 4.5ubuntu2.1] (core)
[11:20] -queuebot:#ubuntu-release- New: rejected yagf [sync] (focal-proposed) [0.9.5+repack1-1]
[11:21] -queuebot:#ubuntu-release- Unapproved: linux-base (bionic-proposed/main) [4.5ubuntu1 => 4.5ubuntu1.1] (core)
[11:21] -queuebot:#ubuntu-release- New binary: linux-base [amd64] (focal-proposed/main) [4.5ubuntu3] (core, i386-whitelist)
[11:23] <cjwatson> 61833   Mar 12 /bin/sh -c ~/ddeb-retriever/ddeb-retriever --verbose >>/srv/ddebs.ubuntu.com/logs/ddeb-retriever.log 2>&1
[11:23] <cjwatson> 61834   Mar 12  \_ /usr/bin/python3 /srv/ddebs.ubuntu.com//ddeb-retriever/ddeb-retriever --verbose
[11:23] <cjwatson> cpaelzer: ^- unstuck
[11:23] <cpaelzer> thank you cjwatson
[11:23] <cjwatson> (i.e. killed that process on numen)
[11:25] <cjwatson> Not sure why that got stuck - no obvious incident around then
[11:25] <cjwatson> It got stuck at 16:47ish, some hours before the GS2 edge network incident
[11:29] <cjwatson> cpaelzer: Also started up manually in screen since it was going to be an hour or so before it started for itself
[11:39] <locutus_> did anybody wrongly move llvm-toolchain-10 to main? I can't parse the reason for it not migrating clang-tidy-10/amd64 unsatisfiable Depends: clang-tools-10 and similar
[11:41] -queuebot:#ubuntu-release- New binary: linux-signed-oracle-5.0 [amd64] (bionic-proposed/main) [5.0.0-1014.19] (no packageset)
[11:42] -queuebot:#ubuntu-release- Unapproved: linux-base (xenial-proposed/main) [4.5ubuntu1~16.04.1 => 4.5ubuntu1.1~16.04.1] (core)
[11:42] <doko> locutus_: I did, but every new upload puts *every* binary package to main again
[11:49] <locutus_> but why? the sync I did, didn't change binaries or add new stuff
[11:49] <locutus_> so, why is stuff auto promoting? bug?
[12:09] -queuebot:#ubuntu-release- New source: what-is-python (focal-proposed/primary) [1]
[12:30] -queuebot:#ubuntu-release- New: rejected what-is-python [source] (focal-proposed) [1]
[12:30] -queuebot:#ubuntu-release- New: accepted what-is-python [source] (focal-proposed) [1]
[12:32] -queuebot:#ubuntu-release- New binary: what-is-python [amd64] (focal-proposed/none) [1] (no packageset)
[12:38] -queuebot:#ubuntu-release- New: accepted what-is-python [amd64] (focal-proposed) [1]
[12:42] <locutus_> doko, I didn't ask to reject yagf, but to accept it :)
[12:42] <locutus_> the syncd package is now qt5
[12:43] -queuebot:#ubuntu-release- New sync: yagf (focal-proposed/primary) [0.9.5+repack1-1]
[13:14] <doko> locutus_: sorry, misread
[13:15] -queuebot:#ubuntu-release- New: accepted yagf [sync] (focal-proposed) [0.9.5+repack1-1]
[13:18] -queuebot:#ubuntu-release- New binary: yagf [s390x] (focal-proposed/universe) [0.9.5+repack1-1] (no packageset)
[13:19] -queuebot:#ubuntu-release- New binary: yagf [amd64] (focal-proposed/universe) [0.9.5+repack1-1] (no packageset)
[13:19] -queuebot:#ubuntu-release- New binary: yagf [ppc64el] (focal-proposed/universe) [0.9.5+repack1-1] (no packageset)
[13:22] -queuebot:#ubuntu-release- New binary: yagf [arm64] (focal-proposed/universe) [0.9.5+repack1-1] (no packageset)
[13:22] -queuebot:#ubuntu-release- New binary: yagf [armhf] (focal-proposed/universe) [0.9.5+repack1-1] (no packageset)
[13:43] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (eoan-proposed/main) [5.3.0-1015.16] (core, kernel)
[13:43] -queuebot:#ubuntu-release- New binary: linux-signed-gke-4.15 [amd64] (bionic-proposed/main) [4.15.0-1056.59] (no packageset)
[13:50] -queuebot:#ubuntu-release- New: accepted linux-signed-gke-4.15 [amd64] (bionic-proposed) [4.15.0-1056.59]
[13:51] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (eoan-proposed) [5.3.0-1015.16]
[13:51] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle-5.0 [amd64] (bionic-proposed) [5.0.0-1014.19]
[13:51] <locutus_> no problem thanks!
[13:55] <ddstreet> cpaelzer fyi re: dbgsyms, you can always use pull-lp-ddebs
[13:56] <cpaelzer> ddstreet: I have got them from the build page already
[13:56] <cpaelzer> ddstreet: this was mostly to get the publishing fixed up
[13:56] <ddstreet> ack
[13:56] -queuebot:#ubuntu-release- New: accepted yagf [amd64] (focal-proposed) [0.9.5+repack1-1]
[13:56] -queuebot:#ubuntu-release- New: accepted yagf [armhf] (focal-proposed) [0.9.5+repack1-1]
[13:56] -queuebot:#ubuntu-release- New: accepted yagf [s390x] (focal-proposed) [0.9.5+repack1-1]
[13:57] -queuebot:#ubuntu-release- New: accepted yagf [arm64] (focal-proposed) [0.9.5+repack1-1]
[13:57] -queuebot:#ubuntu-release- New: accepted yagf [ppc64el] (focal-proposed) [0.9.5+repack1-1]
[15:16] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.9-2build1 => 1.3.9-2build1] (core)
[15:17] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.9-2build1 => 1.3.9-2build1] (core)
[15:18] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.9-2build1 => 1.3.9-2build1] (core)
[15:39] <vorlon> doko, xnox: why is what-is-python a separate source package instead of the binaries being provided by python3-defaults and python-defaults, and why are there python-dev packages which were not part of the design?
[15:39] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (focal-proposed) [1.3.9-2build1]
[15:39] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (focal-proposed) [1.3.9-2build1]
[15:39] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (focal-proposed) [1.3.9-2build1]
[15:54] <doko> vorlon: why do you want to run triggers on those?
[15:55] <vorlon> doko: I don't think moving code into suboptimal locations in the archive to avoid autopkgtest is a right thing to do
[15:55] <doko> no, I mentioned that at least in a call that these might be necessary
[15:55] <vorlon> "might be necessary" is not a decision that we're supporting it, why are we doing -dev packages?
[15:55] <doko> and I think introducing a delta isn't the right thing either
[15:55] <doko> because people expect to use python-config
[16:00] <xnox> vorlon:  separate source package, because this stuff is weird, and short term.
[16:00] <vorlon> xnox: so then someone has to remember to request removal of the weird, short-term package, instead of being able to figure out as part of our normal merge process that it can be dropped
[16:00] <vorlon> doko: why do we care that "people expect" to use python-config?
[16:01] <xnox> vorlon:  the Maintainer: will. Which is set to i
[16:01] <doko> because software will fail to configure/build?
[16:02] <vorlon> python-dev-is-python2-but-deprecated
[16:02] <vorlon> this package should not exist
[16:02] <vorlon> for sure
[16:02] <doko> it should. of the same reason that python-is-python2-but-deprecated exists
[16:02] <vorlon> we should not give users a package that lets them point python-config at python2
[16:03] <vorlon> no, python-is-python2-but-deprecated (which is also not the binary package name from the spec) is for runtime compatibility
[16:06] <doko> afk now, we can address this tomorrow in the meeing
[18:58] <rbalint> vorlon, i've filed an ffe for systemd 245, please consider it LP: #1867972
[18:58] <ubot5> Launchpad bug 1867972 in systemd (Ubuntu) " [FFe] Please accept systemd 245-2ubuntu1 to Focal" [Undecided,New] https://launchpad.net/bugs/1867972
[19:34] -queuebot:#ubuntu-release- Unapproved: python-barbicanclient (bionic-proposed/main) [4.6.0-0ubuntu1 => 4.6.0-0ubuntu1.1] (openstack, ubuntu-server)
[19:42] <blackboxsw> vorlon hiya if theres time can someone please review ack https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1866930 we have landed a branch with this support in tip of master for cloud-init
[19:42] <ubot5> Ubuntu bug 1866930 in cloud-init (Ubuntu) "[FFe] ec2 add support for configuring secondary NICs and secondary ipv4 and ipv6 addresses" [High,Fix committed]
[19:42] <blackboxsw> and we would like to queue an upload with that cherry pick into focal if we can
[20:47] -queuebot:#ubuntu-release- New: accepted linux-base [amd64] (focal-proposed) [4.5ubuntu3]
[20:49] -queuebot:#ubuntu-release- Unapproved: accepted linux-base [source] (eoan-proposed) [4.5ubuntu2.1]
[20:51] -queuebot:#ubuntu-release- Unapproved: accepted linux-base [source] (bionic-proposed) [4.5ubuntu1.1]
[20:55] -queuebot:#ubuntu-release- New binary: linux-base [amd64] (eoan-proposed/main) [4.5ubuntu2.1] (core)
[20:56] -queuebot:#ubuntu-release- New binary: linux-base [amd64] (bionic-proposed/main) [4.5ubuntu1.1] (core)
[21:19] -queuebot:#ubuntu-release- New: accepted linux-base [amd64] (eoan-proposed) [4.5ubuntu2.1]
[21:20] -queuebot:#ubuntu-release- New: accepted linux-base [amd64] (bionic-proposed) [4.5ubuntu1.1]
[22:24] <Kamilion> just curious if the dh-python runtime warnings will be suppressed soon or not? #1863195
[22:44] <vorlon> kanashiro: are you still working on the ruby transition?  I see a lot of unaddressed autopkgtest regresions; should I start removing packages?
[22:45] <kanashiro> vorlon, I am still working on it. I just fixed 2 packages in Debian, waiting for them to land in unstable to request a sync; and other 3 I have fixes in Debian but in new major upstream releases, so I need to request a FFe
[22:46] -queuebot:#ubuntu-release- Unapproved: apport (eoan-proposed/main) [2.20.11-0ubuntu8.6 => 2.20.11-0ubuntu8.7] (core)
[22:47] -queuebot:#ubuntu-release- Unapproved: apport (bionic-proposed/main) [2.20.9-0ubuntu7.12 => 2.20.9-0ubuntu7.13] (core)
[22:55] <vorlon> kanashiro: given that there are some 14 packages still showing regressions, how quickly do you think we'll have the rest sorted?  Note that ruby-defaults is also entangled with both the apt and icu transitions, which is mainly why I care
[22:57] <kanashiro> vorlon, I want to get those packages which I already have fixes tomorrow, after that we can start to remove the remaining packages. Can I let you know on Friday? about the status
[22:58] <vorlon> kanashiro: works for me
[22:58] <kanashiro> great
[23:24] <vorlon> rbalint: systemd-p11kit> oh dear
[23:25] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (bionic-proposed/main) [5.0.0-1035.37] (kernel)