[00:31] -queuebot:#ubuntu-release- New: accepted directx-headers [source] (hirsute-proposed) [1.0.2-0ubuntu1] [00:34] -queuebot:#ubuntu-release- New binary: directx-headers [s390x] (hirsute-proposed/none) [1.0.2-0ubuntu1] (no packageset) [00:35] -queuebot:#ubuntu-release- New binary: directx-headers [arm64] (hirsute-proposed/none) [1.0.2-0ubuntu1] (no packageset) [00:35] -queuebot:#ubuntu-release- New binary: directx-headers [ppc64el] (hirsute-proposed/none) [1.0.2-0ubuntu1] (no packageset) [00:35] -queuebot:#ubuntu-release- New binary: directx-headers [armhf] (hirsute-proposed/none) [1.0.2-0ubuntu1] (no packageset) [00:36] -queuebot:#ubuntu-release- New binary: directx-headers [amd64] (hirsute-proposed/none) [1.0.2-0ubuntu1] (no packageset) [00:54] -queuebot:#ubuntu-release- New binary: directx-headers [riscv64] (hirsute-proposed/universe) [1.0.2-0ubuntu1] (no packageset) [01:30] vorlon: well I guess I want this grub to migrate in hirsute before uploading armhf fixes, packaging fixes, ppc64el patches.... [01:53] -queuebot:#ubuntu-release- Unapproved: rejected neutron [source] (bionic-proposed) [2:12.1.1-0ubuntu4] [01:53] -queuebot:#ubuntu-release- Unapproved: rejected neutron [source] (bionic-proposed) [2:12.1.1-0ubuntu4] [02:10] -queuebot:#ubuntu-release- Unapproved: accepted west-chamber [source] (focal-proposed) [20100405+svn20111107.r124-12ubuntu0.2~20.04.1] [04:20] RAOF: thanks! looks like it got accepted to debian too, that was quick ;) [04:22] tjaalton: you might want to change the licence to “Expat” (because it's that flavour of MIT) but that wasn't blocking 😀 [04:36] ah ok, committed to git :) [04:46] -queuebot:#ubuntu-release- New binary: directx-headers [ppc64el] (hirsute-proposed/universe) [1.0.2-1] (no packageset) [04:46] -queuebot:#ubuntu-release- New binary: directx-headers [s390x] (hirsute-proposed/universe) [1.0.2-1] (no packageset) [04:47] -queuebot:#ubuntu-release- New binary: directx-headers [amd64] (hirsute-proposed/universe) [1.0.2-1] (no packageset) [04:47] -queuebot:#ubuntu-release- New binary: directx-headers [armhf] (hirsute-proposed/universe) [1.0.2-1] (no packageset) [04:47] -queuebot:#ubuntu-release- New binary: directx-headers [arm64] (hirsute-proposed/universe) [1.0.2-1] (no packageset) [05:07] -queuebot:#ubuntu-release- New binary: directx-headers [riscv64] (hirsute-proposed/universe) [1.0.2-1] (no packageset) === didrocks2 is now known as didrocks [09:21] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (hirsute-proposed) [5.8.0-1024.26+21.04.1] [10:09] -queuebot:#ubuntu-release- New: accepted directx-headers [amd64] (hirsute-proposed) [1.0.2-0ubuntu1] [10:09] -queuebot:#ubuntu-release- New: accepted directx-headers [armhf] (hirsute-proposed) [1.0.2-0ubuntu1] [10:09] -queuebot:#ubuntu-release- New: accepted directx-headers [riscv64] (hirsute-proposed) [1.0.2-0ubuntu1] [10:09] -queuebot:#ubuntu-release- New: accepted directx-headers [amd64] (hirsute-proposed) [1.0.2-1] [10:09] -queuebot:#ubuntu-release- New: accepted directx-headers [armhf] (hirsute-proposed) [1.0.2-1] [10:09] -queuebot:#ubuntu-release- New: accepted directx-headers [riscv64] (hirsute-proposed) [1.0.2-1] [10:09] -queuebot:#ubuntu-release- New: accepted directx-headers [arm64] (hirsute-proposed) [1.0.2-0ubuntu1] [10:09] -queuebot:#ubuntu-release- New: accepted directx-headers [s390x] (hirsute-proposed) [1.0.2-0ubuntu1] [10:09] -queuebot:#ubuntu-release- New: accepted directx-headers [ppc64el] (hirsute-proposed) [1.0.2-1] [10:09] -queuebot:#ubuntu-release- New: accepted directx-headers [ppc64el] (hirsute-proposed) [1.0.2-0ubuntu1] [10:09] -queuebot:#ubuntu-release- New: accepted directx-headers [s390x] (hirsute-proposed) [1.0.2-1] [10:09] -queuebot:#ubuntu-release- New: accepted directx-headers [arm64] (hirsute-proposed) [1.0.2-1] [11:13] Laney: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt grub2 & grub2-signed migrated in hirsute, without grub2-unsigned causing havoc. [11:14] and i don't understand how or why britney do that, as that is very broken. [11:14] Britney also says Depends: grub2 grub2-unsigned in update_excuses [11:14] what should have prevented it in your opinion? [11:16] grub2 depends on grub2-unsigned [11:16] vorlon, see LP: #1867338 [11:16] Launchpad bug 1867338 in kerneloops (Ubuntu) "Is kerneloops still useful on Ubuntu?" [Undecided,New] https://launchpad.net/bugs/1867338 [11:16] or did I read that wrong way around? [11:16] certainly causes me to switch from grub-efi-* to grub-pc [11:17] secondly [11:17] that update_output.txt says that grub2-unsigned was taken with the set [11:18] juliank: Laney: i think just bad timing? [11:18] https://people.canonical.com/~ubuntu-archive/proposed-migration/log/hirsute/2021-03-03/06:22:51.log [11:18] Copying: grub2/2.04-1ubuntu42 [11:18] Copying: grub2-signed/1.164 [11:18] has [11:18] Copying: grub2-unsigned/2.04-1ubuntu42 [11:18] yeap that [11:19] https://launchpad.net/ubuntu/+source/grub2-unsigned/+publishinghistory [11:19] deleted but not published in release [11:19] what [11:19] but i see no pending there [11:19] Laney: please use AA powers to copy into release suite [11:19] launchpad had a hickup? :D [11:19] thanks I will, you're like one step behind me [11:19] this is a matter for #launchpad to look into [11:20] Probably a copy failure. We should fix this by making the promotion arrangements use the newish "move" facility rather than copy-then-delete [11:21] [2021-03-03 08:53:53,220: DEBUG/ForkPoolWorker-1] Rejected: [11:21] [2021-03-03 08:53:53,220: DEBUG/ForkPoolWorker-1] grub2-unsigned 2.04-1ubuntu42 in hirsute (binaries conflicting with the existing ones) [11:21] cjwatson: is that more immune to failures or would we still have had a partial set, just without the deletion from proposed? [11:22] It means that if it fails the result will still be published in -proposed rather than just vanishing [11:22] kind of needs an atomic move of multiple thingies [11:22] You aren't going to get that though [11:22] move all or nothing :) [11:22] The copier is already awful [11:23] But you *can* have an atomic move of one thing [11:23] not enough acid for me [11:23] So how about not letting the perfect be the enemy of the good [11:23] * Laney makes a sad face [11:23] I was just wondering if it would have avoided the breakage hirsute users are seeing, we should still use it of course [11:24] i think it would have been okish if britney requested things in reverse order. [11:24] I'm not sure what's going on with this one. Binary conflicts maybe due to something about i386? [11:24] i.e. it knows that grub2 has depends on grub2-unsigned and implicit on grub2-signed. it could have copied grub2-unsigned, grub2-signed, then grub2. [11:24] Might need a wgrant consult [11:24] -queuebot:#ubuntu-release- New sync: grub2-unsigned (hirsute-release/primary) [2.04-1ubuntu42] [11:25] cjwatson: the same source and binaries got copied down to bionic, built i386 record there, and copied further down to xenial (trusty-esm). So yes the source has i386 build record that is not to be published in hirsute. [11:25] xnox: Even with move=True, the move would still be asynchronous so the copyPackage caller doesn't necessarily get an error [11:25] is that a good thing to accept? [11:25] ah [11:25] So I don't think reverse order helps [11:26] naive xnox [11:27] I suspect that is going to fail again once approved, but we'll see [11:27] maybe i should have kept building grub-efi-amd64:i386 out of src:grub2 on bionic down. =/ [11:27] then src:grub2-unsigned would not have had i386 build [11:28] i guess the copy needs to be done with arches specified explicitely, i.e. we only want amd64 & arm64 in hirsute-release. [11:28] * xnox has no idea if that makes sense [11:28] It doesn't [11:29] I have not had enough coffee (ever) to be confident about working out this particular bit of copier behaviour [11:29] Yeah looks like that accept disappeared [11:29] -queuebot:#ubuntu-release- New: rejected grub2-unsigned [sync] (hirsute-release) [2.04-1ubuntu42] [11:29] lies [11:30] Same error [11:31] You may need a separate build for now [11:32] cjwatson: Laney: can you please back out grub2 & grub2-signed out of release, back into proposed? and put the old one in (ubuntu40 based) [11:32] * cjwatson is not going to do that FWIW [11:33] (not because I object, but because you can either have me working out copier bugs or doing archive surgery but not both) [11:33] I wonder if the issuperset check in the copier needs to be adjusted a bit to take the target series's architecture set into account [11:33] separate build means building three source packages. And this time i will drop building grub-efi-amd64:i386 so will take time. [11:34] Even if I can figure out the copier bug that would still be faster than me fixing it :)( [11:34] :) [11:35] Laney: can you please demote-to-proposed grub2 & grub2-signed? [11:36] i will prepare new i386-less builds [11:38] yes, you don't need to repeatedly ask :-) [11:38] and you definitely don't mean demote-to-proposed, that means remove from release :p [11:38] can you file a block-proposed bug or something so they don't accidentally get copied back again? [11:41] tags added on https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536 [11:41] Ubuntu bug 1915536 in grub2-signed (Ubuntu Groovy) "one grub" [Undecided,Fix committed] [11:45] xnox: done, can you check the publishing history please to see if it looks ok? [11:45] I didn't copy back to proposed fwiw [11:47] Could somebody file a Launchpad bug about the copy issue please? I *think* the copier needs to be extended to take architecture filters into account - if createMissingBuilds isn't going to create builds for an architecture, then the check for whether conflicting builds would be created should also exclude that architecture [11:48] Laney: you are amazing, it looks beautiful. [11:49] cjwatson: i will file the bug report. [11:50] I wonder if we could arrange for ubuntu-archive-robot's mail to go somewhere [11:51] we would have been at least theoretically able to see the reject then [11:51] get IS to create a non-janky email address for it and I'd be happy to reconfigure it [11:51] ah [11:51] https://launchpad.net/~ubuntu-archive-robot I see the destination now :-) [11:51] it was easy at the time ... [11:52] xnox: ta [11:54] cjwatson: https://bugs.launchpad.net/launchpad/+bug/1917614 [11:54] Ubuntu bug 1917614 in Launchpad itself "one grub broke copypackage -proposed => release in hirsute with i386 build in bionic" [Undecided,New] [11:55] -queuebot:#ubuntu-release- New binary: rust-serial-test [amd64] (hirsute-proposed/universe) [0.5.1-1] (no packageset) [11:55] should I ask for a mailing list or just for it to forward to a list of people? [11:55] ubuntu-archive ^- opinions on where to send ~ubuntu-archive-robot's Launchpad mail? [11:56] -queuebot:#ubuntu-release- New binary: rust-serial-test [ppc64el] (hirsute-proposed/universe) [0.5.1-1] (no packageset) [11:56] -queuebot:#ubuntu-release- New binary: rust-serial-test [s390x] (hirsute-proposed/universe) [0.5.1-1] (no packageset) [11:56] Laney, i don't think we have a list if that helps; likely it should go to those who can access its host [11:56] Laney, what sort of emails is the robot getting? [11:56] (copy failures I assume) [11:56] not sure, but at least the output of copying packages to the release pocket [11:56] there are buildd mailing lists but i think that's full of spam. [11:57] -queuebot:#ubuntu-release- New binary: rust-serial-test [armhf] (hirsute-proposed/universe) [0.5.1-1] (no packageset) [11:57] sorry i mean ftbfs [11:57] but likely a bunch of positive copies too [11:57] I'm guessing most of you won't want to see most of it [11:57] I'm subscribed to all fbfs mails ;p [11:57] I would probably /dev/null anything that's not a reject [11:57] unless it turns out there's something else interesting in there [11:58] -queuebot:#ubuntu-release- New binary: rust-serial-test [arm64] (hirsute-proposed/universe) [0.5.1-1] (no packageset) [11:58] basically wondering if you want to be able to opt in via a list orrrrr opt in via an RT ticket [11:58] not sure there's anything particularly secret in there but if there is the list archives could be private [11:58] that feels easiest to me [11:59] feel free to throw me on the list [12:00] i am used to a firehose of lauchpad emails, and having to sort them for useful things [12:00] I guess there's already https://lists.ubuntu.com/archives/ubuntu-archive/ [12:03] Having it just be an alias for ubuntu-archive@lists doesn't seem awful [12:03] Nothing sensitive in the output in your experience? [12:03] if not, let's do that then [12:04] Hm [12:04] Two problems that maybe interact badly: ubuntu-archive@lists is moderated and ~ubuntu-archive-robot gets a lot of mail; and it would be bad practice to allow ~ubuntu-archive-robot's email to go to a public list without moderation because there are probably ways that could be used to do bad things to the account [12:05] How about a new internal-only mailing list maybe? [12:05] Alright [12:06] Reading /home/cjwatson/mail/ubuntu/archive-robot... 24408/397994 (6%) [12:06] Not sure I've ever archived anything from that :) [12:07] (if it's a new mailing list, though, it needs to be configured to allow mails from LP without moderation. I can probably provide headers if need be) [12:09] Looking at this, I think just adding archive@ubuntu.com and noreply@launchpad.net to the permitted senders list would work fine [12:11] * Laney nods [12:18] ok, request sent [12:18] -queuebot:#ubuntu-release- New binary: rust-serial-test [riscv64] (hirsute-proposed/universe) [0.5.1-1] (no packageset) [12:26] -queuebot:#ubuntu-release- New binary: linux-signed-kvm [amd64] (hirsute-proposed/main) [5.8.0-1020.22+21.04.1] (core) [12:27] -queuebot:#ubuntu-release- New: accepted rust-serial-test [amd64] (hirsute-proposed) [0.5.1-1] [12:27] -queuebot:#ubuntu-release- New: accepted rust-serial-test [armhf] (hirsute-proposed) [0.5.1-1] [12:27] -queuebot:#ubuntu-release- New: accepted rust-serial-test [riscv64] (hirsute-proposed) [0.5.1-1] [12:27] -queuebot:#ubuntu-release- New: accepted rust-serial-test [arm64] (hirsute-proposed) [0.5.1-1] [12:27] -queuebot:#ubuntu-release- New: accepted rust-serial-test [s390x] (hirsute-proposed) [0.5.1-1] [12:27] -queuebot:#ubuntu-release- New: accepted rust-serial-test [ppc64el] (hirsute-proposed) [0.5.1-1] [12:56] Laney: can you please remove i386 binaries of src:grub2-unsigned in bionic-proposed xenial-proposed trusty-proposed? the grub-efi-amd64:i386 grub-efi-amd64-bin:i386 grub-efi-amd64-dbg:i386 ? as those will have to go back to 2.02 based versions from src:grub2 [13:03] xnox: I'm going to lunch now but I'd prefer you work with vorlon or someone who knows this better than I do if you don't mind. I don't feel super comfortable given that I'm coming to this kind of cold [13:33] ok [13:34] i will have all that staged in a ppa, to ensure all the things are right, and will upload into the archive. [13:34] and then will ask for vorlon to accept. [14:06] -queuebot:#ubuntu-release- Unapproved: accepted xsane [source] (focal-proposed) [0.999-8ubuntu2.1] [14:26] -queuebot:#ubuntu-release- New: accepted linux-signed-kvm [amd64] (hirsute-proposed) [5.8.0-1020.22+21.04.1] [14:42] -queuebot:#ubuntu-release- Unapproved: neutron (bionic-proposed/main) [2:12.1.1-0ubuntu3 => 2:12.1.1-0ubuntu4] (openstack, ubuntu-server) [14:45] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.23 => 2.02-2ubuntu8.24] (core) [14:45] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.31 => 2.02~beta2-36ubuntu3.32] (core) [14:45] -queuebot:#ubuntu-release- Unapproved: grub2 (trusty-proposed/main) [2.02~beta2-9ubuntu1.17 => 2.02~beta2-9ubuntu1.23] (core) [14:46] -queuebot:#ubuntu-release- New source: grub2-unsigned (hirsute-proposed/primary) [2.04-1ubuntu43] [14:47] vorlon: ^^^^ [14:47] i guess trusty is not needed in primary, so please reject that one. [14:53] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (trusty-proposed) [2.02~beta2-9ubuntu1.23] [14:53] xnox, ^ [15:02] mmm a proposed-migration log is now 45MB... [15:02] https://people.canonical.com/~ubuntu-archive/proposed-migration/log/hirsute/2021-03-03/ [15:05] apw: tah. [15:59] -queuebot:#ubuntu-release- Unapproved: openvpn (groovy-proposed/main) [2.4.9-3ubuntu1 => 2.5.1-1ubuntu1] (ubuntu-desktop, ubuntu-server) [16:12] -queuebot:#ubuntu-release- Unapproved: accepted google-osconfig-agent [source] (groovy-proposed) [20210219.00-0ubuntu1~20.10.0] [16:13] -queuebot:#ubuntu-release- New: accepted grub2-unsigned [source] (hirsute-proposed) [2.04-1ubuntu43] [16:13] -queuebot:#ubuntu-release- Unapproved: rejected openvpn [source] (groovy-proposed) [2.5.1-1ubuntu1] [16:14] rbalint: ah, so a MoM bug that a package removed from Debian still shows up in the merge list. So you want me to remove kerneloops from Ubuntu as well? ubuntu-archive wasn't subscribed to that bug [16:16] -queuebot:#ubuntu-release- Unapproved: accepted google-osconfig-agent [source] (focal-proposed) [20210219.00-0ubuntu1~20.04.0] [16:23] -queuebot:#ubuntu-release- Unapproved: accepted google-osconfig-agent [source] (bionic-proposed) [20210219.00-0ubuntu1~18.04.0] [16:23] -queuebot:#ubuntu-release- Unapproved: systemd (groovy-proposed/main) [246.6-1ubuntu1.1 => 246.6-1ubuntu1.2] (core, i386-whitelist) [16:24] xnox: why would we move grub-efi-amd64-bin:i386 back to src:grub2 instead of adding grub2-unsigned to the i386 build whitelist? [16:26] -queuebot:#ubuntu-release- Unapproved: systemd (focal-proposed/main) [245.4-4ubuntu3.4 => 245.4-4ubuntu3.5] (core, i386-whitelist) [16:28] vorlon, ideally i'd like to hear kernel team's opinion [16:29] -queuebot:#ubuntu-release- Unapproved: systemd (bionic-proposed/main) [237-3ubuntu10.44 => 237-3ubuntu10.45] (core) [16:29] apw, should kerneloops be dropped? [16:31] thanks [16:31] -queuebot:#ubuntu-release- Unapproved: grub2-unsigned (hirsute-proposed/none) [none => 2.04-1ubuntu43] (no packageset) [16:31] I realize now this has shown up in the process-removals list and I've been ignoring it for a while because of the Ubuntu delta :) [16:33] vorlon, definitely not merge material :-) [16:41] -queuebot:#ubuntu-release- New binary: rust-cargo-outdated [amd64] (hirsute-proposed/universe) [0.9.9-1ubuntu1] (no packageset) [16:43] -queuebot:#ubuntu-release- New binary: rust-cargo-outdated [s390x] (hirsute-proposed/universe) [0.9.9-1ubuntu1] (no packageset) [16:44] -queuebot:#ubuntu-release- New binary: rust-cargo-outdated [ppc64el] (hirsute-proposed/universe) [0.9.9-1ubuntu1] (no packageset) [16:46] vorlon: i can try that, please stand by. [16:48] -queuebot:#ubuntu-release- New binary: rust-cargo-outdated [arm64] (hirsute-proposed/universe) [0.9.9-1ubuntu1] (no packageset) [16:49] -queuebot:#ubuntu-release- New binary: rust-cargo-outdated [armhf] (hirsute-proposed/universe) [0.9.9-1ubuntu1] (no packageset) [16:51] -queuebot:#ubuntu-release- Unapproved: grub2-unsigned (hirsute-proposed/main) [2.04-1ubuntu43 => 2.04-1ubuntu43] (no packageset) [17:05] -queuebot:#ubuntu-release- New binary: rust-cpp-macros [ppc64el] (hirsute-proposed/universe) [0.5.6-1ubuntu1] (no packageset) [17:05] -queuebot:#ubuntu-release- New binary: rust-cpp-macros [s390x] (hirsute-proposed/universe) [0.5.6-1ubuntu1] (no packageset) [17:07] -queuebot:#ubuntu-release- New binary: rust-cpp-macros [amd64] (hirsute-proposed/universe) [0.5.6-1ubuntu1] (no packageset) [17:07] -queuebot:#ubuntu-release- New binary: rust-cpp-macros [arm64] (hirsute-proposed/universe) [0.5.6-1ubuntu1] (no packageset) [17:07] -queuebot:#ubuntu-release- New binary: rust-cpp-macros [armhf] (hirsute-proposed/universe) [0.5.6-1ubuntu1] (no packageset) [17:15] xnox: expedited adding grub2-unsigned to the whitelist so that the next hirsute upload will build on i386 without any further futzing [17:16] xnox: will I need to add grub2 to the whitelist as well? if I don't will we have i386 binaries from grub2-unsigned with unsatisfiable deps that will make britney sad? [17:23] -queuebot:#ubuntu-release- New binary: rust-cpp-macros [riscv64] (hirsute-proposed/universe) [0.5.6-1ubuntu1] (no packageset) [17:43] -queuebot:#ubuntu-release- Packageset: Added grub2-unsigned to i386-whitelist in hirsute [17:51] vorlon, [17:51] autopkgtest for rust-glib/0.8.2-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻ [17:51] autopkgtest for rust-onig/blacklisted: amd64: Not a regression, arm64: Not a regression, armhf: Regression ♻ , ppc64el: Not a regression, s390x: Not a regression [17:51] is it possible to hint them two? rust-onig is already blacklisted, I don't get why it complains on armhf [17:51] and rust-glib fails also in Debian... [17:55] also please kick rust-sha-1 out from release pocket, its buggy in Debian too and holding back rust migration [17:56] I think with 2 hints and one demotion to proposed we can see ~40 packages migrate [18:32] -queuebot:#ubuntu-release- New: accepted rust-cargo-outdated [amd64] (hirsute-proposed) [0.9.9-1ubuntu1] [18:32] -queuebot:#ubuntu-release- New: accepted rust-cargo-outdated [armhf] (hirsute-proposed) [0.9.9-1ubuntu1] [18:32] -queuebot:#ubuntu-release- New: accepted rust-cargo-outdated [s390x] (hirsute-proposed) [0.9.9-1ubuntu1] [18:32] -queuebot:#ubuntu-release- New: accepted rust-cpp-macros [arm64] (hirsute-proposed) [0.5.6-1ubuntu1] [18:32] -queuebot:#ubuntu-release- New: accepted rust-cpp-macros [ppc64el] (hirsute-proposed) [0.5.6-1ubuntu1] [18:32] -queuebot:#ubuntu-release- New: accepted rust-cpp-macros [s390x] (hirsute-proposed) [0.5.6-1ubuntu1] [18:32] -queuebot:#ubuntu-release- New: accepted rust-cargo-outdated [arm64] (hirsute-proposed) [0.9.9-1ubuntu1] [18:32] -queuebot:#ubuntu-release- New: accepted rust-cpp-macros [amd64] (hirsute-proposed) [0.5.6-1ubuntu1] [18:32] -queuebot:#ubuntu-release- New: accepted rust-cpp-macros [riscv64] (hirsute-proposed) [0.5.6-1ubuntu1] [18:32] -queuebot:#ubuntu-release- New: accepted rust-cargo-outdated [ppc64el] (hirsute-proposed) [0.9.9-1ubuntu1] [18:32] -queuebot:#ubuntu-release- New binary: rust-cargo-outdated [riscv64] (hirsute-proposed/universe) [0.9.9-1ubuntu1] (no packageset) [18:32] -queuebot:#ubuntu-release- New: accepted rust-cpp-macros [armhf] (hirsute-proposed) [0.5.6-1ubuntu1] [18:32] -queuebot:#ubuntu-release- New: accepted rust-cargo-outdated [riscv64] (hirsute-proposed) [0.9.9-1ubuntu1] [18:48] slyon, will you post patches to the respective debian bugs ^^ ? === ijohnson is now known as ijohnson|lunch [19:09] LocutusOfBorg: why did Debian allow rust-glib autopkgtests to regress in testing? [19:10] who knows... its... rust [19:11] maybe transitions and uninstallabilities makes tracking it hard [19:11] LocutusOfBorg: rust-onig, had a successful test run on armhf of 6.1.0-1 previously and is now blacklisted. Does it need to be blacklisted there? [19:12] force-test-reset on armhf maybe? [19:12] if the test is blacklisted should it be reset anyway? [19:12] ok Laney blacklisted it for sensible reasons that apply to armhf on lxd also even if they don't necessarily cause rust-onig's own tests to fail [19:13] (they would just make *other* tests fail on the same lxd host by consuming all the shared disk :P) [19:13] ok but how can an blacklisted test ever run successfully? [19:13] oh but also https://bugs.debian.org/973657 is fixed [19:13] Debian bug 973657 in src:rust-onig "src:rust-onig: autopkgtest uses enormous amount (> 25 GB) of disk space" [Important,Fixed] [19:13] a blacklisted test can't run successfully, it ran successfully before the blacklist was added [19:13] anyway we should just remove the blacklist for this one now [19:16] vorlon, this doesn't explain what I see on excuses [19:16] autopkgtest for rust-onig/blacklisted: amd64: Not a regression, arm64: Not a regression, armhf: Regression ♻ , ppc64el: Not a regression, s390x: Not a regression [19:16] on armhf its shown as regressed [19:17] LocutusOfBorg: it does explain. It's regressed because the test previously *succeeded* on armhf due to the lxd host having enough disk space to accommodate; and then it was blacklisted; so all subsequent test requests from britney for this package get returned with version 'blacklisted', as a failure, with the test never run [19:17] ok but if a package is blacklisted, shouldn't previous passes just be discarded? [19:17] anyway if you unblacklist even better [19:18] that's not how it's implemented [19:18] ack :) [19:19] maybe can you please do also something for rust-sha-1? [19:22] still working through the others [19:22] thanks, I admit I can't understand if the blacklist/hint/sha-1 are the only blockers [19:22] I need some britney run before figuring out if something else is missing :) [19:25] rust-onig unblacklisted, tests retriggered [19:27] LocutusOfBorg: yes, I'll submittodebian tomorrow [19:27] thanks [19:28] -queuebot:#ubuntu-release- Packageset: Added grub2 to i386-whitelist in hirsute [19:28] I have some more of those in the pipeline [19:28] slyon, if you need somebody to NMU them let me know [19:29] you sumbit, we wait 10 days, we NMU, we sync, we profit [19:29] Sounds like a plan! [19:31] :) === ijohnson|lunch is now known as ijohnson [23:19] -queuebot:#ubuntu-release- New binary: qiskit-aer [riscv64] (hirsute-proposed/universe) [0.4.1-1build1] (no packageset) [23:35] -queuebot:#ubuntu-release- Unapproved: accepted grub2-unsigned [amd64] (hirsute-proposed) [2.04-1ubuntu43] [23:35] -queuebot:#ubuntu-release- Unapproved: accepted grub2-unsigned [arm64] (hirsute-proposed) [2.04-1ubuntu43]