/srv/irclogs.ubuntu.com/2021/03/03/#ubuntu-release.txt

-queuebot:#ubuntu-release- New: accepted directx-headers [source] (hirsute-proposed) [1.0.2-0ubuntu1]00:31
-queuebot:#ubuntu-release- New binary: directx-headers [s390x] (hirsute-proposed/none) [1.0.2-0ubuntu1] (no packageset)00:34
-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:35
-queuebot:#ubuntu-release- New binary: directx-headers [amd64] (hirsute-proposed/none) [1.0.2-0ubuntu1] (no packageset)00:36
-queuebot:#ubuntu-release- New binary: directx-headers [riscv64] (hirsute-proposed/universe) [1.0.2-0ubuntu1] (no packageset)00:54
xnoxvorlon: well I guess I want this grub to migrate in hirsute before uploading armhf fixes, packaging fixes, ppc64el patches....01:30
-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]01:53
-queuebot:#ubuntu-release- Unapproved: accepted west-chamber [source] (focal-proposed) [20100405+svn20111107.r124-12ubuntu0.2~20.04.1]02:10
tjaaltonRAOF: thanks! looks like it got accepted to debian too, that was quick ;)04:20
RAOFtjaalton: you might want to change the licence to “Expat” (because it's that flavour of MIT) but that wasn't blocking 😀04:22
tjaaltonah ok, committed to git :)04:36
-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:46
-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)04:47
-queuebot:#ubuntu-release- New binary: directx-headers [riscv64] (hirsute-proposed/universe) [1.0.2-1] (no packageset)05:07
=== didrocks2 is now known as didrocks
-queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (hirsute-proposed) [5.8.0-1024.26+21.04.1]09:21
-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]10:09
xnoxLaney: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt grub2 & grub2-signed migrated in hirsute, without grub2-unsigned causing havoc.11:13
xnoxand i don't understand how or why britney do that, as that is very broken.11:14
juliankBritney also says Depends: grub2 grub2-unsigned in update_excuses11:14
Laneywhat should have prevented it in your opinion?11:14
juliankgrub2 depends on grub2-unsigned11:16
rbalintvorlon, see LP: #186733811:16
ubot5Launchpad bug 1867338 in kerneloops (Ubuntu) "Is kerneloops still useful on Ubuntu?" [Undecided,New] https://launchpad.net/bugs/186733811:16
juliankor did I read that wrong way around?11:16
juliankcertainly causes me to switch from grub-efi-* to grub-pc11:16
Laneysecondly11:17
Laneythat update_output.txt says that grub2-unsigned was taken with the set11:17
xnoxjuliank:  Laney: i think just bad timing?11:18
xnoxhttps://people.canonical.com/~ubuntu-archive/proposed-migration/log/hirsute/2021-03-03/06:22:51.log11:18
LaneyCopying: grub2/2.04-1ubuntu4211:18
LaneyCopying: grub2-signed/1.16411:18
xnoxhas11:18
LaneyCopying: grub2-unsigned/2.04-1ubuntu4211:18
xnoxyeap that11:18
Laneyhttps://launchpad.net/ubuntu/+source/grub2-unsigned/+publishinghistory11:19
Laneydeleted but not published in release11:19
Laneywhat11:19
xnoxbut i see no pending there11:19
xnoxLaney:  please use AA powers to copy into release suite11:19
julianklaunchpad had a hickup? :D11:19
Laneythanks I will, you're like one step behind me11:19
Laneythis is a matter for #launchpad to look into11:19
cjwatsonProbably a copy failure.  We should fix this by making the promotion arrangements use the newish "move" facility rather than copy-then-delete11:20
cjwatson[2021-03-03 08:53:53,220: DEBUG/ForkPoolWorker-1] Rejected:11:21
cjwatson[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
Laneycjwatson: is that more immune to failures or would we still have had a partial set, just without the deletion from proposed?11:21
cjwatsonIt means that if it fails the result will still be published in -proposed rather than just vanishing11:22
juliankkind of needs an atomic move of multiple thingies11:22
cjwatsonYou aren't going to get that though11:22
juliankmove all or nothing :)11:22
cjwatsonThe copier is already awful11:22
cjwatsonBut you *can* have an atomic move of one thing11:23
julianknot enough acid for me11:23
cjwatsonSo how about not letting the perfect be the enemy of the good11:23
* Laney makes a sad face11:23
LaneyI was just wondering if it would have avoided the breakage hirsute users are seeing, we should still use it of course11:23
xnoxi think it would have been okish if britney requested things in reverse order.11:24
cjwatsonI'm not sure what's going on with this one.  Binary conflicts maybe due to something about i386?11:24
xnoxi.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
cjwatsonMight need a wgrant consult11:24
-queuebot:#ubuntu-release- New sync: grub2-unsigned (hirsute-release/primary) [2.04-1ubuntu42]11:24
xnoxcjwatson:  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
cjwatsonxnox: Even with move=True, the move would still be asynchronous so the copyPackage caller doesn't necessarily get an error11:25
Laneyis that a good thing to accept?11:25
xnoxah11:25
cjwatsonSo I don't think reverse order helps11:25
xnoxnaive xnox11:26
cjwatsonI suspect that is going to fail again once approved, but we'll see11:27
xnoxmaybe i should have kept building grub-efi-amd64:i386 out of src:grub2 on bionic down. =/11:27
xnoxthen src:grub2-unsigned would not have had i386 build11:27
xnoxi 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 sense11:28
cjwatsonIt doesn't11:28
cjwatsonI have not had enough coffee (ever) to be confident about working out this particular bit of copier behaviour11:29
LaneyYeah looks like that accept disappeared11:29
-queuebot:#ubuntu-release- New: rejected grub2-unsigned [sync] (hirsute-release) [2.04-1ubuntu42]11:29
Laneylies11:29
cjwatsonSame error11:30
cjwatsonYou may need a separate build for now11:31
xnoxcjwatson:  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 FWIW11:32
cjwatson(not because I object, but because you can either have me working out copier bugs or doing archive surgery but not both)11:33
cjwatsonI wonder if the issuperset check in the copier needs to be adjusted a bit to take the target series's architecture set into account11:33
xnoxseparate build means building three source packages. And this time i will drop building grub-efi-amd64:i386 so will take time.11:33
cjwatsonEven if I can figure out the copier bug that would still be faster than me fixing it :)(11:34
cjwatson:)11:34
xnoxLaney:  can you please demote-to-proposed grub2 & grub2-signed?11:35
xnoxi will prepare new i386-less builds11:36
Laneyyes, you don't need to repeatedly ask :-)11:38
Laneyand you definitely don't mean demote-to-proposed, that means remove from release :p11:38
Laneycan you file a block-proposed bug or something so they don't accidentally get copied back again?11:38
xnoxtags added on https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/191553611:41
ubot5Ubuntu bug 1915536 in grub2-signed (Ubuntu Groovy) "one grub" [Undecided,Fix committed]11:41
Laneyxnox: done, can you check the publishing history please to see if it looks ok?11:45
LaneyI didn't copy back to proposed fwiw11:45
cjwatsonCould 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 architecture11:47
xnoxLaney:  you are amazing, it looks beautiful.11:48
xnoxcjwatson:  i will file the bug report.11:49
LaneyI wonder if we could arrange for ubuntu-archive-robot's mail to go somewhere11:50
Laneywe would have been at least theoretically able to see the reject then11:51
cjwatsonget IS to create a non-janky email address for it and I'd be happy to reconfigure it11:51
Laneyah11:51
Laneyhttps://launchpad.net/~ubuntu-archive-robot I see the destination now :-)11:51
cjwatsonit was easy at the time ...11:51
cjwatsonxnox: ta11:52
xnoxcjwatson:  https://bugs.launchpad.net/launchpad/+bug/191761411:54
ubot5Ubuntu bug 1917614 in Launchpad itself "one grub broke copypackage -proposed => release in hirsute with i386 build in bionic" [Undecided,New]11:54
-queuebot:#ubuntu-release- New binary: rust-serial-test [amd64] (hirsute-proposed/universe) [0.5.1-1] (no packageset)11:55
Laneyshould I ask for a mailing list or just for it to forward to a list of people?11:55
Laneyubuntu-archive ^- opinions on where to send ~ubuntu-archive-robot's Launchpad mail?11:55
-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
apwLaney, i don't think we have a list if that helps; likely it should go to those who can access its host11:56
seb128Laney, what sort of emails is the robot getting?11:56
apw(copy failures I assume)11:56
Laneynot sure, but at least the output of copying packages to the release pocket11:56
xnoxthere are buildd mailing lists but i think that's full of spam.11:56
-queuebot:#ubuntu-release- New binary: rust-serial-test [armhf] (hirsute-proposed/universe) [0.5.1-1] (no packageset)11:57
xnoxsorry i mean ftbfs11:57
apwbut likely a bunch of positive copies too11:57
LaneyI'm guessing most of you won't want to see most of it11:57
dokoI'm subscribed to all fbfs mails ;p11:57
LaneyI would probably /dev/null anything that's not a reject11:57
Laneyunless it turns out there's something else interesting in there11:57
-queuebot:#ubuntu-release- New binary: rust-serial-test [arm64] (hirsute-proposed/universe) [0.5.1-1] (no packageset)11:58
Laneybasically wondering if you want to be able to opt in via a list orrrrr opt in via an RT ticket11:58
Laneynot sure there's anything particularly secret in there but if there is the list archives could be private11:58
Laneythat feels easiest to me11:58
apwfeel free to throw me on the list11:59
apwi am used to a firehose of lauchpad emails, and having to sort them for useful things12:00
LaneyI guess there's already https://lists.ubuntu.com/archives/ubuntu-archive/12:00
cjwatsonHaving it just be an alias for ubuntu-archive@lists doesn't seem awful12:03
LaneyNothing sensitive in the output in your experience?12:03
Laneyif not, let's do that then12:03
cjwatsonHm12:04
cjwatsonTwo 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 account12:04
cjwatsonHow about a new internal-only mailing list maybe?12:05
LaneyAlright12:05
cjwatsonReading /home/cjwatson/mail/ubuntu/archive-robot... 24408/397994 (6%)12:06
cjwatsonNot sure I've ever archived anything from that :)12:06
cjwatson(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:07
cjwatsonLooking at this, I think just adding archive@ubuntu.com and noreply@launchpad.net to the permitted senders list would work fine12:09
* Laney nods12:11
Laneyok, request sent12:18
-queuebot:#ubuntu-release- New binary: rust-serial-test [riscv64] (hirsute-proposed/universe) [0.5.1-1] (no packageset)12:18
-queuebot:#ubuntu-release- New binary: linux-signed-kvm [amd64] (hirsute-proposed/main) [5.8.0-1020.22+21.04.1] (core)12:26
-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:27
xnoxLaney:  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:grub212:56
Laneyxnox: 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 cold13:03
xnoxok13:33
xnoxi will have all that staged in a ppa, to ensure all the things are right, and will upload into the archive.13:34
xnoxand then will ask for vorlon to accept.13:34
-queuebot:#ubuntu-release- Unapproved: accepted xsane [source] (focal-proposed) [0.999-8ubuntu2.1]14:06
-queuebot:#ubuntu-release- New: accepted linux-signed-kvm [amd64] (hirsute-proposed) [5.8.0-1020.22+21.04.1]14:26
-queuebot:#ubuntu-release- Unapproved: neutron (bionic-proposed/main) [2:12.1.1-0ubuntu3 => 2:12.1.1-0ubuntu4] (openstack, ubuntu-server)14:42
-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:45
-queuebot:#ubuntu-release- New source: grub2-unsigned (hirsute-proposed/primary) [2.04-1ubuntu43]14:46
xnoxvorlon:  ^^^^14:47
xnoxi guess trusty is not needed in primary, so please reject that one.14:47
-queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (trusty-proposed) [2.02~beta2-9ubuntu1.23]14:53
apwxnox, ^14:53
LocutusOfBorgmmm a proposed-migration log is now 45MB...15:02
LocutusOfBorghttps://people.canonical.com/~ubuntu-archive/proposed-migration/log/hirsute/2021-03-03/15:02
xnoxapw:  tah.15:05
-queuebot:#ubuntu-release- Unapproved: openvpn (groovy-proposed/main) [2.4.9-3ubuntu1 => 2.5.1-1ubuntu1] (ubuntu-desktop, ubuntu-server)15:59
-queuebot:#ubuntu-release- Unapproved: accepted google-osconfig-agent [source] (groovy-proposed) [20210219.00-0ubuntu1~20.10.0]16:12
-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:13
vorlonrbalint: 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 bug16:14
-queuebot:#ubuntu-release- Unapproved: accepted google-osconfig-agent [source] (focal-proposed) [20210219.00-0ubuntu1~20.04.0]16:16
-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:23
vorlonxnox: why would we move grub-efi-amd64-bin:i386 back to src:grub2 instead of adding grub2-unsigned to the i386 build whitelist?16:24
-queuebot:#ubuntu-release- Unapproved: systemd (focal-proposed/main) [245.4-4ubuntu3.4 => 245.4-4ubuntu3.5] (core, i386-whitelist)16:26
rbalintvorlon, ideally i'd like to hear kernel team's opinion16:28
-queuebot:#ubuntu-release- Unapproved: systemd (bionic-proposed/main) [237-3ubuntu10.44 => 237-3ubuntu10.45] (core)16:29
rbalintapw, should kerneloops be dropped?16:29
vorlonthanks16:31
-queuebot:#ubuntu-release- Unapproved: grub2-unsigned (hirsute-proposed/none) [none => 2.04-1ubuntu43] (no packageset)16:31
vorlonI 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:31
rbalintvorlon, definitely not merge material :-)16:33
-queuebot:#ubuntu-release- New binary: rust-cargo-outdated [amd64] (hirsute-proposed/universe) [0.9.9-1ubuntu1] (no packageset)16:41
-queuebot:#ubuntu-release- New binary: rust-cargo-outdated [s390x] (hirsute-proposed/universe) [0.9.9-1ubuntu1] (no packageset)16:43
-queuebot:#ubuntu-release- New binary: rust-cargo-outdated [ppc64el] (hirsute-proposed/universe) [0.9.9-1ubuntu1] (no packageset)16:44
xnoxvorlon:  i can try that, please stand by.16:46
-queuebot:#ubuntu-release- New binary: rust-cargo-outdated [arm64] (hirsute-proposed/universe) [0.9.9-1ubuntu1] (no packageset)16:48
-queuebot:#ubuntu-release- New binary: rust-cargo-outdated [armhf] (hirsute-proposed/universe) [0.9.9-1ubuntu1] (no packageset)16:49
-queuebot:#ubuntu-release- Unapproved: grub2-unsigned (hirsute-proposed/main) [2.04-1ubuntu43 => 2.04-1ubuntu43] (no packageset)16:51
-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:05
-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:07
vorlonxnox: expedited adding grub2-unsigned to the whitelist so that the next hirsute upload will build on i386 without any further futzing17:15
vorlonxnox: 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:16
-queuebot:#ubuntu-release- New binary: rust-cpp-macros [riscv64] (hirsute-proposed/universe) [0.5.6-1ubuntu1] (no packageset)17:23
-queuebot:#ubuntu-release- Packageset: Added grub2-unsigned to i386-whitelist in hirsute17:43
LocutusOfBorgvorlon,17:51
LocutusOfBorgautopkgtest for rust-glib/0.8.2-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻17:51
LocutusOfBorgautopkgtest for rust-onig/blacklisted: amd64: Not a regression, arm64: Not a regression, armhf: Regression ♻ , ppc64el: Not a regression, s390x: Not a regression17:51
LocutusOfBorgis it possible to hint them two? rust-onig is already blacklisted, I don't get why it complains on armhf17:51
LocutusOfBorgand rust-glib fails also in Debian...17:51
LocutusOfBorgalso please kick rust-sha-1 out from release pocket, its buggy in Debian too and holding back rust migration17:55
LocutusOfBorgI think with 2 hints and one demotion to proposed we can see ~40 packages migrate17:56
-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:32
LocutusOfBorgslyon, will you post patches to the respective debian bugs ^^ ?18:48
=== ijohnson is now known as ijohnson|lunch
vorlonLocutusOfBorg: why did Debian allow rust-glib autopkgtests to regress in testing?19:09
LocutusOfBorgwho knows... its... rust19:10
LocutusOfBorgmaybe transitions and uninstallabilities makes tracking it hard19:11
vorlonLocutusOfBorg: 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:11
LocutusOfBorgforce-test-reset on armhf maybe?19:12
LocutusOfBorgif the test is blacklisted should it be reset anyway?19:12
vorlonok 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 fail19:12
vorlon(they would just make *other* tests fail on the same lxd host by consuming all the shared disk :P)19:13
LocutusOfBorgok but how can an blacklisted test ever run successfully?19:13
vorlonoh but also https://bugs.debian.org/973657 is fixed19:13
ubot5Debian bug 973657 in src:rust-onig "src:rust-onig: autopkgtest uses enormous amount (> 25 GB) of disk space" [Important,Fixed]19:13
vorlona blacklisted test can't run successfully, it ran successfully before the blacklist was added19:13
vorlonanyway we should just remove the blacklist for this one now19:13
LocutusOfBorgvorlon, this doesn't explain what I see on excuses19:16
LocutusOfBorgautopkgtest for rust-onig/blacklisted: amd64: Not a regression, arm64: Not a regression, armhf: Regression ♻ , ppc64el: Not a regression, s390x: Not a regression19:16
LocutusOfBorgon armhf its shown as regressed19:16
vorlonLocutusOfBorg: 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 run19:17
LocutusOfBorgok but if a package is blacklisted, shouldn't previous passes just be discarded?19:17
LocutusOfBorganyway if you unblacklist even better19:17
vorlonthat's not how it's implemented19:18
LocutusOfBorgack :)19:18
LocutusOfBorgmaybe can you please do also something for rust-sha-1?19:19
vorlonstill working through the others19:22
LocutusOfBorgthanks, I admit I can't understand if the blacklist/hint/sha-1 are the only blockers19:22
LocutusOfBorgI need some britney run before figuring out if something else is missing :)19:22
vorlonrust-onig unblacklisted, tests retriggered19:25
slyonLocutusOfBorg: yes, I'll submittodebian tomorrow19:27
LocutusOfBorgthanks19:27
-queuebot:#ubuntu-release- Packageset: Added grub2 to i386-whitelist in hirsute19:28
slyonI have some more of those in the pipeline19:28
LocutusOfBorgslyon, if you need somebody to NMU them let me know19:28
LocutusOfBorgyou sumbit, we wait 10 days, we NMU, we sync, we profit19:29
slyonSounds like a plan!19:29
LocutusOfBorg:)19:31
=== ijohnson|lunch is now known as ijohnson
-queuebot:#ubuntu-release- New binary: qiskit-aer [riscv64] (hirsute-proposed/universe) [0.4.1-1build1] (no packageset)23:19
-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]23:35

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!