[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) === pieq_ is now known as pieq [03:50] 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] ahayzen: ^^ [03:51] 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] Problem is you can't tell that when reviewing the queue [09:09] oh, no Ken [09:11] I feel like there must be a Launchpad bug for that but I can't find it [09:13] In [6]: groovy.getPackageUploads(status='Unapproved', name='flatpak')[0].contains_build [09:13] Out[6]: False [09:13] Someoneā„¢ once told me that you can't rely on that [09:14] like, maybe only one of contains_{build,copy,source} can be true at a time maybe? [09:14] * Laney is guessing [09:15] I don't think queue entries for copies have PackageUploadBuild rows linked to them [09:16] One of the several ways in which the interaction between copies and queues is a bit suboptimal [09:18] 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] But I don't believe there's a bug for it [09:22] Alrighty then, I will file one [09:23] contains_source is False too, feels like that should be True as well but less sure if that's useful for us [09:41] 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] 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] 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] 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] doko, ack, I has a vac day yesterday but I'm going to do +1 today and tomorrow, I will check those [10:34] 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] rbalint: would you support overriding the glibc x32 test failures triggered by binutils? [14:52] doko, it did not reproduce locally, i'm a bit nervous about a potential miscompilation [14:53] doko, i'm looking into it, so we can make the call today [14:53] ta, just want to use the binutils for the test rebuild next week [15:27] 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:27] bug 1906627 in adcli (Ubuntu Bionic) "GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression" [High,In progress] https://launchpad.net/bugs/1906627 [15:36] rbasak: hey! Yeah, I wanted to take a look at the whole adcli/sssd situation later today [15:52] doko, apparently the test runner(s?) are running on amd opteron: http://autopkgtest.ubuntu.com/packages/cpuinfo/hirsute/amd64 [15:52] doko, could you please try reproducing the glibc vs binutils failure locally on ryzen? [15:57] rbalint: ok, I'll do that [15:57] damn, I shouldn't have told you about that machine ;p [16:05] doko, :-P when mine arrives i'll tell you ;-) [16:10] cjwatson, Laney: so is it expected that for a sourceful sync, when I *fetch* it from the queue, I get binaries? [16:11] Depends what you mean by expected [16:11] I think yes given how LP works now, probably not yes in terms of what we would want to happen [16:11] :-) [16:11] 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] indeed [16:11] hmm k [16:12] https://bugs.launchpad.net/launchpad/+bug/1907429 [16:12] Ubuntu bug 1907429 in Launchpad itself "Can't tell if copies in distro upload queues contain binaries or not" [Undecided,New] [16:12] that's the one I filed earlier [16:14] doko: LP: #1907472 , adding my observations [16:14] Launchpad bug 1907472 in glibc (Ubuntu) "glibc x32 autopkgtest fails in hirsute with binutils and audit in -proposed" [Undecided,New] https://launchpad.net/bugs/1907472 [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] doko, i've added the isa differences, the sse and avx2 differences seem interesting, i suspect sse issues with the latest binutils [16:41] doko, and if i'm right probably the test on ryzen will pass, because it has updated isa [16:56] 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 === ijohnson is now known as ijohnson|lunch [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) === ijohnson|lunch is now known as ijohnson [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] 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] ricotz: a better question for the server team than the release team; but I don't believe so [21:49] the server team has a relationship with mysql upstream and I haven't heard that there are any changes planned [21:51] vorlon, I see, I am asking because debian seems to be doing something in this manner [21:52] I understood that Debian had switched their default to mariadb quite a while ago; Ubuntu did not follow suit [21:52] 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] 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:34] Launchpad bug 1907177 in php8.0 (Ubuntu) "Please remove php8.0 from Ubuntu 21.04" [Undecided,New] https://launchpad.net/bugs/1907177 [22:35] ricotz, I can confirm there haven't been any discussions about that on the server team. [22:38] not recently anyway [22:38] bryce, thanks for confirming [22:52] bryce: You presumably want that removed and sync-blacklisted? [22:52] RAOF, yes indeed [23:08] bryce: please subscribe ~ubuntu-archive to removal bugs [23:12] 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] 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] of course I've immediately clobbered the test case for this [23:15] bryce: I mean block-proposed, not update-excuse [23:18] vorlon: Shall I leave this to you, then? [23:18] 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] RAOF: ah yes, sorry, somehow I missed your comments [23:19] ah; golang-github-keltia-archive was previously updated but then deleted due to autopkgtest regressions, so yay [23:19] bryce: the difference is whether we block it in -proposed, or before -proposed [23:19] personal taste as much as anything, I suppose [23:19] ah, before -proposed would be preferred [23:19] if you block it in proposed, it'll block everything else in proposed... [23:20] tumbleweed: it's not changing php-defaults, only php8.0 [23:20] bryce: then that's a sync-blacklist [23:20] right, I notice there are some proposed-migration excuses where php packages are listing php8.0, which we don't want [23:20] but I'm on my way afk at the moment [23:20] bryce: not that I see currently [23:20] (no php8.0 references except php8.0 itself) [23:21] well, like I see it listed on https://autopkgtest.ubuntu.com/packages/p/php-amqplib/hirsute/amd64 [23:22] ok, not proposed-migration excuses, but rather appearing in autopkgtest results. But maybe that's just from php8.0 itself so no worry