| 2021-03-03 11:54:00 |
Dimitri John Ledkov |
description |
one grub broke copypackage -proposed => release in hirsute with i386 build in bionic
As part of https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536 a src:grub2-unsigned was created that builds grub-efi-amd64 & grub-efi-arm64 packages and submits things for signing in hirsute.
This source package and binaries, got copied back as far as bionic. Where an i386 build record got created to build grub-efi-amd64:i386. And then copied to xenial.
https://launchpad.net/ubuntu/+source/grub2-unsigned/2.04-1ubuntu42
Publishing
Series Pocket Published Component Section
Bionic proposed 16 hours ago main admin
Focal proposed 16 hours ago main admin
Groovy proposed 16 hours ago main admin
Xenial proposed 16 hours ago main admin
Builds
Hirsute: [FULLYBUILT] amd64 [FULLYBUILT] arm64
Bionic: [FULLYBUILT] i386
When britney decided to migrate copy from hirsute-proposed to hirsute-release failed.
On IRC colin says this:
<cjwatson> 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
to mitigate this I'm preparing a new set of uploads that will ensure that src:grub2-unsigned never has any i386 build records. |
one grub broke copypackage -proposed => release in hirsute with i386 build in bionic
As part of https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536 a src:grub2-unsigned was created that builds grub-efi-amd64 & grub-efi-arm64 packages and submits things for signing in hirsute.
This source package and binaries, got copied back as far as bionic. Where an i386 build record got created to build grub-efi-amd64:i386. And then copied to xenial.
https://launchpad.net/ubuntu/+source/grub2-unsigned/2.04-1ubuntu42
Publishing
Series Pocket Published Component Section
Bionic proposed 16 hours ago main admin
Focal proposed 16 hours ago main admin
Groovy proposed 16 hours ago main admin
Xenial proposed 16 hours ago main admin
Builds
Hirsute: [FULLYBUILT] amd64 [FULLYBUILT] arm64
Bionic: [FULLYBUILT] i386
When britney decided to migrate copy from hirsute-proposed to hirsute-release it failed.
On IRC colin says this:
<cjwatson> 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
to mitigate this I'm preparing a new set of uploads that will ensure that src:grub2-unsigned never has any i386 build records. |
|
| 2021-03-03 11:54:27 |
Dimitri John Ledkov |
description |
one grub broke copypackage -proposed => release in hirsute with i386 build in bionic
As part of https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536 a src:grub2-unsigned was created that builds grub-efi-amd64 & grub-efi-arm64 packages and submits things for signing in hirsute.
This source package and binaries, got copied back as far as bionic. Where an i386 build record got created to build grub-efi-amd64:i386. And then copied to xenial.
https://launchpad.net/ubuntu/+source/grub2-unsigned/2.04-1ubuntu42
Publishing
Series Pocket Published Component Section
Bionic proposed 16 hours ago main admin
Focal proposed 16 hours ago main admin
Groovy proposed 16 hours ago main admin
Xenial proposed 16 hours ago main admin
Builds
Hirsute: [FULLYBUILT] amd64 [FULLYBUILT] arm64
Bionic: [FULLYBUILT] i386
When britney decided to migrate copy from hirsute-proposed to hirsute-release it failed.
On IRC colin says this:
<cjwatson> 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
to mitigate this I'm preparing a new set of uploads that will ensure that src:grub2-unsigned never has any i386 build records. |
one grub broke copypackage -proposed => release in hirsute with i386 build in bionic
As part of https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536 a src:grub2-unsigned was created that builds grub-efi-amd64 & grub-efi-arm64 packages and submits things for signing in hirsute.
This source package and binaries, got copied back as far as bionic. Where an i386 build record got created to build grub-efi-amd64:i386. And then copied to xenial.
https://launchpad.net/ubuntu/+source/grub2-unsigned/2.04-1ubuntu42
Publishing
Series Pocket Published Component Section
Bionic proposed 16 hours ago main admin
Focal proposed 16 hours ago main admin
Groovy proposed 16 hours ago main admin
Xenial proposed 16 hours ago main admin
Builds
Hirsute: [FULLYBUILT] amd64 [FULLYBUILT] arm64
Bionic: [FULLYBUILT] i386
When britney decided to migrate copy from hirsute-proposed to hirsute-release it failed.
to mitigate this I'm preparing a new set of uploads that will ensure that src:grub2-unsigned never has any i386 build records.
On IRC colin says this:
<cjwatson> 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 |
|
