| 2021-02-12 17:05:15 |
Dimitri John Ledkov |
bug |
|
|
added bug |
| 2021-02-12 17:14:12 |
Dimitri John Ledkov |
description |
[Impact]
* Currently
[Test Case]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
[Where problems could occur]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance |
[Impact]
* Currently one needs grub-$platform-bin and grub-$platform-signed packages installed together. As first one provides modules, and the later one provides signed .efi images. The two are built from different source packages, and there is a delay of manual reviews before matching signed grub appears.
* The proposal is to rename modules in -bin to be shipped in the $platfrom-unsigned directly.
* And make -signed package ship both modules and signed binaries
* And add dependency from the -bin onto > -signed one, such that grub uses whichever modules match the signed images.
* This allows allows in the future for grub2-signed to pull appropriate grub modules for a given distro. For example, using 2.04 modules & signed images from focal on bionic to gain support for TPM verifies and other EFI platform specific developments without affecting userspace grub tooling.
[Test Case]
* Upgrade to new grub-efi-amd64-bin and grub-efi-amd64-signed packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* The binaries shipped by -signed packages are innert, they are bootloader binaries only. The only compatibility that has to be maintained is within the userspace tooling - specifically maintainer scripts, and file names and locations.
[Other Info]
* See all the bug reports that grub can't be installed or upgraded when people use -proposed. |
|
| 2021-02-12 17:14:18 |
Dimitri John Ledkov |
bug task added |
|
grub2-signed (Ubuntu) |
|
| 2021-02-18 07:36:32 |
Dimitri John Ledkov |
attachment added |
|
one-grub2.diff https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+attachment/5464726/+files/one-grub2.diff |
|
| 2021-02-18 07:36:48 |
Dimitri John Ledkov |
attachment added |
|
one-grub2-signed.diff https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+attachment/5464727/+files/one-grub2-signed.diff |
|
| 2021-02-18 07:48:51 |
Dimitri John Ledkov |
attachment removed |
one-grub2-signed.diff https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+attachment/5464727/+files/one-grub2-signed.diff |
|
|
| 2021-02-18 07:49:03 |
Dimitri John Ledkov |
attachment added |
|
one-grub2-signed.diff https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+attachment/5464728/+files/one-grub2-signed.diff |
|
| 2021-02-18 08:27:00 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2021-02-19 22:35:38 |
Dimitri John Ledkov |
description |
[Impact]
* Currently one needs grub-$platform-bin and grub-$platform-signed packages installed together. As first one provides modules, and the later one provides signed .efi images. The two are built from different source packages, and there is a delay of manual reviews before matching signed grub appears.
* The proposal is to rename modules in -bin to be shipped in the $platfrom-unsigned directly.
* And make -signed package ship both modules and signed binaries
* And add dependency from the -bin onto > -signed one, such that grub uses whichever modules match the signed images.
* This allows allows in the future for grub2-signed to pull appropriate grub modules for a given distro. For example, using 2.04 modules & signed images from focal on bionic to gain support for TPM verifies and other EFI platform specific developments without affecting userspace grub tooling.
[Test Case]
* Upgrade to new grub-efi-amd64-bin and grub-efi-amd64-signed packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* The binaries shipped by -signed packages are innert, they are bootloader binaries only. The only compatibility that has to be maintained is within the userspace tooling - specifically maintainer scripts, and file names and locations.
[Other Info]
* See all the bug reports that grub can't be installed or upgraded when people use -proposed. |
[Impact]
* Currently one needs grub-$platform-bin and grub-$platform-signed packages installed together. As first one provides modules, and the later one provides signed .efi images. The two are built from different source packages, and there is a delay of manual reviews before matching signed grub appears.
* The proposal is to rename modules in -bin to be shipped in the $platfrom-unsigned directly.
* And make -signed-bin package ship modules
* And add dependency from the -bin onto > -signed-bin one
* This allows allows in the future for grub2-signed to pull appropriate grub modules for a given distro. For example, using 2.04 modules & signed images from focal on bionic to gain support for TPM verifies and other EFI platform specific developments without affecting userspace grub tooling.
[Caveats]
* If one chooses to remove or not install grub-efi-*-signed package, then modules keep receiving updates, but no SRUs of grub-efi-amd64/grub-efi-arm64 getting published meaning nothing is upgraded that has a maintainer script to trigger grub-install. This is closer inline with grub-pc which also stopped calling grub-install in the release series. But I feel iffy about this.
but i'm not sure if it is ok to add circular dependency from grub-efi-*-bin back onto grub-efi-amd64/grub-efi-amd64/signed/grub-pc.
almost as if the top level packages should simply have a file trigger on modules directory to trigger upgrade logic to execute grub-install.
also feel iffy about the fact that -signed ships efi apps; -signed-bin ships modules; and -signed-dbg ships debug ones. collapsing them all into one will break the multiarch-foreign constraint on the unsigned -bin packages.
I guess question remains if i should add file-triggers in the grub-pc & grub-efi-arm64|amd64-signed packages.
[Test Case]
* Upgrade to new grub-efi-amd64-bin and grub-efi-amd64-signed packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* The binaries shipped by -signed packages are innert, they are bootloader binaries only. The only compatibility that has to be maintained is within the userspace tooling - specifically maintainer scripts, and file names and locations.
[Other Info]
* See all the bug reports that grub can't be installed or upgraded when people use -proposed. |
|
| 2021-02-19 22:37:03 |
Dimitri John Ledkov |
description |
[Impact]
* Currently one needs grub-$platform-bin and grub-$platform-signed packages installed together. As first one provides modules, and the later one provides signed .efi images. The two are built from different source packages, and there is a delay of manual reviews before matching signed grub appears.
* The proposal is to rename modules in -bin to be shipped in the $platfrom-unsigned directly.
* And make -signed-bin package ship modules
* And add dependency from the -bin onto > -signed-bin one
* This allows allows in the future for grub2-signed to pull appropriate grub modules for a given distro. For example, using 2.04 modules & signed images from focal on bionic to gain support for TPM verifies and other EFI platform specific developments without affecting userspace grub tooling.
[Caveats]
* If one chooses to remove or not install grub-efi-*-signed package, then modules keep receiving updates, but no SRUs of grub-efi-amd64/grub-efi-arm64 getting published meaning nothing is upgraded that has a maintainer script to trigger grub-install. This is closer inline with grub-pc which also stopped calling grub-install in the release series. But I feel iffy about this.
but i'm not sure if it is ok to add circular dependency from grub-efi-*-bin back onto grub-efi-amd64/grub-efi-amd64/signed/grub-pc.
almost as if the top level packages should simply have a file trigger on modules directory to trigger upgrade logic to execute grub-install.
also feel iffy about the fact that -signed ships efi apps; -signed-bin ships modules; and -signed-dbg ships debug ones. collapsing them all into one will break the multiarch-foreign constraint on the unsigned -bin packages.
I guess question remains if i should add file-triggers in the grub-pc & grub-efi-arm64|amd64-signed packages.
[Test Case]
* Upgrade to new grub-efi-amd64-bin and grub-efi-amd64-signed packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* The binaries shipped by -signed packages are innert, they are bootloader binaries only. The only compatibility that has to be maintained is within the userspace tooling - specifically maintainer scripts, and file names and locations.
[Other Info]
* See all the bug reports that grub can't be installed or upgraded when people use -proposed. |
[Impact]
* Currently one needs grub-$platform-bin and grub-$platform-signed packages installed together. As first one provides modules, and the later one provides signed .efi images. The two are built from different source packages, and there is a delay of manual reviews before matching signed grub appears.
* The proposal is to rename modules in -bin to be shipped in the $platfrom-unsigned directly.
* And make -signed-bin package ship modules
* And add dependency from the -bin onto > -signed-bin one
* This allows allows in the future for grub2-signed to pull appropriate grub modules for a given distro. For example, using 2.04 modules & signed images from focal on bionic to gain support for TPM verifies and other EFI platform specific developments without affecting userspace grub tooling.
[Caveats]
* If one chooses to remove or not install grub-efi-*-signed package, then modules keep receiving updates, but no SRUs of grub-efi-amd64/grub-efi-arm64 getting published meaning nothing is upgraded that has a maintainer script to trigger grub-install. This is closer inline with grub-pc which also stopped calling grub-install in the release series. But I feel iffy about this.
but i'm not sure if it is ok to add circular dependency from grub-efi-*-bin back onto grub-efi-amd64/grub-efi-amd64/signed/grub-pc.
almost as if the top level packages should simply have a file trigger on modules directory to trigger upgrade logic to execute grub-install.
also feel iffy about the fact that -signed ships efi apps; -signed-bin ships modules; and -signed-dbg ships debug ones. collapsing them all into one will break the multiarch-foreign constraint on the unsigned -bin packages.
I guess question remains if i should add file-triggers in the grub-pc & grub-efi-arm64|amd64-signed packages.
The advantage of file-trigger would be that grub-efi-*-signed packages no longer need to ship any maitaniner scripts, and can be multiarch foreign providing modules & efi apps (and dbg modules separate).
[Test Case]
* Upgrade to new grub-efi-amd64-bin and grub-efi-amd64-signed packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* The binaries shipped by -signed packages are innert, they are bootloader binaries only. The only compatibility that has to be maintained is within the userspace tooling - specifically maintainer scripts, and file names and locations.
[Other Info]
* See all the bug reports that grub can't be installed or upgraded when people use -proposed. |
|
| 2021-02-19 23:04:44 |
Dimitri John Ledkov |
description |
[Impact]
* Currently one needs grub-$platform-bin and grub-$platform-signed packages installed together. As first one provides modules, and the later one provides signed .efi images. The two are built from different source packages, and there is a delay of manual reviews before matching signed grub appears.
* The proposal is to rename modules in -bin to be shipped in the $platfrom-unsigned directly.
* And make -signed-bin package ship modules
* And add dependency from the -bin onto > -signed-bin one
* This allows allows in the future for grub2-signed to pull appropriate grub modules for a given distro. For example, using 2.04 modules & signed images from focal on bionic to gain support for TPM verifies and other EFI platform specific developments without affecting userspace grub tooling.
[Caveats]
* If one chooses to remove or not install grub-efi-*-signed package, then modules keep receiving updates, but no SRUs of grub-efi-amd64/grub-efi-arm64 getting published meaning nothing is upgraded that has a maintainer script to trigger grub-install. This is closer inline with grub-pc which also stopped calling grub-install in the release series. But I feel iffy about this.
but i'm not sure if it is ok to add circular dependency from grub-efi-*-bin back onto grub-efi-amd64/grub-efi-amd64/signed/grub-pc.
almost as if the top level packages should simply have a file trigger on modules directory to trigger upgrade logic to execute grub-install.
also feel iffy about the fact that -signed ships efi apps; -signed-bin ships modules; and -signed-dbg ships debug ones. collapsing them all into one will break the multiarch-foreign constraint on the unsigned -bin packages.
I guess question remains if i should add file-triggers in the grub-pc & grub-efi-arm64|amd64-signed packages.
The advantage of file-trigger would be that grub-efi-*-signed packages no longer need to ship any maitaniner scripts, and can be multiarch foreign providing modules & efi apps (and dbg modules separate).
[Test Case]
* Upgrade to new grub-efi-amd64-bin and grub-efi-amd64-signed packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* The binaries shipped by -signed packages are innert, they are bootloader binaries only. The only compatibility that has to be maintained is within the userspace tooling - specifically maintainer scripts, and file names and locations.
[Other Info]
* See all the bug reports that grub can't be installed or upgraded when people use -proposed. |
[Impact]
* The proposal is to rename modules in -bin to be shipped in the $platfrom-unsigned directory.
* And make -signed-bin package ship modules
* And add dependency from the -bin onto > -signed-bin (>= $grub2-signed stem)
* This allows allows in the future for grub2-signed to pull appropriate grub modules for a given distro. For example, using 2.04 modules & signed images from focal on bionic to gain support for TPM verifies and other EFI platform specific developments without affecting userspace grub tooling.
[Caveats]
* In devel series, keep grub2 submitting things for signing SB_SUBMIT := yes
* With every new upload bump the version number of the -signed-bin (>= $grub2-signed-ver) package, to the expected one from grub2-signed.
* Upload new grub2-signed, vendoring the desired signed grub2
--
In stable series, disable submitting signing SB_SUBMIT := no
Upload grub2 to bump the version number of the -signed-bin (>= $grub2-signed-ver) dependency, to the expected one from grub2-signed.
Upload new grub2-signed pulling whichever signed grub from whichever series as needed.
[Test Case]
* Upgrade to new grub-efi-amd64-bin and grub-efi-amd64-signed packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* The binaries shipped by -signed packages are innert, they are bootloader binaries only. The only compatibility that has to be maintained is within the userspace tooling - specifically maintainer scripts, and file names and locations.
[Other Info]
* See all the bug reports that grub can't be installed or upgraded when people use -proposed. |
|
| 2021-02-19 23:51:51 |
Dimitri John Ledkov |
description |
[Impact]
* The proposal is to rename modules in -bin to be shipped in the $platfrom-unsigned directory.
* And make -signed-bin package ship modules
* And add dependency from the -bin onto > -signed-bin (>= $grub2-signed stem)
* This allows allows in the future for grub2-signed to pull appropriate grub modules for a given distro. For example, using 2.04 modules & signed images from focal on bionic to gain support for TPM verifies and other EFI platform specific developments without affecting userspace grub tooling.
[Caveats]
* In devel series, keep grub2 submitting things for signing SB_SUBMIT := yes
* With every new upload bump the version number of the -signed-bin (>= $grub2-signed-ver) package, to the expected one from grub2-signed.
* Upload new grub2-signed, vendoring the desired signed grub2
--
In stable series, disable submitting signing SB_SUBMIT := no
Upload grub2 to bump the version number of the -signed-bin (>= $grub2-signed-ver) dependency, to the expected one from grub2-signed.
Upload new grub2-signed pulling whichever signed grub from whichever series as needed.
[Test Case]
* Upgrade to new grub-efi-amd64-bin and grub-efi-amd64-signed packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* The binaries shipped by -signed packages are innert, they are bootloader binaries only. The only compatibility that has to be maintained is within the userspace tooling - specifically maintainer scripts, and file names and locations.
[Other Info]
* See all the bug reports that grub can't be installed or upgraded when people use -proposed. |
[Impact]
* The proposal is to rename modules in -bin to be shipped in the $platfrom-unsigned directory.
* And make -signed-bin package ship modules
* And add dependency from the -bin onto > -signed-bin (>= $grub2-signed stem)
* This allows allows in the future for grub2-signed to pull appropriate grub modules for a given distro. For example, using 2.04 modules & signed images from focal on bionic to gain support for TPM verifies and other EFI platform specific developments without affecting userspace grub tooling.
[Caveats]
* In devel series, keep grub2 submitting things for signing by setting SB_SUBMIT := yes
* With every new upload bump the version number of the -signed-bin (>= $grub2-signed-ver) package, to the expected one from grub2-signed.
* Upload new grub2-signed with the version set above or higher, vendoring the desired signed grub2.
--
In stable series to disable submitting signing set SB_SUBMIT := no.
Then one can upload grub2-signed first, followed by grub2.
Upload grub2 to bump the version number of the -signed-bin (>= $grub2-signed-ver) dependency, to the expected one from grub2-signed.
Upload new grub2-signed pulling whichever signed grub from whichever series as needed.
[Test Case]
* Upgrade to new grub-efi-amd64-bin and grub-efi-amd64-signed packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* The binaries shipped by -signed packages are innert, they are bootloader binaries only. The only compatibility that has to be maintained is within the userspace tooling - specifically maintainer scripts, and file names and locations.
[Other Info]
* See all the bug reports that grub can't be installed or upgraded when people use -proposed. |
|
| 2021-02-20 02:37:11 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~xnox/grub/+git/grub/+merge/398407 |
|
| 2021-02-23 17:53:19 |
Dimitri John Ledkov |
description |
[Impact]
* The proposal is to rename modules in -bin to be shipped in the $platfrom-unsigned directory.
* And make -signed-bin package ship modules
* And add dependency from the -bin onto > -signed-bin (>= $grub2-signed stem)
* This allows allows in the future for grub2-signed to pull appropriate grub modules for a given distro. For example, using 2.04 modules & signed images from focal on bionic to gain support for TPM verifies and other EFI platform specific developments without affecting userspace grub tooling.
[Caveats]
* In devel series, keep grub2 submitting things for signing by setting SB_SUBMIT := yes
* With every new upload bump the version number of the -signed-bin (>= $grub2-signed-ver) package, to the expected one from grub2-signed.
* Upload new grub2-signed with the version set above or higher, vendoring the desired signed grub2.
--
In stable series to disable submitting signing set SB_SUBMIT := no.
Then one can upload grub2-signed first, followed by grub2.
Upload grub2 to bump the version number of the -signed-bin (>= $grub2-signed-ver) dependency, to the expected one from grub2-signed.
Upload new grub2-signed pulling whichever signed grub from whichever series as needed.
[Test Case]
* Upgrade to new grub-efi-amd64-bin and grub-efi-amd64-signed packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* The binaries shipped by -signed packages are innert, they are bootloader binaries only. The only compatibility that has to be maintained is within the userspace tooling - specifically maintainer scripts, and file names and locations.
[Other Info]
* See all the bug reports that grub can't be installed or upgraded when people use -proposed. |
[Impact]
* The proposal is to split src:grub2 into two source packages
src:grub2 will continue to build most things, apart from bin|dbg|signing-tempate binary packages for platforms that get signed.
src:grub2-unsigned source package is source-full copy of src:grub2 that only builds bin|dbg|signing-tempate binary packages for platforms that get signed and submits monolithic binaries for signing.
src:grub2-signed is built as before, but its maintainer scripts should be compatible across grub2-common from precise and up.
Stable series will receive grub2 update that drops building bin|dbg|signing-template.
Stable series will receive binary-copy of grub2-unsigned & grub2-signed, thus on signed platforms EFI apps and modules will be the same across all series.
[Caveats]
* In devel series, always upload grub2 with matching src:grub2-unsigned which can be build with ./debian/rules generate-grub2-unsigned command.
* In stable series, only upload src:grub2 when fixes needed in update-grub / grub.cfg / grub-install / etc, but not in the efi modules & apps.
* As needed, binary copy grub2-unsigned & grub2-signed from later series to stable series.
[Test Case]
* Upgrade to new packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* There might be regression on the EFI platforms with grub 2.04 that have not so far been caught on Focal / Groovy / Hirsute. |
|
| 2021-02-23 17:54:03 |
Dimitri John Ledkov |
description |
[Impact]
* The proposal is to split src:grub2 into two source packages
src:grub2 will continue to build most things, apart from bin|dbg|signing-tempate binary packages for platforms that get signed.
src:grub2-unsigned source package is source-full copy of src:grub2 that only builds bin|dbg|signing-tempate binary packages for platforms that get signed and submits monolithic binaries for signing.
src:grub2-signed is built as before, but its maintainer scripts should be compatible across grub2-common from precise and up.
Stable series will receive grub2 update that drops building bin|dbg|signing-template.
Stable series will receive binary-copy of grub2-unsigned & grub2-signed, thus on signed platforms EFI apps and modules will be the same across all series.
[Caveats]
* In devel series, always upload grub2 with matching src:grub2-unsigned which can be build with ./debian/rules generate-grub2-unsigned command.
* In stable series, only upload src:grub2 when fixes needed in update-grub / grub.cfg / grub-install / etc, but not in the efi modules & apps.
* As needed, binary copy grub2-unsigned & grub2-signed from later series to stable series.
[Test Case]
* Upgrade to new packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* There might be regression on the EFI platforms with grub 2.04 that have not so far been caught on Focal / Groovy / Hirsute. |
[Impact]
The proposal is to split src:grub2 into two source packages.
src:grub2 will continue to build most things, apart from bin|dbg|signing-tempate binary packages for platforms that get signed.
src:grub2-unsigned source package is source-full copy of src:grub2 that only builds bin|dbg|signing-tempate binary packages for platforms that get signed and submits monolithic binaries for signing.
src:grub2-signed is built as before, but its maintainer scripts should be compatible across grub2-common from precise and up.
Stable series will receive grub2 update that drops building bin|dbg|signing-template.
Stable series will receive binary-copy of grub2-unsigned & grub2-signed, thus on signed platforms EFI apps and modules will be the same across all series.
[Caveats]
* In devel series, always upload grub2 with matching src:grub2-unsigned and src:grub2-signed. The unsigned package can be build with ./debian/rules generate-grub2-unsigned command from src:grub2.
* In stable series, only upload src:grub2 when fixes needed in update-grub / grub.cfg / grub-install / etc, but not in the efi modules & apps.
* As needed, binary copy grub2-unsigned & grub2-signed from later series to stable series.
[Test Case]
* Upgrade to new packages
* Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues.
[Where problems could occur]
* There might be regression on the EFI platforms with grub 2.04 that have not so far been caught on Focal / Groovy / Hirsute. |
|
| 2021-02-26 07:26:28 |
Launchpad Janitor |
grub2-signed (Ubuntu): status |
New |
Fix Released |
|
| 2021-03-02 08:52:26 |
Dimitri John Ledkov |
grub2-signed (Ubuntu): status |
Fix Released |
New |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Groovy |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
bug task added |
|
grub2 (Ubuntu Groovy) |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
bug task added |
|
grub2-signed (Ubuntu Groovy) |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Xenial |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
bug task added |
|
grub2 (Ubuntu Xenial) |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
bug task added |
|
grub2-signed (Ubuntu Xenial) |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Focal |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
bug task added |
|
grub2 (Ubuntu Focal) |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
bug task added |
|
grub2-signed (Ubuntu Focal) |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Bionic |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
bug task added |
|
grub2 (Ubuntu Bionic) |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
bug task added |
|
grub2-signed (Ubuntu Bionic) |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Hirsute |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
bug task added |
|
grub2 (Ubuntu Hirsute) |
|
| 2021-03-02 20:33:15 |
Dimitri John Ledkov |
bug task added |
|
grub2-signed (Ubuntu Hirsute) |
|
| 2021-03-02 20:33:27 |
Dimitri John Ledkov |
grub2 (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2021-03-02 20:33:35 |
Dimitri John Ledkov |
grub2 (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2021-03-02 20:33:43 |
Dimitri John Ledkov |
grub2 (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2021-03-02 20:33:51 |
Dimitri John Ledkov |
grub2 (Ubuntu Groovy): status |
New |
Fix Committed |
|
| 2021-03-02 20:33:59 |
Dimitri John Ledkov |
grub2 (Ubuntu Hirsute): status |
New |
Fix Committed |
|
| 2021-03-02 20:34:08 |
Dimitri John Ledkov |
grub2-signed (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2021-03-02 20:34:16 |
Dimitri John Ledkov |
grub2-signed (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2021-03-02 20:34:25 |
Dimitri John Ledkov |
grub2-signed (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2021-03-02 20:34:33 |
Dimitri John Ledkov |
grub2-signed (Ubuntu Groovy): status |
New |
Fix Committed |
|
| 2021-03-02 20:34:42 |
Dimitri John Ledkov |
grub2-signed (Ubuntu Hirsute): status |
New |
Fix Committed |
|
| 2021-03-02 20:41:30 |
Dimitri John Ledkov |
merge proposal unlinked |
https://code.launchpad.net/~xnox/grub/+git/grub/+merge/398407 |
|
|
| 2021-03-03 08:53:48 |
Launchpad Janitor |
grub2 (Ubuntu Hirsute): status |
Fix Committed |
Fix Released |
|
| 2021-03-03 08:53:48 |
Launchpad Janitor |
cve linked |
|
2020-14372 |
|
| 2021-03-03 08:53:48 |
Launchpad Janitor |
cve linked |
|
2020-25632 |
|
| 2021-03-03 08:53:48 |
Launchpad Janitor |
cve linked |
|
2020-25647 |
|
| 2021-03-03 08:53:48 |
Launchpad Janitor |
cve linked |
|
2020-27749 |
|
| 2021-03-03 08:53:48 |
Launchpad Janitor |
cve linked |
|
2020-27779 |
|
| 2021-03-03 08:53:48 |
Launchpad Janitor |
cve linked |
|
2021-20225 |
|
| 2021-03-03 08:53:48 |
Launchpad Janitor |
cve linked |
|
2021-20233 |
|
| 2021-03-03 08:53:49 |
Launchpad Janitor |
grub2-signed (Ubuntu Hirsute): status |
Fix Committed |
Fix Released |
|
| 2021-03-03 11:41:44 |
Dimitri John Ledkov |
tags |
patch |
block-proposed block-proposed-hirsute patch |
|
| 2021-03-05 02:05:46 |
Dimitri John Ledkov |
grub2 (Ubuntu Hirsute): status |
Fix Released |
In Progress |
|
| 2021-03-05 02:05:55 |
Dimitri John Ledkov |
grub2-signed (Ubuntu Hirsute): status |
Fix Released |
In Progress |
|
| 2021-03-05 02:06:10 |
Dimitri John Ledkov |
bug task added |
|
grub2-unsigned (Ubuntu) |
|
| 2021-03-05 11:11:05 |
Dimitri John Ledkov |
tags |
block-proposed block-proposed-hirsute patch |
|
|
| 2021-03-05 12:30:28 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2021-03-05 16:04:33 |
Launchpad Janitor |
grub2 (Ubuntu Hirsute): status |
In Progress |
Fix Released |
|
| 2021-03-05 16:04:35 |
Launchpad Janitor |
grub2-signed (Ubuntu Hirsute): status |
In Progress |
Fix Released |
|
| 2021-03-08 23:12:12 |
Mathew Hodson |
bug |
|
|
added subscriber Mathew Hodson |
| 2021-03-19 05:46:03 |
Mathew Hodson |
grub2-unsigned (Ubuntu Hirsute): status |
New |
Fix Released |
|
| 2021-03-29 11:29:34 |
Dimitri John Ledkov |
grub2-unsigned (Ubuntu Groovy): status |
New |
Fix Committed |
|
| 2021-03-29 11:29:52 |
Dimitri John Ledkov |
grub2-unsigned (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2021-03-29 11:30:26 |
Dimitri John Ledkov |
grub2-unsigned (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2021-03-29 11:30:36 |
Dimitri John Ledkov |
grub2-unsigned (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2021-03-29 11:31:43 |
Dimitri John Ledkov |
tags |
patch |
patch verification-done verification-done-bionic verification-done-focal verification-done-groovy verification-done-xenial |
|
| 2021-04-12 16:22:24 |
Launchpad Janitor |
grub2 (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2021-04-12 16:23:02 |
Launchpad Janitor |
grub2-signed (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2021-04-13 12:34:13 |
Dimitri John Ledkov |
grub2-unsigned (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2021-04-27 08:39:53 |
Launchpad Janitor |
grub2 (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-04-27 08:39:59 |
Launchpad Janitor |
grub2-signed (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-04-29 22:06:40 |
Launchpad Janitor |
grub2 (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2021-04-29 22:06:52 |
Launchpad Janitor |
grub2-signed (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2021-04-30 19:36:38 |
Steve Langasek |
grub2 (Ubuntu Xenial): status |
Fix Released |
Fix Committed |
|
| 2021-04-30 19:36:47 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-04-30 19:36:50 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2021-04-30 19:36:54 |
Steve Langasek |
tags |
patch verification-done verification-done-bionic verification-done-focal verification-done-groovy verification-done-xenial |
patch verification-done-bionic verification-done-focal verification-done-groovy verification-needed verification-needed-xenial |
|
| 2021-05-07 21:29:07 |
Launchpad Janitor |
grub2 (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2021-05-07 21:29:22 |
Launchpad Janitor |
grub2-signed (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2021-05-08 20:32:18 |
Julian Andres Klode |
tags |
patch verification-done-bionic verification-done-focal verification-done-groovy verification-needed verification-needed-xenial |
patch verification-done verification-done-bionic verification-done-focal verification-done-groovy verification-done-xenial |
|
| 2021-05-08 21:57:55 |
Launchpad Janitor |
grub2 (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2021-06-07 20:22:47 |
Steve Langasek |
grub2-unsigned (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2021-06-07 20:23:07 |
Steve Langasek |
grub2-unsigned (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2021-06-07 20:23:44 |
Steve Langasek |
grub2-unsigned (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-06-07 23:03:08 |
Mathew Hodson |
removed subscriber Mathew Hodson |
|
|
|
