[00:00] -queuebot:#ubuntu-release- New binary: volk [arm64] (hirsute-proposed/universe) [2.4.0-3] (no packageset)
[00:01] -queuebot:#ubuntu-release- New binary: volk [armhf] (hirsute-proposed/universe) [2.4.0-3] (no packageset)
[01:22] -queuebot:#ubuntu-release- New: accepted bornagain [amd64] (hirsute-proposed) [1.18.0-1]
[01:22] -queuebot:#ubuntu-release- New: accepted libosmocore [armhf] (hirsute-proposed) [1.4.1-3]
[01:22] -queuebot:#ubuntu-release- New: accepted volk [arm64] (hirsute-proposed) [2.4.0-3]
[01:22] -queuebot:#ubuntu-release- New: accepted libosmocore [arm64] (hirsute-proposed) [1.4.1-3]
[01:22] -queuebot:#ubuntu-release- New: accepted volk [armhf] (hirsute-proposed) [2.4.0-3]
[01:22] -queuebot:#ubuntu-release- New: accepted libosmocore [riscv64] (hirsute-proposed) [1.4.1-3]
[01:22] -queuebot:#ubuntu-release- New: accepted bpfcc [amd64] (hirsute-proposed) [0.17.0-8]
[01:22] -queuebot:#ubuntu-release- New: accepted bpfcc [ppc64el] (hirsute-proposed) [0.17.0-8]
[01:22] -queuebot:#ubuntu-release- New: accepted libosmocore [s390x] (hirsute-proposed) [1.4.1-3]
[01:22] -queuebot:#ubuntu-release- New: accepted volk [ppc64el] (hirsute-proposed) [2.4.0-3]
[01:22] -queuebot:#ubuntu-release- New: accepted volk [s390x] (hirsute-proposed) [2.4.0-3]
[01:22] -queuebot:#ubuntu-release- New: accepted bpfcc [arm64] (hirsute-proposed) [0.17.0-8]
[01:22] -queuebot:#ubuntu-release- New: accepted volk [amd64] (hirsute-proposed) [2.4.0-3]
[01:22] -queuebot:#ubuntu-release- New: accepted libosmocore [ppc64el] (hirsute-proposed) [1.4.1-3]
[01:22] -queuebot:#ubuntu-release- New: accepted volk [riscv64] (hirsute-proposed) [2.4.0-3]
[01:23] -queuebot:#ubuntu-release- New: accepted libosmocore [amd64] (hirsute-proposed) [1.4.1-3]
[03:42] -queuebot:#ubuntu-release- Unapproved: flatpak (groovy-proposed/universe) [1.8.2-1 => 1.8.3-0ubuntu0.1] (no packageset) (sync)
[03:50] <kenvandine> vorlon: according to my command history, i did not include binaries last time i did a copy-package on flatpak from that PPA.  I don't know why it looked like it did.  I just did it again, it definitely should not include binaries.  Hopefully it looks good now.
[03:50] <kenvandine> ahayzen: ^^
[03:51] <kenvandine> copy-package --from=~ahayzen/ubuntu/flatpak-manual-uploads-1-8-3-clean-1-groovy --from-suite=groovy --to=ubuntu --to-suite=groovy-proposed --sponsor ahayzen flatpak
[09:09] <Laney> Problem is you can't tell that when reviewing the queue
[09:09] <Laney> oh, no Ken
[09:11] <Laney> I feel like there must be a Launchpad bug for that but I can't find it
[09:13] <Laney> In [6]: groovy.getPackageUploads(status='Unapproved', name='flatpak')[0].contains_build
[09:13] <Laney> Out[6]: False
[09:13] <Laney> Someone™ once told me that you can't rely on that
[09:14] <Laney> like, maybe only one of contains_{build,copy,source} can be true at a time maybe?
[09:14]  * Laney is guessing
[09:15] <cjwatson> I don't think queue entries for copies have PackageUploadBuild rows linked to them
[09:16] <cjwatson> One of the several ways in which the interaction between copies and queues is a bit suboptimal
[09:18] <cjwatson> There's probably no good reason why PackageUpload.contains_build couldn't just have a quick look to see whether an associated PackageCopyJob has include_binaries set, though
[09:18] <cjwatson> But I don't believe there's a bug for it
[09:22] <Laney> Alrighty then, I will file one
[09:23] <Laney> contains_source is False too, feels like that should be True as well but less sure if that's useful for us
[09:41] <cjwatson> Maybe.  Either of them would be a semantic change and we might want to think about whether we expose it in some other way
[09:41] <cjwatson> Since tools might well assume that contains_source means there's an actual source package to download from the queue, and similarly contains_build for binaries
[09:47] <Laney> I suppose so, since you're expected to dereference the archive the entry was copied from and then download from that one, rather than the files being directly exposed on the package_upload object
[10:16] <doko> seb128: I see you did +1 yesterday, and today. test queues are busy, so maybe it would be good to look on synced transitions
[10:33] <seb128> doko, ack, I has a vac day yesterday but I'm going to do +1 today and tomorrow, I will check those
[10:34] <doko> seb128: and autopilot, or maybe ping jibel ;)
[11:28] -queuebot:#ubuntu-release- Unapproved: glib2.0 (focal-proposed/main) [2.64.3-1~ubuntu20.04.1 => 2.64.6-1~ubuntu20.04.1] (core, i386-whitelist)
[14:16] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-release-upgrader [source] (bionic-proposed) [1:18.04.42]
[14:48] <doko> rbalint: would you support overriding the glibc x32 test failures triggered by binutils?
[14:52] <rbalint> doko, it did not reproduce locally, i'm a bit nervous about a potential miscompilation
[14:53] <rbalint> doko, i'm looking into it, so we can make the call today
[14:53] <doko> ta, just want to use the binutils for the test rebuild next week
[15:27] <rbasak> sil2100: bug 1906627 has an adcli queue upload in bionic-proposed, which I think is wrong. I left a comment. Can I leave this one to you please?
[15:36] <sil2100> rbasak: hey! Yeah, I wanted to take a look at the whole adcli/sssd situation later today
[15:52] <rbalint> doko, apparently the test runner(s?) are running on amd opteron: http://autopkgtest.ubuntu.com/packages/cpuinfo/hirsute/amd64
[15:52] <rbalint> doko, could you please try reproducing the glibc vs binutils failure locally on ryzen?
[15:57] <doko> rbalint: ok, I'll do that
[15:57] <doko> damn, I shouldn't have told you about that machine ;p
[16:05] <rbalint> doko, :-P when mine arrives i'll tell you ;-)
[16:10] <vorlon> cjwatson, Laney: so is it expected that for a sourceful sync, when I *fetch* it from the queue, I get binaries?
[16:11] <Laney> Depends what you mean by expected
[16:11] <Laney> I think yes given how LP works now, probably not yes in terms of what we would want to happen
[16:11] <Laney> :-)
[16:11] <vorlon> Laney: is it true that seeing binares when I download it from the queue doesn't tell us whether it was a binary or sourceful sync
[16:11] <Laney> indeed
[16:11] <vorlon> hmm k
[16:12] <Laney> https://bugs.launchpad.net/launchpad/+bug/1907429
[16:12] <Laney> that's the one I filed earlier
[16:14] <rbalint> doko: LP: #1907472 , adding my observations
[16:20] -queuebot:#ubuntu-release- Unapproved: libvirt (focal-proposed/main) [6.0.0-0ubuntu8.5 => 6.0.0-0ubuntu8.6] (ubuntu-server, virt)
[16:20] -queuebot:#ubuntu-release- Unapproved: libvirt (groovy-proposed/main) [6.6.0-1ubuntu3.1 => 6.6.0-1ubuntu3.2] (ubuntu-server, virt)
[16:22] -queuebot:#ubuntu-release- Unapproved: libvirt (bionic-proposed/main) [4.0.0-1ubuntu8.17 => 4.0.0-1ubuntu8.18] (ubuntu-server, virt)
[16:38] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (bionic-proposed/main) [1:18.04.41 => 1:18.04.42] (core)
[16:40] <rbalint> doko, i've added the isa differences, the sse and avx2 differences seem interesting, i suspect sse issues with the latest binutils
[16:41] <rbalint> doko, and if i'm right probably the test on ryzen will pass, because it has updated isa
[16:56] <vorlon> ugh what's up with libtpms's libtool, it's suppressing compiler output /as if/ it were doing multiple passes and suppressing output for subsequent passes
[18:04] -queuebot:#ubuntu-release- New binary: libosmo-abis [s390x] (hirsute-proposed/universe) [1.0.1-2] (no packageset)
[18:04] -queuebot:#ubuntu-release- New binary: libgit2 [ppc64el] (hirsute-proposed/universe) [1.1.0+dfsg.1-2] (kubuntu)
[18:04] -queuebot:#ubuntu-release- New binary: libosmo-abis [ppc64el] (hirsute-proposed/universe) [1.0.1-2] (no packageset)
[18:04] -queuebot:#ubuntu-release- New binary: libgit2 [s390x] (hirsute-proposed/universe) [1.1.0+dfsg.1-2] (kubuntu)
[18:05] -queuebot:#ubuntu-release- New binary: osmo-ggsn [ppc64el] (hirsute-proposed/universe) [1.6.0-2] (no packageset)
[18:05] -queuebot:#ubuntu-release- New binary: osmo-ggsn [s390x] (hirsute-proposed/universe) [1.6.0-2] (no packageset)
[18:05] -queuebot:#ubuntu-release- New binary: btfs [s390x] (hirsute-proposed/universe) [2.23-1] (no packageset)
[18:06] -queuebot:#ubuntu-release- New binary: btfs [ppc64el] (hirsute-proposed/universe) [2.23-1] (no packageset)
[18:10] -queuebot:#ubuntu-release- New binary: libgit2 [amd64] (hirsute-proposed/universe) [1.1.0+dfsg.1-2] (kubuntu)
[18:10] -queuebot:#ubuntu-release- New binary: libosmo-abis [amd64] (hirsute-proposed/universe) [1.0.1-2] (no packageset)
[18:11] -queuebot:#ubuntu-release- New binary: btfs [riscv64] (hirsute-proposed/universe) [2.23-1] (no packageset)
[18:11] -queuebot:#ubuntu-release- New binary: libosmo-abis [riscv64] (hirsute-proposed/universe) [1.0.1-2] (no packageset)
[18:14] -queuebot:#ubuntu-release- New binary: osmo-ggsn [amd64] (hirsute-proposed/universe) [1.6.0-2] (no packageset)
[18:16] -queuebot:#ubuntu-release- New binary: btfs [amd64] (hirsute-proposed/universe) [2.23-1] (no packageset)
[18:16] -queuebot:#ubuntu-release- New binary: osmo-ggsn [riscv64] (hirsute-proposed/universe) [1.6.0-2] (no packageset)
[18:16] -queuebot:#ubuntu-release- New binary: node-has-yarn [amd64] (hirsute-proposed/universe) [2.1.0-1] (no packageset)
[18:22] -queuebot:#ubuntu-release- New binary: libosmo-abis [arm64] (hirsute-proposed/universe) [1.0.1-2] (no packageset)
[18:23] -queuebot:#ubuntu-release- New binary: octave [s390x] (hirsute-proposed/universe) [6.1.0-2] (no packageset)
[18:24] -queuebot:#ubuntu-release- New binary: libosmo-abis [armhf] (hirsute-proposed/universe) [1.0.1-2] (no packageset)
[18:27] -queuebot:#ubuntu-release- New binary: libgit2 [arm64] (hirsute-proposed/universe) [1.1.0+dfsg.1-2] (kubuntu)
[18:27] -queuebot:#ubuntu-release- New binary: libgit2 [armhf] (hirsute-proposed/universe) [1.1.0+dfsg.1-2] (kubuntu)
[18:29] -queuebot:#ubuntu-release- New binary: osmo-ggsn [arm64] (hirsute-proposed/universe) [1.6.0-2] (no packageset)
[18:29] -queuebot:#ubuntu-release- New binary: osmo-ggsn [armhf] (hirsute-proposed/universe) [1.6.0-2] (no packageset)
[18:32] -queuebot:#ubuntu-release- New binary: libgit2 [riscv64] (hirsute-proposed/universe) [1.1.0+dfsg.1-2] (kubuntu)
[18:39] -queuebot:#ubuntu-release- New binary: btfs [armhf] (hirsute-proposed/universe) [2.23-1] (no packageset)
[18:39] -queuebot:#ubuntu-release- New binary: btfs [arm64] (hirsute-proposed/universe) [2.23-1] (no packageset)
[18:40] -queuebot:#ubuntu-release- New binary: octave [ppc64el] (hirsute-proposed/universe) [6.1.0-2] (no packageset)
[18:48] -queuebot:#ubuntu-release- New binary: octave [amd64] (hirsute-proposed/universe) [6.1.0-2] (no packageset)
[19:55] -queuebot:#ubuntu-release- New: accepted libgit2 [amd64] (hirsute-proposed) [1.1.0+dfsg.1-2]
[19:55] -queuebot:#ubuntu-release- New: accepted libgit2 [armhf] (hirsute-proposed) [1.1.0+dfsg.1-2]
[19:55] -queuebot:#ubuntu-release- New: accepted libgit2 [riscv64] (hirsute-proposed) [1.1.0+dfsg.1-2]
[19:55] -queuebot:#ubuntu-release- New: accepted libgit2 [arm64] (hirsute-proposed) [1.1.0+dfsg.1-2]
[19:55] -queuebot:#ubuntu-release- New: accepted libgit2 [s390x] (hirsute-proposed) [1.1.0+dfsg.1-2]
[19:55] -queuebot:#ubuntu-release- New: accepted libgit2 [ppc64el] (hirsute-proposed) [1.1.0+dfsg.1-2]
[19:56] -queuebot:#ubuntu-release- New: accepted node-has-yarn [amd64] (hirsute-proposed) [2.1.0-1]
[19:57] -queuebot:#ubuntu-release- New: accepted btfs [amd64] (hirsute-proposed) [2.23-1]
[19:57] -queuebot:#ubuntu-release- New: accepted btfs [armhf] (hirsute-proposed) [2.23-1]
[19:57] -queuebot:#ubuntu-release- New: accepted btfs [riscv64] (hirsute-proposed) [2.23-1]
[19:57] -queuebot:#ubuntu-release- New: accepted btfs [arm64] (hirsute-proposed) [2.23-1]
[19:57] -queuebot:#ubuntu-release- New: accepted btfs [s390x] (hirsute-proposed) [2.23-1]
[19:57] -queuebot:#ubuntu-release- New: accepted btfs [ppc64el] (hirsute-proposed) [2.23-1]
[19:58] -queuebot:#ubuntu-release- New: accepted osmo-ggsn [amd64] (hirsute-proposed) [1.6.0-2]
[19:58] -queuebot:#ubuntu-release- New: accepted osmo-ggsn [armhf] (hirsute-proposed) [1.6.0-2]
[19:58] -queuebot:#ubuntu-release- New: accepted osmo-ggsn [riscv64] (hirsute-proposed) [1.6.0-2]
[19:58] -queuebot:#ubuntu-release- New: accepted osmo-ggsn [arm64] (hirsute-proposed) [1.6.0-2]
[19:58] -queuebot:#ubuntu-release- New: accepted osmo-ggsn [ppc64el] (hirsute-proposed) [1.6.0-2]
[19:59] -queuebot:#ubuntu-release- New: accepted libosmo-abis [amd64] (hirsute-proposed) [1.0.1-2]
[19:59] -queuebot:#ubuntu-release- New: accepted libosmo-abis [armhf] (hirsute-proposed) [1.0.1-2]
[19:59] -queuebot:#ubuntu-release- New: accepted libosmo-abis [riscv64] (hirsute-proposed) [1.0.1-2]
[19:59] -queuebot:#ubuntu-release- New: accepted osmo-ggsn [s390x] (hirsute-proposed) [1.6.0-2]
[19:59] -queuebot:#ubuntu-release- New: accepted libosmo-abis [arm64] (hirsute-proposed) [1.0.1-2]
[19:59] -queuebot:#ubuntu-release- New: accepted libosmo-abis [s390x] (hirsute-proposed) [1.0.1-2]
[19:59] -queuebot:#ubuntu-release- New: accepted libosmo-abis [ppc64el] (hirsute-proposed) [1.0.1-2]
[20:47] -queuebot:#ubuntu-release- New binary: octave [armhf] (hirsute-proposed/universe) [6.1.0-2] (no packageset)
[21:24] -queuebot:#ubuntu-release- New binary: octave [arm64] (hirsute-proposed/universe) [6.1.0-2] (no packageset)
[21:28] <ricotz> hi :), are there plans to transition from mysql-8.0 to mariadb-10.5?
[21:30] -queuebot:#ubuntu-release- New: accepted octave [amd64] (hirsute-proposed) [6.1.0-2]
[21:30] -queuebot:#ubuntu-release- New: accepted octave [armhf] (hirsute-proposed) [6.1.0-2]
[21:30] -queuebot:#ubuntu-release- New: accepted octave [s390x] (hirsute-proposed) [6.1.0-2]
[21:30] -queuebot:#ubuntu-release- New: accepted octave [arm64] (hirsute-proposed) [6.1.0-2]
[21:30] -queuebot:#ubuntu-release- New: accepted octave [ppc64el] (hirsute-proposed) [6.1.0-2]
[21:49] <vorlon> ricotz: a better question for the server team than the release team; but I don't believe so
[21:49] <vorlon> the server team has a relationship with mysql upstream and I haven't heard that there are any changes planned
[21:51] <ricotz> vorlon, I see, I am asking because debian seems to be doing something in this manner
[21:52] <vorlon> I understood that Debian had switched their default to mariadb quite a while ago; Ubuntu did not follow suit
[21:52] <ricotz> ok, thanks for the info
[22:28] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (focal-proposed) [6.0.0-0ubuntu8.6]
[22:28] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (groovy-proposed) [6.6.0-1ubuntu3.2]
[22:28] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (bionic-proposed) [4.0.0-1ubuntu8.18]
[22:34] <bryce> ubuntu-archive: I see that php8.0 has gotten sync'd into hirsute-proposed/universe, but we aren't planning on enabling php 8.0 this cycle.  Can you please remove it from 21.04?  LP: #1907177
[22:35] <bryce> ricotz, I can confirm there haven't been any discussions about that on the server team.
[22:38] <bryce> not recently anyway
[22:38] <ricotz> bryce, thanks for confirming
[22:52] <RAOF> bryce: You presumably want that removed and sync-blacklisted?
[22:52] <bryce> RAOF, yes indeed
[23:08] <vorlon> bryce: please subscribe ~ubuntu-archive to removal bugs
[23:12] <vorlon> bryce: to avoid future revisions of the package from being autosynced and migrating, do you want php8.0 added to the sync blacklist, or to keep an update-excuse bug open on it?
[23:13] <vorlon> hmm. something's gone seriously wrong with autosyncing, I've just found golang-github-keltia-archive that has been in unstable since Oct 2019 but hasn't gotten synced
[23:13] <vorlon> of course I've immediately clobbered the test case for this
[23:15] <vorlon> bryce: I mean block-proposed, not update-excuse
[23:18] <RAOF> vorlon: Shall I leave this to you, then?
[23:18] <bryce> vorlon, thanks.  I'm not sure what the distinction is between the sync blacklist vs. a block-proposed bug tag, but essentially we just want to hold off on php8.0 until we're ready to undertake that transition
[23:18] <vorlon> RAOF: ah yes, sorry, somehow I missed your comments
[23:19] <vorlon> ah; golang-github-keltia-archive was previously updated but then deleted due to autopkgtest regressions, so yay
[23:19] <vorlon> bryce: the difference is whether we block it in -proposed, or before -proposed
[23:19] <vorlon> personal taste as much as anything, I suppose
[23:19] <bryce> ah, before -proposed would be preferred
[23:19] <tumbleweed> if you block it in proposed, it'll block everything else in proposed...
[23:20] <vorlon> tumbleweed: it's not changing php-defaults, only php8.0
[23:20] <vorlon> bryce: then that's a sync-blacklist
[23:20] <bryce> right, I notice there are some proposed-migration excuses where php packages are listing php8.0, which we don't want
[23:20] <vorlon> but I'm on my way afk at the moment
[23:20] <vorlon> bryce: not that I see currently
[23:20] <vorlon> (no php8.0 references except php8.0 itself)
[23:21] <bryce> well, like I see it listed on https://autopkgtest.ubuntu.com/packages/p/php-amqplib/hirsute/amd64
[23:22] <bryce> ok, not proposed-migration excuses, but rather appearing in autopkgtest results.  But maybe that's just from php8.0 itself so no worry