[Bug 1571388] Re: grub-efi-amd64: prompted to disable SecureBoot on upgrade from 2.02~beta2-36ubuntu2 to 2.02~beta2-36ubuntu3

2021-06-20 Thread Steve Langasek
Xenial is now in extended support, and only one other user reported
being affected by this bug.  So by and large this seems to have not been
a significant issue; and post-xenial, it's even less of a problem
because it should only affect upgrades *to* xenial.  Therefore marking
this wontfix, barring any further information.

** Changed in: shim-signed (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: shim-signed (Ubuntu)
Milestone: ubuntu-17.05 => None

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571388

Title:
  grub-efi-amd64: prompted to disable SecureBoot on upgrade from
  2.02~beta2-36ubuntu2 to 2.02~beta2-36ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1571388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811901] Re: shim crashes in OBJ_create()

2021-06-20 Thread Steve Langasek
** Changed in: shim-signed (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811901

Title:
  shim crashes in OBJ_create()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1811901/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926748] Re: regression in xenial updates - grub2 cannot handle new arm64 relocations

2021-06-19 Thread Steve Langasek
When a developer marks a bug task as invalid, Mathew, you do not need to
be changing it to fix released.

** Changed in: grub2 (Ubuntu)
   Status: Fix Released => Invalid

** Changed in: grub2-signed (Ubuntu)
   Status: Fix Released => Invalid

** Changed in: grub2-unsigned (Ubuntu)
   Status: Fix Released => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926748

Title:
  regression in xenial updates - grub2 cannot handle new arm64
  relocations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932967] Re: Please remove twig-extensions from Impish

2021-06-18 Thread Steve Langasek
Removing packages:
twig-extensions 1.5.4-2build1 in impish
php-twig-extensions 1.5.4-2build1 in impish amd64
php-twig-extensions 1.5.4-2build1 in impish arm64
php-twig-extensions 1.5.4-2build1 in impish armhf
php-twig-extensions 1.5.4-2build1 in impish i386
php-twig-extensions 1.5.4-2build1 in impish ppc64el
php-twig-extensions 1.5.4-2build1 in impish riscv64
php-twig-extensions 1.5.4-2build1 in impish s390x
Comment: (From Debian) ROM; abandoned upstream; Debian bug #980343
Remove [y|N]? y


** Changed in: twig-extensions (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932967

Title:
  Please remove twig-extensions from Impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/twig-extensions/+bug/1932967/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932122] Re: ubuntu installer crashed

2021-06-16 Thread Steve Langasek
According to the logs, sda1 is formatted as an ext2 partition; so it's
not an ESP since an ESP must be FAT.

It's possible we could improve ubiquity's handling of this case, but if
you are skipping ubiquity's support for automatically configuring your
partitions correctly, you're somewhat on your own for getting the
partitions right.

** Changed in: ubiquity (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932122

Title:
  ubuntu installer crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1932122/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927078] Re: Don't allow useradd to use fully numeric names

2021-06-16 Thread Steve Langasek
> I think our preference would be to disallow leading numeric digits
> entirely so that for example, 0x0 and 0o0 would be blocked as well,
> to try to prevent both user and programmatic confusion.

Disallowing leading numeric digits entirely would, unfortunately,
disable a significant class of valid usernames in conflict with
historical usage.

The main motivation in fixing this is that allowing fully-numeric
usernames means there is ambiguity in contexts that can reference both
uids and usernames and do not have strong typing.  Aside from systemd,
this is mostly about shells and invocations of various commandline
tools; and neither bash nor the tools appear to interpret 0o0 or 0x0 as
numbers:

$ id 0o0
id: ‘0o0’: no such user
$ id 0x0
id: ‘0x0’: no such user
$ getent passwd 0x0
$ getent passwd 0o0

Let's please focus on the known problem case of all-numeric usernames.
If there are other confirmed security issues with octal/hex
representations of numbers, then we should also close those, but it
needs a more precise fix than disabling leading digits.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927078

Title:
  Don't allow useradd to use fully numeric names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931913] Re: Please drop shaarli (and associated components) from impish

2021-06-16 Thread Steve Langasek
Removing packages from impish:
php-pimple 3.3.1-1 in impish
php-pimple 3.3.1-1 in impish amd64
php-pimple 3.3.1-1 in impish arm64
php-pimple 3.3.1-1 in impish armhf
php-pimple 3.3.1-1 in impish i386
php-pimple 3.3.1-1 in impish ppc64el
php-pimple 3.3.1-1 in impish riscv64
php-pimple 3.3.1-1 in impish s390x
Comment: FTBFS with new PSR, blocks php8 transition; LP: #1931913
1 package successfully removed.


** Changed in: php-pimple (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931913

Title:
  Please drop shaarli (and associated components) from impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-oscarotero-gettext/+bug/1931913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931913] Re: Please drop shaarli (and associated components) from impish

2021-06-16 Thread Steve Langasek
Thanks.  It's important to be clear about the rationale for removing any
given package, rather than "associated components" since if the
"associated" components are not themselves buggy, it causes confusion to
remove them and then have to bring them back later.

Removing packages from impish:
php-slim 3.12.3-4 in impish
php-slim 3.12.3-4 in impish amd64
php-slim 3.12.3-4 in impish arm64
php-slim 3.12.3-4 in impish armhf
php-slim 3.12.3-4 in impish i386
php-slim 3.12.3-4 in impish ppc64el
php-slim 3.12.3-4 in impish riscv64
php-slim 3.12.3-4 in impish s390x
Comment: broken by new php-psr-container, blocks php8 transition; LP: #1931913
1 package successfully removed.


** Changed in: php-slim (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931913

Title:
  Please drop shaarli (and associated components) from impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-oscarotero-gettext/+bug/1931913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927264] Re: Php8.0 Transition - Please remove and blacklist php7.4

2021-06-16 Thread Steve Langasek
$ reverse-depends src:php7.4
Reverse-Depends
* libapache2-mod-php(for libapache2-mod-php7.4)
* libphp-embed  (for libphp7.4-embed)
* php   (for php7.4)
* php-all-dev   (for php7.4-dev)
* php-all-dev   (for php7.4-json)
* php-bcmath(for php7.4-bcmath)
* php-bz2   (for php7.4-bz2)
* php-cgi   (for php7.4-cgi)
* php-cli   (for php7.4-cli)
* php-curl  (for php7.4-curl)
* php-dev   (for php7.4-dev)
* php-enchant   (for php7.4-enchant)
* php-fpm   (for php7.4-fpm)
* php-gd(for php7.4-gd)
* php-gmp   (for php7.4-gmp)
* php-imap  (for php7.4-imap)
* php-interbase (for php7.4-interbase)
* php-intl  (for php7.4-intl)
* php-json  (for php7.4-json)
* php-ldap  (for php7.4-ldap)
* php-mbstring  (for php7.4-mbstring)
* php-mysql (for php7.4-mysql)
* php-odbc  (for php7.4-odbc)
* php-pgsql (for php7.4-pgsql)
* php-phpdbg(for php7.4-phpdbg)
* php-pspell(for php7.4-pspell)
* php-readline  (for php7.4-readline)
* php-snmp  (for php7.4-snmp)
* php-soap  (for php7.4-soap)
* php-sqlite3   (for php7.4-sqlite3)
* php-sybase(for php7.4-sybase)
* php-tidy  (for php7.4-tidy)
* php-xml   (for php7.4-xml)
* php-xmlrpc(for php7.4-xmlrpc)
* php-zip   (for php7.4-zip)

Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
$

php-defaults 2:8.0+82~0build1 has not yet made it into the release
pocket, so removing php7.4 will make large swaths of packages
uninstallable (and results in proposed-migration being rather
untrustworthy in resolving these uninstallabilities correctly).  php-
defaults appears to be blocked from migrating by autopkgtest regressions
that are unrelated to php7.4.  So removing php7.4 does not look correct
to me.

We will eventually have to deal with php-defaults migration making
php7.4-common uninstallable; but that is likely best handled by a force
hint in britney, not a forced removal of php7.4.

** Changed in: php7.4 (Ubuntu)
   Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927264

Title:
  Php8.0 Transition - Please remove and blacklist php7.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-defaults/+bug/1927264/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931806] Re: Wrong repository

2021-06-16 Thread Steve Langasek
Override component to universe
maelstrom 1.4.3-L3.0.6+main-9build1 in impish: multiverse/games -> universe
maelstrom 1.4.3-L3.0.6+main-9build1 in impish amd64: 
multiverse/games/optional/100% -> universe
maelstrom 1.4.3-L3.0.6+main-9build1 in impish arm64: 
multiverse/games/optional/100% -> universe
maelstrom 1.4.3-L3.0.6+main-9build1 in impish armhf: 
multiverse/games/optional/100% -> universe
maelstrom 1.4.3-L3.0.6+main-9build1 in impish ppc64el: 
multiverse/games/optional/100% -> universe
maelstrom 1.4.3-L3.0.6+main-9build1 in impish riscv64: 
multiverse/games/optional/100% -> universe
maelstrom 1.4.3-L3.0.6+main-9build1 in impish s390x: 
multiverse/games/optional/100% -> universe
7 publications overridden.


** Changed in: maelstrom (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931806

Title:
  Wrong repository

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maelstrom/+bug/1931806/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931913] Re: Please drop shaarli (and associated components) from impish

2021-06-16 Thread Steve Langasek
Is php-slim itself blocking the migration?  If not, we would normally
leave such a package in - rather than removing it solely because nothing
else depends on it.  In particular, if Debian fixes php-oscarotero-
gettext, we would want shaarli to be available+installable again without
additional work to resurrect php-slim.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931913

Title:
  Please drop shaarli (and associated components) from impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-oscarotero-gettext/+bug/1931913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931913] Re: Please drop shaarli (and associated components) from impish

2021-06-16 Thread Steve Langasek
Removing packages from impish:
php-oscarotero-gettext 4.8.2-4 in impish
php-oscarotero-gettext 4.8.2-4 in impish amd64
php-oscarotero-gettext 4.8.2-4 in impish arm64
php-oscarotero-gettext 4.8.2-4 in impish armhf
php-oscarotero-gettext 4.8.2-4 in impish i386
php-oscarotero-gettext 4.8.2-4 in impish ppc64el
php-oscarotero-gettext 4.8.2-4 in impish riscv64
php-oscarotero-gettext 4.8.2-4 in impish s390x
Comment: blocks php transition; LP: #1931913
1 package successfully removed.


** Changed in: php-oscarotero-gettext (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931913

Title:
  Please drop shaarli (and associated components) from impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-oscarotero-gettext/+bug/1931913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931913] Re: Please drop shaarli (and associated components) from impish

2021-06-16 Thread Steve Langasek
Removing packages from impish:
shaarli 0.12.0+dfsg-2 in impish
shaarli 0.12.0+dfsg-2 in impish amd64
shaarli 0.12.0+dfsg-2 in impish arm64
shaarli 0.12.0+dfsg-2 in impish armhf
shaarli 0.12.0+dfsg-2 in impish i386
shaarli 0.12.0+dfsg-2 in impish ppc64el
shaarli 0.12.0+dfsg-2 in impish riscv64
shaarli 0.12.0+dfsg-2 in impish s390x
Comment: blocks php transition; LP: #1931913
1 package successfully removed.


** Changed in: shaarli (Ubuntu)
   Status: New => Fix Released

** Also affects: php-oscarotero-gettext (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931913

Title:
  Please drop shaarli (and associated components) from impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-oscarotero-gettext/+bug/1931913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931914] Re: Please drop php-nesbot-carbon from impish

2021-06-15 Thread Steve Langasek
Removing packages from impish:
php-nesbot-carbon 2.32.2-1 in impish
php-nesbot-carbon 2.32.2-1 in impish amd64
php-nesbot-carbon 2.32.2-1 in impish arm64
php-nesbot-carbon 2.32.2-1 in impish armhf
php-nesbot-carbon 2.32.2-1 in impish i386
php-nesbot-carbon 2.32.2-1 in impish ppc64el
php-nesbot-carbon 2.32.2-1 in impish riscv64
php-nesbot-carbon 2.32.2-1 in impish s390x
Comment: Fails tests with new PHP; LP: #1931914
1 package successfully removed.
Removing packages from impish-proposed:
php-nesbot-carbon 2.32.2-1build1 in impish
Comment: Fails tests with new PHP; LP: #1931914
1 package successfully removed.


** Changed in: php-nesbot-carbon (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931914

Title:
  Please drop php-nesbot-carbon from impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-nesbot-carbon/+bug/1931914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code

2021-06-15 Thread Steve Langasek
** Tags added: fr-1444

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931994

Title:
  [Ubuntu 20.04] OpenSSL bugs im s390x AES code

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1910192] Re: Remove 0.1.0 from the archive

2021-06-13 Thread Steve Langasek
** Changed in: lomiri-url-dispatcher (Ubuntu)
   Status: New => Fix Released

** Also affects: ayatana-indicator-datetime (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ayatana-indicator-power (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: proposed-migration

** Tags removed: proposed-migration
** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910192

Title:
  Remove 0.1.0 from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-datetime/+bug/1910192/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2021-06-13 Thread Steve Langasek
** Changed in: aptdaemon
 Assignee: RICARDO ALEXIS RESTREPO RENGIFO (richard618921) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/349469

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1918023] Re: Please remove armhf and s390x binaries for gdpc

2021-06-11 Thread Steve Langasek
This got done somewhere along the way :)

** Changed in: gdpc (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918023

Title:
  Please remove armhf and s390x binaries for gdpc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdpc/+bug/1918023/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931315] Re: Please drop php-laravel-framework (and associated components), and movim from impish

2021-06-11 Thread Steve Langasek
Removing packages from impish:
ratchetphp 0.4.2-1build1 in impish
php-cboden-ratchet 0.4.2-1build1 in impish amd64
php-cboden-ratchet 0.4.2-1build1 in impish arm64
php-cboden-ratchet 0.4.2-1build1 in impish armhf
php-cboden-ratchet 0.4.2-1build1 in impish i386
php-cboden-ratchet 0.4.2-1build1 in impish ppc64el
php-cboden-ratchet 0.4.2-1build1 in impish riscv64
php-cboden-ratchet 0.4.2-1build1 in impish s390x
Comment: blocks php transition; LP: #1931315
1 package successfully removed.


** Changed in: ratchetphp (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931315

Title:
  Please drop php-laravel-framework (and associated components), and
  movim from impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/movim/+bug/1931315/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931315] Re: Please drop php-laravel-framework (and associated components), and movim from impish

2021-06-11 Thread Steve Langasek
Removing packages from impish:
php-robmorgan-phinx 0.9.2-3build1 in impish
php-robmorgan-phinx 0.9.2-3build1 in impish amd64
php-robmorgan-phinx 0.9.2-3build1 in impish arm64
php-robmorgan-phinx 0.9.2-3build1 in impish armhf
php-robmorgan-phinx 0.9.2-3build1 in impish i386
php-robmorgan-phinx 0.9.2-3build1 in impish ppc64el
php-robmorgan-phinx 0.9.2-3build1 in impish riscv64
php-robmorgan-phinx 0.9.2-3build1 in impish s390x
Comment: blocks php transition; LP: #1931315
1 package successfully removed.


** Changed in: php-robmorgan-phinx (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931315

Title:
  Please drop php-laravel-framework (and associated components), and
  movim from impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/movim/+bug/1931315/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920959] Re: Remove rust-derive-more from hirsute{,-proposed}

2021-06-11 Thread Steve Langasek
Deleted on 2021-03-29.

** Changed in: rust-derive-more (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920959

Title:
  Remove rust-derive-more from hirsute{,-proposed}

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-derive-more/+bug/1920959/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920961] Re: Remove ams.lv2

2021-06-11 Thread Steve Langasek
Deleted on 2021-03-31.

** Changed in: ams.lv2 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920961

Title:
  Remove ams.lv2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ams.lv2/+bug/1920961/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921100] Re: remove gconf-editor again, add it to sync blocklist

2021-06-11 Thread Steve Langasek
I don't think we want to blacklist this; it came back because it
previously had an Ubuntu delta and was out of date, so the new version
was synced.  I expect any further uploads of gconf-editor to fix this
bug, so no need to blacklist.

Removing packages from impish-proposed:
gconf-editor 3.0.1-6 in impish
Comment: deprecated, build-depends on the deprecated gnome-doc-utils, removed 
from Debian; LP: #1921100
1 package successfully removed.


** Changed in: gconf-editor (Ubuntu)
   Status: New => Incomplete

** Changed in: gconf-editor (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921100

Title:
  remove gconf-editor again, add it to sync blocklist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf-editor/+bug/1921100/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute

2021-06-11 Thread Steve Langasek
indicator-sound has reverse-dependencies, so this probably needs fixed
rather than removed.

** Changed in: poppler-qml-plugin (Ubuntu)
   Status: New => Fix Released

** Changed in: qtpowerd (Ubuntu)
   Status: New => Fix Released

** Changed in: qtubuntu-cameraplugin-fake (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921781

Title:
  Build-depends on qt5-default which is obsolete and dropped in hirsute

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922606] Re: Please remove wulfware from Ubuntu

2021-06-11 Thread Steve Langasek
Removing packages from impish:
wulfware 2.6.0-0ubuntu5 in impish
libwulf-dev 2.6.0-0ubuntu5 in impish amd64
libwulf-dev 2.6.0-0ubuntu5 in impish arm64
libwulf-dev 2.6.0-0ubuntu5 in impish armhf
libwulf-dev 2.6.0-0ubuntu5 in impish ppc64el
libwulf-dev 2.6.0-0ubuntu5 in impish riscv64
libwulf-dev 2.6.0-0ubuntu5 in impish s390x
libwulf2 2.6.0-0ubuntu5 in impish amd64
libwulf2 2.6.0-0ubuntu5 in impish arm64
libwulf2 2.6.0-0ubuntu5 in impish armhf
libwulf2 2.6.0-0ubuntu5 in impish ppc64el
libwulf2 2.6.0-0ubuntu5 in impish riscv64
libwulf2 2.6.0-0ubuntu5 in impish s390x
wulf2html 2.6.0-0ubuntu5 in impish amd64
wulf2html 2.6.0-0ubuntu5 in impish arm64
wulf2html 2.6.0-0ubuntu5 in impish armhf
wulf2html 2.6.0-0ubuntu5 in impish i386
wulf2html 2.6.0-0ubuntu5 in impish ppc64el
wulf2html 2.6.0-0ubuntu5 in impish riscv64
wulf2html 2.6.0-0ubuntu5 in impish s390x
wulflogger 2.6.0-0ubuntu5 in impish amd64
wulflogger 2.6.0-0ubuntu5 in impish arm64
wulflogger 2.6.0-0ubuntu5 in impish armhf
wulflogger 2.6.0-0ubuntu5 in impish ppc64el
wulflogger 2.6.0-0ubuntu5 in impish riscv64
wulflogger 2.6.0-0ubuntu5 in impish s390x
wulfstat 2.6.0-0ubuntu5 in impish amd64
wulfstat 2.6.0-0ubuntu5 in impish arm64
wulfstat 2.6.0-0ubuntu5 in impish armhf
wulfstat 2.6.0-0ubuntu5 in impish ppc64el
wulfstat 2.6.0-0ubuntu5 in impish riscv64
wulfstat 2.6.0-0ubuntu5 in impish s390x
xmlsysd 2.6.0-0ubuntu5 in impish amd64
xmlsysd 2.6.0-0ubuntu5 in impish arm64
xmlsysd 2.6.0-0ubuntu5 in impish armhf
xmlsysd 2.6.0-0ubuntu5 in impish ppc64el
xmlsysd 2.6.0-0ubuntu5 in impish riscv64
xmlsysd 2.6.0-0ubuntu5 in impish s390x
Comment: Ubuntu-specific, unmaintained since 2007, FTBFS; LP: #1922606
1 package successfully removed.


** Changed in: wulfware (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922606

Title:
  Please remove wulfware from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wulfware/+bug/1922606/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922821] Re: Please remove qtubuntu-cameraplugin-fake from Ubuntu

2021-06-11 Thread Steve Langasek
Removing packages from impish:
qtubuntu-cameraplugin-fake 0.1.10+14.04.20140304-0ubuntu2 in impish
cameraplugin-fake 0.1.10+14.04.20140304-0ubuntu2 in impish amd64
cameraplugin-fake 0.1.10+14.04.20140304-0ubuntu2 in impish arm64
cameraplugin-fake 0.1.10+14.04.20140304-0ubuntu2 in impish armhf
cameraplugin-fake 0.1.10+14.04.20140304-0ubuntu2 in impish 
ppc64el
cameraplugin-fake 0.1.10+14.04.20140304-0ubuntu2 in impish 
riscv64
cameraplugin-fake 0.1.10+14.04.20140304-0ubuntu2 in impish s390x
Comment: Ubuntu-specific, part of an obsolete product, unmaintained since 2014, 
FTBFS; LP: #1922821
1 package successfully removed.


** Changed in: qtubuntu-cameraplugin-fake (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922821

Title:
  Please remove qtubuntu-cameraplugin-fake from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu-cameraplugin-fake/+bug/1922821/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922822] Re: Please remove qtpowerd from Ubuntu

2021-06-11 Thread Steve Langasek
Removing packages from impish:
qtpowerd 0.2+13.10.20131014.3-0ubuntu4 in impish
qtdeclarative5-qtpowerd0.1 0.2+13.10.20131014.3-0ubuntu4 in 
impish amd64
qtdeclarative5-qtpowerd0.1 0.2+13.10.20131014.3-0ubuntu4 in 
impish arm64
qtdeclarative5-qtpowerd0.1 0.2+13.10.20131014.3-0ubuntu4 in 
impish armhf
qtdeclarative5-qtpowerd0.1 0.2+13.10.20131014.3-0ubuntu4 in 
impish ppc64el
qtdeclarative5-qtpowerd0.1 0.2+13.10.20131014.3-0ubuntu4 in 
impish riscv64
qtdeclarative5-qtpowerd0.1 0.2+13.10.20131014.3-0ubuntu4 in 
impish s390x
Comment: Ubuntu-specific, part of an obsolete product, unmaintained since 2013, 
FTBFS; LP: #1922822
1 package successfully removed.


** Changed in: qtpowerd (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922822

Title:
  Please remove qtpowerd from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtpowerd/+bug/1922822/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922823] Re: Please remove poppler-qml-plugin from Ubuntu

2021-06-11 Thread Steve Langasek
Removing packages from impish:
poppler-qml-plugin 0.1.1+13.10.20130819.3-0ubuntu4~gcc5.2 in impish
qtdeclarative5-poppler1.0 
0.1.1+13.10.20130819.3-0ubuntu4~gcc5.2 in impish amd64
qtdeclarative5-poppler1.0 
0.1.1+13.10.20130819.3-0ubuntu4~gcc5.2 in impish arm64
qtdeclarative5-poppler1.0 
0.1.1+13.10.20130819.3-0ubuntu4~gcc5.2 in impish armhf
qtdeclarative5-poppler1.0 
0.1.1+13.10.20130819.3-0ubuntu4~gcc5.2 in impish ppc64el
qtdeclarative5-poppler1.0 
0.1.1+13.10.20130819.3-0ubuntu4~gcc5.2 in impish riscv64
qtdeclarative5-poppler1.0 
0.1.1+13.10.20130819.3-0ubuntu4~gcc5.2 in impish s390x
Comment: Ubuntu-specific, part of an obsolete product, unmaintained since 2013, 
FTBFS; LP: #1922823
1 package successfully removed.


** Changed in: poppler-qml-plugin (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922823

Title:
  Please remove poppler-qml-plugin from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler-qml-plugin/+bug/1922823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922957] Re: Please remove libspe2 from Ubuntu

2021-06-11 Thread Steve Langasek
Removing packages:
libspe2 2.2.80-95-3.1ubuntu7 in impish
libspe2-doc 2.2.80-95-3.1ubuntu7 in impish amd64
libspe2-doc 2.2.80-95-3.1ubuntu7 in impish arm64
libspe2-doc 2.2.80-95-3.1ubuntu7 in impish armhf
libspe2-doc 2.2.80-95-3.1ubuntu7 in impish ppc64el
Comment: (From Debian) RoQA; FTBFS, no MU since 2008, not in squeeze; Debian 
bug #662189
Remove [y|N]? y


** Changed in: libspe2 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922957

Title:
  Please remove libspe2 from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libspe2/+bug/1922957/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928087] Re: Please remove src:jack-rack

2021-06-11 Thread Steve Langasek
Removing packages from impish:
jack-rack 1.4.8~rc1-2ubuntu4 in impish
jack-rack 1.4.8~rc1-2ubuntu4 in impish amd64
jack-rack 1.4.8~rc1-2ubuntu4 in impish arm64
jack-rack 1.4.8~rc1-2ubuntu4 in impish armhf
jack-rack 1.4.8~rc1-2ubuntu4 in impish ppc64el
jack-rack 1.4.8~rc1-2ubuntu4 in impish riscv64
jack-rack 1.4.8~rc1-2ubuntu4 in impish s390x
Comment: Ubuntu-specific, no longer used by UbuntuStudio, removed from Debian 
in 2014, depends on python2; LP: #1928087
1 package successfully removed.


** Changed in: jack-rack (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928087

Title:
  Please remove src:jack-rack

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jack-rack/+bug/1928087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922958] Re: Please remove librcps from Ubuntu

2021-06-11 Thread Steve Langasek
Removing packages from impish:
librcps 0.3-0ubuntu3 in impish
librcps-dev 0.3-0ubuntu3 in impish amd64
librcps-dev 0.3-0ubuntu3 in impish arm64
librcps-dev 0.3-0ubuntu3 in impish armhf
librcps-dev 0.3-0ubuntu3 in impish ppc64el
librcps0 0.3-0ubuntu3 in impish amd64
librcps0 0.3-0ubuntu3 in impish arm64
librcps0 0.3-0ubuntu3 in impish armhf
librcps0 0.3-0ubuntu3 in impish ppc64el
Comment: Ubuntu-specific, unmaintained since 2010, FTBFS; LP: #1922958
1 package successfully removed.


** Changed in: librcps (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922958

Title:
  Please remove librcps from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librcps/+bug/1922958/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922963] Re: Please remove gpp4 from Ubuntu

2021-06-11 Thread Steve Langasek
again, with actually passing the package as an argument:

Removing packages from impish:
gpp4 1.3.1-0ubuntu10 in impish
libgpp4-0 1.3.1-0ubuntu10 in impish amd64
libgpp4-0 1.3.1-0ubuntu10 in impish armhf
libgpp4-0 1.3.1-0ubuntu10 in impish ppc64el
libgpp4-0 1.3.1-0ubuntu10 in impish s390x
libgpp4-dev 1.3.1-0ubuntu10 in impish amd64
libgpp4-dev 1.3.1-0ubuntu10 in impish armhf
libgpp4-dev 1.3.1-0ubuntu10 in impish ppc64el
libgpp4-dev 1.3.1-0ubuntu10 in impish s390x
libgpp4-doc 1.3.1-0ubuntu10 in impish amd64
libgpp4-doc 1.3.1-0ubuntu10 in impish arm64
libgpp4-doc 1.3.1-0ubuntu10 in impish armhf
libgpp4-doc 1.3.1-0ubuntu10 in impish i386
libgpp4-doc 1.3.1-0ubuntu10 in impish ppc64el
libgpp4-doc 1.3.1-0ubuntu10 in impish riscv64
libgpp4-doc 1.3.1-0ubuntu10 in impish s390x
libgpp4f-0 1.3.1-0ubuntu10 in impish amd64
libgpp4f-0 1.3.1-0ubuntu10 in impish armhf
libgpp4f-0 1.3.1-0ubuntu10 in impish ppc64el
libgpp4f-0 1.3.1-0ubuntu10 in impish s390x
libgpp4f-dev 1.3.1-0ubuntu10 in impish amd64
libgpp4f-dev 1.3.1-0ubuntu10 in impish armhf
libgpp4f-dev 1.3.1-0ubuntu10 in impish ppc64el
libgpp4f-dev 1.3.1-0ubuntu10 in impish s390x
Comment: Ubuntu-specific, unmaintained since 2011, FTBFS; LP: #1922963
1 package successfully removed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922963

Title:
  Please remove gpp4 from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpp4/+bug/1922963/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922963] Re: Please remove gpp4 from Ubuntu

2021-06-11 Thread Steve Langasek
Removing packages from impish:
Comment: Ubuntu-specific, unmaintained since 2011, FTBFS; LP: #1922963
0 packages successfully removed.


** Changed in: gpp4 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922963

Title:
  Please remove gpp4 from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpp4/+bug/1922963/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1923533] Re: Please remove nxcomp from Ubuntu

2021-06-11 Thread Steve Langasek
Removing packages from impish:
nxcomp 3.5.0-2-0ubuntu4 in impish
libxcomp-dev 3.5.0-2-0ubuntu4 in impish riscv64
libxcomp3 3.5.0-2-0ubuntu4 in impish riscv64
Comment: Superseded by nx-libs; LP: #1923533
1 package successfully removed.


** Changed in: nxcomp (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923533

Title:
  Please remove nxcomp from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nxcomp/+bug/1923533/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1923534] Re: Please remove nxcompshad from Ubuntu

2021-06-11 Thread Steve Langasek
Removing packages from impish:
nxcompshad 3.3.0-3-0ubuntu1 in impish
libxcompshad-dev 3.3.0-3-0ubuntu1 in impish riscv64
libxcompshad3 3.3.0-3-0ubuntu1 in impish riscv64
Comment: Superseded by nx-libs; LP: #1923534
1 package successfully removed.


** Changed in: nxcompshad (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923534

Title:
  Please remove nxcompshad from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nxcompshad/+bug/1923534/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925034] Re: Please remove src:aws-shell

2021-06-11 Thread Steve Langasek
Removing packages from impish:
aws-shell 0.2.1-1 in impish
aws-shell 0.2.1-1 in impish amd64
aws-shell 0.2.1-1 in impish arm64
aws-shell 0.2.1-1 in impish armhf
aws-shell 0.2.1-1 in impish i386
aws-shell 0.2.1-1 in impish ppc64el
aws-shell 0.2.1-1 in impish riscv64
aws-shell 0.2.1-1 in impish s390x
Comment: FTBFS, removed from Debian testing; Debian bug #944542, LP: #1925034
1 package successfully removed.


** Changed in: aws-shell (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925034

Title:
  Please remove src:aws-shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aws-shell/+bug/1925034/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928087] Re: Please remove src:jack-rack

2021-06-11 Thread Steve Langasek
The reason this was not removed 7 years ago when it was removed in
Debian was because Ubuntu Studio referenced it and so the Ubuntu Studio
team picked it up as the maintainers.  We should check if they still
care about having it in Ubuntu and if they are going to do the work to
migrate it to python3.

If not, or if there is no timely response, we will proceed with the
removal, since jack-rack is no longer seeded in ubuntustudio.

** Changed in: jack-rack (Ubuntu)
   Status: New => Incomplete

** Changed in: jack-rack (Ubuntu)
 Assignee: (unassigned) => Ubuntu Studio Development (ubuntustudio-dev)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928087

Title:
  Please remove src:jack-rack

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jack-rack/+bug/1928087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928877] Re: Please remove rhc from the archive

2021-06-11 Thread Steve Langasek
Removing packages from impish:
rhc 1.38.7-3 in impish
rhc 1.38.7-3 in impish amd64
rhc 1.38.7-3 in impish arm64
rhc 1.38.7-3 in impish armhf
rhc 1.38.7-3 in impish i386
rhc 1.38.7-3 in impish ppc64el
rhc 1.38.7-3 in impish riscv64
rhc 1.38.7-3 in impish s390x
Comment: Deprecated, unused, removed from Debian testing; Debian bug #908295, 
LP: #1928877
1 package successfully removed.


** Changed in: rhc (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928877

Title:
  Please remove rhc from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhc/+bug/1928877/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931315] Re: Please drop php-laravel-framework (and associated components), and movim from impish

2021-06-11 Thread Steve Langasek
Removing packages from impish:
php-laravel-framework 6.20.14+dfsg-2build1 in impish
php-illuminate-auth 6.20.14+dfsg-2build1 in impish amd64
php-illuminate-auth 6.20.14+dfsg-2build1 in impish arm64
php-illuminate-auth 6.20.14+dfsg-2build1 in impish armhf
php-illuminate-auth 6.20.14+dfsg-2build1 in impish i386
php-illuminate-auth 6.20.14+dfsg-2build1 in impish ppc64el
php-illuminate-auth 6.20.14+dfsg-2build1 in impish riscv64
php-illuminate-auth 6.20.14+dfsg-2build1 in impish s390x
php-illuminate-broadcasting 6.20.14+dfsg-2build1 in impish amd64
php-illuminate-broadcasting 6.20.14+dfsg-2build1 in impish arm64
php-illuminate-broadcasting 6.20.14+dfsg-2build1 in impish armhf
php-illuminate-broadcasting 6.20.14+dfsg-2build1 in impish i386
php-illuminate-broadcasting 6.20.14+dfsg-2build1 in impish 
ppc64el
php-illuminate-broadcasting 6.20.14+dfsg-2build1 in impish 
riscv64
php-illuminate-broadcasting 6.20.14+dfsg-2build1 in impish s390x
php-illuminate-bus 6.20.14+dfsg-2build1 in impish amd64
php-illuminate-bus 6.20.14+dfsg-2build1 in impish arm64
php-illuminate-bus 6.20.14+dfsg-2build1 in impish armhf
php-illuminate-bus 6.20.14+dfsg-2build1 in impish i386
php-illuminate-bus 6.20.14+dfsg-2build1 in impish ppc64el
php-illuminate-bus 6.20.14+dfsg-2build1 in impish riscv64
php-illuminate-bus 6.20.14+dfsg-2build1 in impish s390x
php-illuminate-cache 6.20.14+dfsg-2build1 in impish amd64
php-illuminate-cache 6.20.14+dfsg-2build1 in impish arm64
php-illuminate-cache 6.20.14+dfsg-2build1 in impish armhf
php-illuminate-cache 6.20.14+dfsg-2build1 in impish i386
php-illuminate-cache 6.20.14+dfsg-2build1 in impish ppc64el
php-illuminate-cache 6.20.14+dfsg-2build1 in impish riscv64
php-illuminate-cache 6.20.14+dfsg-2build1 in impish s390x
php-illuminate-config 6.20.14+dfsg-2build1 in impish amd64
php-illuminate-config 6.20.14+dfsg-2build1 in impish arm64
php-illuminate-config 6.20.14+dfsg-2build1 in impish armhf
php-illuminate-config 6.20.14+dfsg-2build1 in impish i386
php-illuminate-config 6.20.14+dfsg-2build1 in impish ppc64el
php-illuminate-config 6.20.14+dfsg-2build1 in impish riscv64
php-illuminate-config 6.20.14+dfsg-2build1 in impish s390x
php-illuminate-console 6.20.14+dfsg-2build1 in impish amd64
php-illuminate-console 6.20.14+dfsg-2build1 in impish arm64
php-illuminate-console 6.20.14+dfsg-2build1 in impish armhf
php-illuminate-console 6.20.14+dfsg-2build1 in impish i386
php-illuminate-console 6.20.14+dfsg-2build1 in impish ppc64el
php-illuminate-console 6.20.14+dfsg-2build1 in impish riscv64
php-illuminate-console 6.20.14+dfsg-2build1 in impish s390x
php-illuminate-container 6.20.14+dfsg-2build1 in impish amd64
php-illuminate-container 6.20.14+dfsg-2build1 in impish arm64
php-illuminate-container 6.20.14+dfsg-2build1 in impish armhf
php-illuminate-container 6.20.14+dfsg-2build1 in impish i386
php-illuminate-container 6.20.14+dfsg-2build1 in impish ppc64el
php-illuminate-container 6.20.14+dfsg-2build1 in impish riscv64
php-illuminate-container 6.20.14+dfsg-2build1 in impish s390x
php-illuminate-contracts 6.20.14+dfsg-2build1 in impish amd64
php-illuminate-contracts 6.20.14+dfsg-2build1 in impish arm64
php-illuminate-contracts 6.20.14+dfsg-2build1 in impish armhf
php-illuminate-contracts 6.20.14+dfsg-2build1 in impish i386
php-illuminate-contracts 6.20.14+dfsg-2build1 in impish ppc64el
php-illuminate-contracts 6.20.14+dfsg-2build1 in impish riscv64
php-illuminate-contracts 6.20.14+dfsg-2build1 in impish s390x
php-illuminate-cookie 6.20.14+dfsg-2build1 in impish amd64
php-illuminate-cookie 6.20.14+dfsg-2build1 in impish arm64
php-illuminate-cookie 6.20.14+dfsg-2build1 in impish armhf
php-illuminate-cookie 6.20.14+dfsg-2build1 in impish i386
php-illuminate-cookie 6.20.14+dfsg-2build1 in impish ppc64el
php-illuminate-cookie 6.20.14+dfsg-2build1 in impish riscv64
php-illuminate-cookie 6.20.14+dfsg-2build1 in impish s390x
php-illuminate-database 6.20.14+dfsg-2build1 in impish amd64

[Bug 1931315] Re: Please drop php-laravel-framework (and associated components), and movim from impish

2021-06-11 Thread Steve Langasek
Removing packages from impish:
movim 0.17.1-1.1 in impish
movim 0.17.1-1.1 in impish amd64
movim 0.17.1-1.1 in impish arm64
movim 0.17.1-1.1 in impish armhf
movim 0.17.1-1.1 in impish i386
movim 0.17.1-1.1 in impish ppc64el
movim 0.17.1-1.1 in impish riscv64
movim 0.17.1-1.1 in impish s390x
Comment: blocks php transition; LP: #1931315
1 package successfully removed.


** Changed in: movim (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931315

Title:
  Please drop php-laravel-framework (and associated components), and
  movim from impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/movim/+bug/1931315/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931315] Re: Please drop php-laravel-framework (and associated components), and movim from impish

2021-06-11 Thread Steve Langasek
Removing packages from impish:
php-laravel-lumen-framework 6.3.5-2 in impish
php-laravel-lumen-framework 6.3.5-2 in impish amd64
php-laravel-lumen-framework 6.3.5-2 in impish arm64
php-laravel-lumen-framework 6.3.5-2 in impish armhf
php-laravel-lumen-framework 6.3.5-2 in impish i386
php-laravel-lumen-framework 6.3.5-2 in impish ppc64el
php-laravel-lumen-framework 6.3.5-2 in impish riscv64
php-laravel-lumen-framework 6.3.5-2 in impish s390x
Comment: blocks php transition; LP: #1931315
1 package successfully removed.


** Also affects: php-laravel-lumen-framework (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: php-laravel-framework (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931315

Title:
  Please drop php-laravel-framework (and associated components), and
  movim from impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/movim/+bug/1931315/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931518] Re: grub-efi-amd64-signed 1.167~18.04.1+2.04-1ubuntu44 has broken non-EFI install

2021-06-10 Thread Steve Langasek
It is safe to install on non efi systems, and as shipped, Ubuntu
provides an EFI system partition mounted at /boot/efi.  It appears on
your system this partition is no longer mounted, causing the error.  It
is correct for grub to fail the upgrade rather than leaving the ESP
contents not updated.

If you are not going to have /boot/efi mounted, the other option is to
uninstall shim-signed and grub-efi-amd64-signed; this will prevent you
from transitioning this install to use UEFI in the future.

** Changed in: grub2-signed (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931518

Title:
  grub-efi-amd64-signed 1.167~18.04.1+2.04-1ubuntu44 has broken non-EFI
  install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1931518/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 205254] Re: python-policyd-spf failing on AOL SPF records.

2021-06-08 Thread Steve Langasek
You are responding to a fixed bug from 2008.  Please file a separate bug
report for your issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/205254

Title:
  python-policyd-spf failing on AOL SPF records.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pypolicyd-spf/+bug/205254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931254] Re: Google Confidential Compute fails to boot with 1.47

2021-06-08 Thread Steve Langasek
Per the last comment, if the kernel is panicking, we should look at this
from the kernel side.

** Also affects: linux-gcp (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931254

Title:
  Google Confidential Compute fails to boot with 1.47

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1931254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926748] Re: regression in xenial updates - grub2 cannot handle new arm64 relocations

2021-06-07 Thread Steve Langasek
Hello Dimitri, or anyone else affected,

Accepted grub2-unsigned into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/grub2-unsigned/2.04-1ubuntu44.1.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: grub2-unsigned (Ubuntu Xenial)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926748

Title:
  regression in xenial updates - grub2 cannot handle new arm64
  relocations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930742] Please test proposed package

2021-06-07 Thread Steve Langasek
Hello Steve, or anyone else affected,

Accepted grub2-unsigned into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/grub2-unsigned/2.04-1ubuntu44.1.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930742

Title:
  cloud images in xenial do not get their boot path updated because we
  don't call grub-install --force-extra-removable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915536] Re: one grub

2021-06-07 Thread Steve Langasek
** Changed in: grub2-unsigned (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: grub2-unsigned (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: grub2-unsigned (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915536

Title:
  one grub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921143] Re: efivarfs_set_variable: writing to fd 7 failed: Invalid argument.

2021-06-07 Thread Steve Langasek
** Package changed: grub2-unsigned (Ubuntu) => grub2 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921143

Title:
  efivarfs_set_variable: writing to fd 7 failed: Invalid argument.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1921143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928701] Re: update-grub does not run on kernel updates

2021-06-07 Thread Steve Langasek
*** This bug is a duplicate of bug 1928674 ***
https://bugs.launchpad.net/bugs/1928674

** This bug has been marked a duplicate of bug 1928674
   grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928701

Title:
  update-grub does not run on kernel updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1928701/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926713] Re: package grub-efi-amd64 2.04-1ubuntu44 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 127

2021-06-07 Thread Steve Langasek
> /etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries: 
> libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
> Hittade Windows Boot Manager på /dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi
> dpkg: error processing package grub-efi-amd64 (--configure):
>  installed grub-efi-amd64 package post-installation script subprocess 
> returned error exit status 127

What is /etc/grub.d/bin/grubcfg_proxy?  This file doesn't exist in
Ubuntu.  And you have put it in a path on your system such that you must
be able to execute it in order for update-grub to succeed.

And it depends on an obsolete version of libcrypto.

You will need to fix your local configuration to not be blocked on this
broken, third-party executable.

** Changed in: grub2-unsigned (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926713

Title:
  package grub-efi-amd64 2.04-1ubuntu44 failed to install/upgrade:
  installed grub-efi-amd64 package post-installation script subprocess
  returned error exit status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1926713/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926748] Re: regression in xenial updates - grub2 cannot handle new arm64 relocations

2021-06-07 Thread Steve Langasek
** Also affects: grub2-unsigned (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: grub2-unsigned (Ubuntu)
   Status: New => Invalid

** Also affects: grub2-signed (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: grub2-signed (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926748

Title:
  regression in xenial updates - grub2 cannot handle new arm64
  relocations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922234] Re: Grub doesn't update kernel version

2021-06-07 Thread Steve Langasek
*** This bug is a duplicate of bug 1928674 ***
https://bugs.launchpad.net/bugs/1928674

** This bug has been marked a duplicate of bug 1928674
   grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922234

Title:
  Grub doesn't update kernel version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1922234/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931112] Re: Apple vendor quirk check for LP#1928434 incorrectly fails on all non-DMI hardware

2021-06-07 Thread Steve Langasek
Hello Alyssa, or anyone else affected,

Accepted ubuntu-release-upgrader into hirsute-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:21.04.13 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-release-upgrader (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931112

Title:
  Apple vendor quirk check for LP#1928434 incorrectly fails on all non-
  DMI hardware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931112/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929471] Re: Shim apparently fails to run fwupd64 (hirsute regression?)

2021-06-07 Thread Steve Langasek
** Changed in: shim-signed (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: shim-signed (Ubuntu Hirsute)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929471

Title:
  Shim apparently fails to run fwupd64 (hirsute regression?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1929471/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930939] Re: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1

2021-06-04 Thread Steve Langasek
** Changed in: shim-signed (Ubuntu)
 Assignee: $uperu$er (nozzz) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930939

Title:
  package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade:
  installed shim-signed package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1930939/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable

2021-06-04 Thread Steve Langasek
grub2-unsigned binary copied from bionic-proposed to xenial-proposed.

** Changed in: grub2-unsigned (Ubuntu Xenial)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930742

Title:
  cloud images in xenial do not get their boot path updated because we
  don't call grub-install --force-extra-removable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1928434] Re: shim-signed does not boot on EFI 2.40 by Apple

2021-06-03 Thread Steve Langasek
On Fri, Jun 04, 2021 at 03:11:59AM -, Doug McDonald wrote:
> Does this bug affect ppc64le? It currently prevents do-release-upgrade
> to 21.04 from 20.10.

This bug does not affect ppc64el, but there is no interface for turning on
upgrades on a per-architecture basis.

However, a change has been made to ubuntu-release-upgrader that lets us
block upgrades only for Apple hardware, and upgrades have been turned on for
20.10 to 21.04.  So I'm not sure why you say that it "currently prevents"
it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928434

Title:
  shim-signed does not boot on EFI 2.40 by Apple

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1928434/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable

2021-06-03 Thread Steve Langasek
Because grub-install in bionic and later also defaults to installing to
the removable path, shim-signed in bionic does not need any update for
this; the bionic SRUs of grub are only necessary because grub2-unsigned
is shared between xenial and bionic.

** Changed in: shim-signed (Ubuntu Bionic)
   Status: New => Invalid

** Tags added: regression-update

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930742

Title:
  cloud images in xenial do not get their boot path updated because we
  don't call grub-install --force-extra-removable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable

2021-06-03 Thread Steve Langasek
shim-signed upload is blocked on the availability of a new signed binary
from Microsoft that includes the fix for bug #1928434.  The shim part of
the test case will therefore fail until then, but this should not block
release of the grub fixes.

** Changed in: shim-signed (Ubuntu Xenial)
 Assignee: (unassigned) => Steve Langasek (vorlon)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930742

Title:
  cloud images in xenial do not get their boot path updated because we
  don't call grub-install --force-extra-removable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable

2021-06-03 Thread Steve Langasek
** Changed in: grub2-signed (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: grub2-signed (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: grub2-unsigned (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: grub2-unsigned (Ubuntu Bionic)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930742

Title:
  cloud images in xenial do not get their boot path updated because we
  don't call grub-install --force-extra-removable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable

2021-06-03 Thread Steve Langasek
** Description changed:

  [Impact]
  Verification of the previous SRU, bug #1928674, exposed that we have a 
regression on xenial/arm64 cloud images because they boot from the removable 
media path, which is not updated by the maintainer scripts in those images; and 
because we have never supported the monolithic signed EFI executable on 
xenial/arm64, there is an ABI mismatch between the updated contents of 
/boot/grub and the not-updated contents of \EFI\boot\bootaa64.efi.
  
  The fact that \EFI\boot is not updated on xenial cloud images is ALSO an
  issue on amd64 - it doesn't lead to a boot failure there because we do
  support secureboot on xenial/amd64, so the bootloader doesn't depend on
  loading modules from /boot/grub; however, \EFI\boot not being uploaded
  means that the systems still do not benefit from the updated grub, AND
  are subject to boot failures in the future due to the fact that the old
  shim has been revoked by Microsoft and these revocations may propagate
  to the cloud instance's revocation database in nvram, one way or
  another.
  
  [Test Case]
  - Boot an arm64 Ubuntu image in AWS
  - Enable -proposed
  - Upgrade the grub-efi-amd64 package
  - Reboot
  - Verify that the system comes up
  
  - Boot an amd64 Ubuntu image in GCE
  - rm /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
  - touch /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
  - Enabled -proposed
  - Upgrade the grub-efi-amd64-signed package
  - Reboot
  - Verify that the system comes up
  - rm /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
  - touch /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
  - Upgrade the shim-signed package
  - Reboot
  - Verify that the system comes up
  
  [Where problems could occur]
  Because there were no provisions in the cloud images at the time they were 
built for updates to \EFI\boot, the only practical way to fix this for existing 
images (which is where the upgrade bug is an issue) is by unconditionally 
installing to the removable media path on all systems as part of the upgrade.  
This means that non-cloud systems, which do not normally boot Ubuntu via 
\EFI\boot, will have the contents of \EFI\boot replaced when this was not 
previously the case (and contrary to the debconf setting).  In newer Ubuntu 
releases, we install to \EFI\boot unconditionally; but this is a behavior 
change in a stable series.  If a user has something other than Ubuntu grub+shim 
installed to \EFI\boot, this may be an unexpected behavior change from an SRU.
+ 
+ The risk of this causing a problem for users is mitigated on bionic by
+ the fact that all the most recent install media for Ubuntu 18.04 also
+ install shim+grub to the removable path, so this is already the default
+ behavior.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930742

Title:
  cloud images in xenial do not get their boot path updated because we
  don't call grub-install --force-extra-removable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930694] Re: Hirtute Hippo terminal not working

2021-06-03 Thread Steve Langasek
** Project changed: ubuntu-cdimage => linux-raspi (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930694

Title:
  Hirtute Hippo terminal not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1930694/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable

2021-06-03 Thread Steve Langasek
** Description changed:

  [Impact]
  Verification of the previous SRU, bug #1928674, exposed that we have a 
regression on xenial/arm64 cloud images because they boot from the removable 
media path, which is not updated by the maintainer scripts in those images; and 
because we have never supported the monolithic signed EFI executable on 
xenial/arm64, there is an ABI mismatch between the updated contents of 
/boot/grub and the not-updated contents of \EFI\boot\bootaa64.efi.
  
  The fact that \EFI\boot is not updated on xenial cloud images is ALSO an
  issue on amd64 - it doesn't lead to a boot failure there because we do
  support secureboot on xenial/amd64, so the bootloader doesn't depend on
  loading modules from /boot/grub; however, \EFI\boot not being uploaded
  means that the systems still do not benefit from the updated grub, AND
  are subject to boot failures in the future due to the fact that the old
  shim has been revoked by Microsoft and these revocations may propagate
  to the cloud instance's revocation database in nvram, one way or
  another.
  
  [Test Case]
  - Boot an arm64 Ubuntu image in AWS
  - Enable -proposed
  - Upgrade the grub-efi-amd64 package
  - Reboot
  - Verify that the system comes up
  
- - Boot an amd64 Ubuntu image in AWS
- - rm /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
- - touch /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
- - Enabled -proposed
- - Upgrade the grub-efi-amd64-signed package
- - Reboot
- - Verify that the system comes up
- - rm /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
- - touch /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
- - Upgrade the shim-signed package
- - Reboot
- - Verify that the system comes up
- 
  - Boot an amd64 Ubuntu image in GCE
  - rm /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
  - touch /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
  - Enabled -proposed
  - Upgrade the grub-efi-amd64-signed package
  - Reboot
  - Verify that the system comes up
  - rm /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
  - touch /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
  - Upgrade the shim-signed package
  - Reboot
  - Verify that the system comes up
  
  [Where problems could occur]
  Because there were no provisions in the cloud images at the time they were 
built for updates to \EFI\boot, the only practical way to fix this for existing 
images (which is where the upgrade bug is an issue) is by unconditionally 
installing to the removable media path on all systems as part of the upgrade.  
This means that non-cloud systems, which do not normally boot Ubuntu via 
\EFI\boot, will have the contents of \EFI\boot replaced when this was not 
previously the case (and contrary to the debconf setting).  In newer Ubuntu 
releases, we install to \EFI\boot unconditionally; but this is a behavior 
change in a stable series.  If a user has something other than Ubuntu grub+shim 
installed to \EFI\boot, this may be an unexpected behavior change from an SRU.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930742

Title:
  cloud images in xenial do not get their boot path updated because we
  don't call grub-install --force-extra-removable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable

2021-06-03 Thread Steve Langasek
** Description changed:

  [Impact]
  Verification of the previous SRU, bug #1928674, exposed that we have a 
regression on xenial/arm64 cloud images because they boot from the removable 
media path, which is not updated by the maintainer scripts in those images; and 
because we have never supported the monolithic signed EFI executable on 
xenial/arm64, there is an ABI mismatch between the updated contents of 
/boot/grub and the not-updated contents of \EFI\boot\bootaa64.efi.
  
  The fact that \EFI\boot is not updated on xenial cloud images is ALSO an
  issue on amd64 - it doesn't lead to a boot failure there because we do
  support secureboot on xenial/amd64, so the bootloader doesn't depend on
  loading modules from /boot/grub; however, \EFI\boot not being uploaded
  means that the systems still do not benefit from the updated grub, AND
  are subject to boot failures in the future due to the fact that the old
  shim has been revoked by Microsoft and these revocations may propagate
  to the cloud instance's revocation database in nvram, one way or
  another.
  
  [Test Case]
  - Boot an arm64 Ubuntu image in AWS
  - Enable -proposed
  - Upgrade the grub-efi-amd64 package
  - Reboot
  - Verify that the system comes up
  
  - Boot an amd64 Ubuntu image in AWS
  - rm /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
  - touch /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
  - Enabled -proposed
  - Upgrade the grub-efi-amd64-signed package
  - Reboot
  - Verify that the system comes up
  - rm /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
  - touch /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
  - Upgrade the shim-signed package
  - Reboot
  - Verify that the system comes up
  
+ - Boot an amd64 Ubuntu image in GCE
+ - rm /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
+ - touch /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
+ - Enabled -proposed
+ - Upgrade the grub-efi-amd64-signed package
+ - Reboot
+ - Verify that the system comes up
+ - rm /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
+ - touch /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
+ - Upgrade the shim-signed package
+ - Reboot
+ - Verify that the system comes up
  
  [Where problems could occur]
  Because there were no provisions in the cloud images at the time they were 
built for updates to \EFI\boot, the only practical way to fix this for existing 
images (which is where the upgrade bug is an issue) is by unconditionally 
installing to the removable media path on all systems as part of the upgrade.  
This means that non-cloud systems, which do not normally boot Ubuntu via 
\EFI\boot, will have the contents of \EFI\boot replaced when this was not 
previously the case (and contrary to the debconf setting).  In newer Ubuntu 
releases, we install to \EFI\boot unconditionally; but this is a behavior 
change in a stable series.  If a user has something other than Ubuntu grub+shim 
installed to \EFI\boot, this may be an unexpected behavior change from an SRU.

** Changed in: grub2-signed (Ubuntu Xenial)
 Assignee: (unassigned) => Steve Langasek (vorlon)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930742

Title:
  cloud images in xenial do not get their boot path updated because we
  don't call grub-install --force-extra-removable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930742] [NEW] cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable

2021-06-03 Thread Steve Langasek
Public bug reported:

[Impact]
Verification of the previous SRU, bug #1928674, exposed that we have a 
regression on xenial/arm64 cloud images because they boot from the removable 
media path, which is not updated by the maintainer scripts in those images; and 
because we have never supported the monolithic signed EFI executable on 
xenial/arm64, there is an ABI mismatch between the updated contents of 
/boot/grub and the not-updated contents of \EFI\boot\bootaa64.efi.

The fact that \EFI\boot is not updated on xenial cloud images is ALSO an
issue on amd64 - it doesn't lead to a boot failure there because we do
support secureboot on xenial/amd64, so the bootloader doesn't depend on
loading modules from /boot/grub; however, \EFI\boot not being uploaded
means that the systems still do not benefit from the updated grub, AND
are subject to boot failures in the future due to the fact that the old
shim has been revoked by Microsoft and these revocations may propagate
to the cloud instance's revocation database in nvram, one way or
another.

[Test Case]
- Boot an arm64 Ubuntu image in AWS
- Enable -proposed
- Upgrade the grub-efi-amd64 package
- Reboot
- Verify that the system comes up

- Boot an amd64 Ubuntu image in AWS
- rm /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
- touch /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
- Enabled -proposed
- Upgrade the grub-efi-amd64-signed package
- Reboot
- Verify that the system comes up
- rm /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
- touch /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi
- Upgrade the shim-signed package
- Reboot
- Verify that the system comes up


[Where problems could occur]
Because there were no provisions in the cloud images at the time they were 
built for updates to \EFI\boot, the only practical way to fix this for existing 
images (which is where the upgrade bug is an issue) is by unconditionally 
installing to the removable media path on all systems as part of the upgrade.  
This means that non-cloud systems, which do not normally boot Ubuntu via 
\EFI\boot, will have the contents of \EFI\boot replaced when this was not 
previously the case (and contrary to the debconf setting).  In newer Ubuntu 
releases, we install to \EFI\boot unconditionally; but this is a behavior 
change in a stable series.  If a user has something other than Ubuntu grub+shim 
installed to \EFI\boot, this may be an unexpected behavior change from an SRU.

** Affects: grub2-signed (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: grub2-unsigned (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: shim-signed (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: grub2-signed (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: grub2-unsigned (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: shim-signed (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: grub2-signed (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: grub2-unsigned (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: shim-signed (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: grub2-signed (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: shim-signed (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: shim-signed (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: shim-signed (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: grub2-signed (Ubuntu)
   Status: New => Invalid

** Changed in: grub2-unsigned (Ubuntu)
   Status: New => Invalid

** Changed in: shim-signed (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930742

Title:
  cloud images in xenial do not get their boot path updated because we
  don't call grub-install --force-extra-removable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

2021-06-03 Thread Steve Langasek
And: agreed that the current bug is verified for xenial now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928674

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

2021-06-03 Thread Steve Langasek
Although amd64 cloud images don't fail to boot after the upgrade, we've
determined that the same fundamental problem - that the contents of the
removable path are not updated on grub upgrade - also affects
amd64/xenial.  This means that all xenial cloud images, whether the
update is installed or not, will not be *booting* the binary that has
the security fixes.

So we need to fix this for both amd64 and arm64 in xenial by having it
--force-extra-removable unconditionally on upgrade.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928674

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930633] Re: Existing EFI Boot partition for Windows 10 not detected by Ubuntu 21.04 install!

2021-06-02 Thread Steve Langasek
unfortunately, I can see nothing in the logs attached which would
explain this failure.  To the contrary, the logs clearly show that
partman correctly detects /dev/sda1 as an ESP.  There are exceptions
from ubiquity in the syslog, but they appear to be unrelated.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930633

Title:
  Existing EFI Boot partition for Windows 10 not detected by Ubuntu
  21.04 install!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1930633/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925529] Update Released

2021-06-02 Thread Steve Langasek
The verification of the Stable Release Update for ubuntu-release-
upgrader has completed successfully and the package is now being
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925529

Title:
  "ReleaseNotesViewer" does not display anything with the text view

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1925529/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929449] Update Released

2021-06-02 Thread Steve Langasek
The verification of the Stable Release Update for ubuntu-release-
upgrader has completed successfully and the package is now being
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929449

Title:
  do not allow upgrades to hirsute for Apple hardware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1929449/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928434] Re: shim-signed does not boot on EFI 2.40 by Apple

2021-06-02 Thread Steve Langasek
Thanks so much for the quick turnaround!  We'll make sure this gets
submitted to Microsoft for signing ASAP so we can get the fix into 21.04
for all users.

** Changed in: shim-signed (Ubuntu)
   Status: Incomplete => In Progress

** Changed in: shim (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928434

Title:
  shim-signed does not boot on EFI 2.40 by Apple

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1928434/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928434] Re: shim-signed does not boot on EFI 2.40 by Apple

2021-06-02 Thread Steve Langasek
Kris, we would appreciate if you could run the above test as requested
by Julian and let us know if it boots on your system.  We take boot
regressions seriously and have put upgrades to 21.04 on hold for all
users while this bug remains unresolved, but it's important to be able
to close this bug out so that we can turn those upgrades back on.  Once
we have confirmation of a fixed shim, this will also need to publish
this to all stable releases, because Microsoft has already issued
revocations of our older shims.  Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928434

Title:
  shim-signed does not boot on EFI 2.40 by Apple

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1928434/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930433] Re: UEFI doesn't load fwupd on Lenovo X1 Carbon 7th

2021-06-01 Thread Steve Langasek
*** This bug is a duplicate of bug 1929471 ***
https://bugs.launchpad.net/bugs/1929471

** This bug has been marked a duplicate of bug 1929471
   Shim apparently fails to run fwupd64 (hirsute regression?)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930433

Title:
  UEFI doesn't load fwupd on Lenovo X1 Carbon 7th

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1930433/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929471] Re: Shim apparently fails to run fwupd64 (hirsute regression?)

2021-06-01 Thread Steve Langasek
** Also affects: fwupd (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929471

Title:
  Shim apparently fails to run fwupd64 (hirsute regression?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1929471/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2021-05-30 Thread Steve Langasek
** Changed in: ubuntu-cdimage
 Assignee: GEO (geo218) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871268

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929830] Re: RM dahdi-linux hardware and upstream do not exist for years

2021-05-28 Thread Steve Langasek
Based on the last comment it doesn't appear there's any current action
for ubuntu-archive; unsubscribing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929830

Title:
  RM dahdi-linux hardware and upstream do not exist for years

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1929830/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1785383] Re: missing EDNS0 record confuses systemd-resolved

2021-05-28 Thread Steve Langasek
marking incomplete for hirsute based on Brian's comment above.

** Changed in: systemd (Ubuntu Hirsute)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785383

Title:
  missing EDNS0 record confuses systemd-resolved

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1785383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1664844] Re: No distinction between link-up and link-down interfaces

2021-05-28 Thread Steve Langasek
** Description changed:

  [Impact]
  
  Since very long, we had a feature request in netplan to determine the
  activation mode of a given network interface. We got requests to enable
  marking some interfaces as 'manual', meaning that networkd (or any other
  backend) would not control its state in any way, requiring the
  administrator to bring the interface up or down manually. The other
  request was to mark a interface as 'off', that is: forcing the network
  interface to always be down until the configuration option isn't
  changed.
  
  This was mainly requested for the networkd backend and requires the new
  feature of specifying ActivationPolicy= for interfaces, alongside the
  required netplan changes.
  
  This feature is present in systemd 248 - for netplan supported stable
  series we have decided to cherry-pick and backport this feature on top
  of current systemd. The networkd feature basically adds the following 5
  ActivationPolicy modes: always-down, down, manual, up, always-up. For
  netplan purposes we only use 'always-down' and 'manual'.
  
  The netplan feature, hopefully landing as part of 0.103, is called
  'activation-mode' and supports two values: 'manual' and 'off'.
  
  [Test Case]
  
  For the systemd part:
  
   * Bring up a VM test environment with either a dummy interface or an 
interface that can be safely manipulated.
   * Upgrade systemd to the -proposed version
   * For the target interface, create/modify the networkd configuration to 
include the ActivationPolicy= setting in [Link], for instance:
  
  [Match]
  Name=dummy0
  
  [Network]
  Address=192.168.10.30/24
  Gateway=192.168.10.1
  
  [Link]
  ActivationPolicy=manual
  
   * Try all 5 combinations of ActivationPolicy values: always-down, down,
  manual, up, always-up - doing `sudo networkctl reload` everytime and
  checking if the interface behaves as expected.
  
  [Where problems could occur]
  
  The patchset modifies quite a lot of code in the networkd link handling
  code paths, so regressions could appear in how networkd manages links -
  maybe by suddenly certain interfaces not getting brought up as they were
- before.
+ before.  By code inspection, the implementation defaults to
+ ACTIVATION_POLICY_UP as the default, equivalent to the current behavior,
+ so this risk is small.
  
  ---
  
  [Original Description]
  
  [Old Impact]
  Users need to write valid configuration, especially for new features that are 
approved by not yet implemented, such as marking a link "optional".
  
  [Old Test case]
  Write a netplan configuration:
  
  network:
    version: 2
    renderer: networkd
    ethernets:
  eth0:
    optional: yes
    dhcp4: yes
  
  And run 'netplan apply'. Netplan should write configuration for the link
  and not error out with a syntax error.
  
  [Old Regression potential]
  This has a minimal potential for regression: the new keyword was added to be 
supported already by consumers of netplan (users, cloud-init) so that they 
could start writing config with the new key and that configuration to be seen 
as valid by netplan before the backend is implemented. There is no functional 
change besides allowing for the value to exist in a netplan configuation.
  
  ---
  
  If I define an interface in netplan (even one which has no DHCP type and
  no addresses), it's not possible to determine if its adminStatus should
  be enabled (link up) or disabled (link down).
  
  I can completely exclude an interface from the netplan configuration,
  but I think that implies that not only its adminStatus is "disabled" by
  default, but also netplan will not be able to do anything "nice" for the
  interface, such as rename it to what the user specified in MAAS.
  
  If I include the interface but don't specify any addresses or DHCP, it
  isn't clear if it will be link up (my current assumption) or link down.
  
  There should be a way to allow an interface to be recognized by netplan
  (and even partially configured, waiting for the user to run something
  like 'ifup ' on a manual but not auto-started interface in
  ifupdown), but marked administratively disabled. (adminStatus down)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664844

Title:
  No distinction between link-up and link-down interfaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1664844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly

2021-05-28 Thread Steve Langasek
+   case EROFS:
+   ignore_failure = true;
+   xwarn(_("setting key \"%s\"%s"), outname, 
(ignore_failure?_(", ignoring"):""));
+   break;
default:
xwarn(_("setting key \"%s\"%s"), outname, 
(ignore_failure?_(", ignoring"):""));
break;

Instead of reproducing the xwarn() call, I believe this should be:

+   case EROFS:
+   ignore_failure = true;
default:
xwarn(_("setting key \"%s\"%s"), outname, 
(ignore_failure?_(", ignoring"):""));
break;

I would prefer to see this reconciled before proceeding with the SRU.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903351

Title:
  ignore_eacces and ignore_erofs patches don't work properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929921] Re: Ubuntu 20.04.2 - OPENSSL_cleanse() fails with segmentation fault in eddsa_test

2021-05-28 Thread Steve Langasek
** Changed in: ubuntu-z-systems
   Status: New => Invalid

** Changed in: linux (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929921

Title:
  Ubuntu 20.04.2 - OPENSSL_cleanse() fails with segmentation fault in
  eddsa_test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929921/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929454] Re: Bios measurements do not contain measurements for the kernel binary and kernel signer cert.

2021-05-25 Thread Steve Langasek
** Changed in: shim-signed (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929454

Title:
  Bios measurements do not contain measurements for the kernel binary
  and kernel signer cert.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1929454/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1929454] Re: Bios measurements do not contain measurements for the kernel binary and kernel signer cert.

2021-05-24 Thread Steve Langasek
On Mon, May 24, 2021 at 11:30:09PM -, VINAY RAJESH wrote:
> What about the scenario where the signers are different for kernel and
> grub? For example, if the kernel is signed using a self signed cert and
> loaded using MOK.

> I am trying to do that right now but the kernel fails to load when
> signed with a MOK key.

In that case, yes, the key in mok used for signing the kernel is supposed to
be measured in addition to the key used for signing grub.  But it sounds
like you're not getting to that point yet, if your kernel fails to load.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929454

Title:
  Bios measurements do not contain measurements for the kernel binary
  and kernel signer cert.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1929454/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929454] Re: Bios measurements do not contain measurements for the kernel binary and kernel signer cert.

2021-05-24 Thread Steve Langasek
> On Ubuntu 20.04, the binary_bios_measurements
> do NOT contain the measurements for the kernel
> binary and the kernel signer cert that is
> typically measured by the shim.

It is my understanding that it is correct to not measure the certificate
for the kernel: per the specs, because grub and the kernel are signed
with keys that chain back to the same cert trusted by shim, this
certificate should only be measured once.  There were bugs in earlier
versions of shim that have since been fixed.

I do not recall if there were reasons to stop measuring the hash of the
kernel, or to change where it is measured.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929454

Title:
  Bios measurements do not contain measurements for the kernel binary
  and kernel signer cert.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1929454/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

2021-05-24 Thread Steve Langasek
Since focal and groovy are no-change uploads, it is sufficient to smoke
test these by showing that they still boot.

I've done this for both focal and groovy on amd64 and the systems still
boot.

** Tags removed: verification-needed-focal verification-needed-groovy
** Tags added: verification-done-focal verification-done-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928674

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929297] Re: Ubuntu Server x86 18.04 installation crashes within seconds

2021-05-24 Thread Steve Langasek
You are reporting that this is a bug when installing Ubuntu Server, but
the information attached to this bug points to ubiquity, which is a
desktop-only installer.

The report also shows that usr/bin/ubiquity
usr/share/ubiquity/plugininstall.py from the ubiquity package are
modified, which would make this unsupported.  Why are those files
modified?

You would also need to expand on what you mean by "crashes" in order for
this bug to be actionable.

** Changed in: ubiquity (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929297

Title:
  Ubuntu Server x86 18.04 installation crashes within seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1929297/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915571] Re: Cannot start bash session for buildd vm images in LXD vm

2021-05-21 Thread Steve Langasek
Is the patch for xenial still relevant? xenial has reached end of
standard support and final images are being rolled.  Do we need another
buildd vm image for 16.04?

** Changed in: livecd-rootfs (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: livecd-rootfs (Ubuntu Xenial)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915571

Title:
  Cannot start bash session for buildd vm images in LXD vm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1915571/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter

2021-05-21 Thread Steve Langasek
Ok, that log file shows no changes to the shim-signed package version
installed.

There is an update to grub, which would trigger re-running grub-install,
which would install the current shimx64.efi to your ESP.

I don't know why you would not have had an up-to-date shimx64.efi on
your system previously, unless you had manually changed the contents of
the ESP.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092

Title:
  Failed to set MokListRT: Invalid Parameter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928942] Re: grub-install: error: failed to register the EFI boot entry: Operation not permitted

2021-05-21 Thread Steve Langasek
** Package changed: grub (Ubuntu) => grub2 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928942

Title:
  grub-install: error: failed to register the EFI boot entry: Operation
  not permitted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928942/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929112] Re: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: »installiertes shim-signed-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück

2021-05-21 Thread Steve Langasek
*** This bug is a duplicate of bug 1928352 ***
https://bugs.launchpad.net/bugs/1928352

** This bug has been marked a duplicate of bug 1928352
   package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed 
shim-signed package post-installation script subprocess returned error exit 
status 1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929112

Title:
  package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade:
  »installiertes shim-signed-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1929112/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929201] Re: Packages in PPA are not installed if version higher than in a release pocket

2021-05-21 Thread Steve Langasek
(If so, I don't think this is a livecd-rootfs bug; livecd-rootfs
shouldn't be expected to override the archives wrt Task fields)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929201

Title:
  Packages in PPA are not installed if version higher than in a release
  pocket

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1929201/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929201] Re: Packages in PPA are not installed if version higher than in a release pocket

2021-05-21 Thread Steve Langasek
Is this perhaps because the packages in the ppa have no Task fields set?
Which can be addressed by setting them manually with XB-Task: in
debian/control.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929201

Title:
  Packages in PPA are not installed if version higher than in a release
  pocket

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1929201/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter

2021-05-21 Thread Steve Langasek
Please show logs (/var/log/apt/history.log) showing what versions of
shim-signed you had installed before and after the problem started.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092

Title:
  Failed to set MokListRT: Invalid Parameter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter

2021-05-21 Thread Steve Langasek
> I am getting the same error after an update to Ubuntu 18.04

After updating from what to what?  There have not been any updates to
the shim-signed package in 18.04 since September of last year.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092

Title:
  Failed to set MokListRT: Invalid Parameter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

2021-05-20 Thread Steve Langasek
Xenial: server install from ubuntu-16.04.7-server-amd64.iso. Security
updates applied by d-i, including grub-efi-amd64 2.04-1ubuntu44.
/etc/kernel/post{inst,rm}.d/zz-update-grub are not present, as with
bionic.

grub-pc is not installed.

Enabled -proposed in sources.list.

sudo apt install grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed

/etc/kernel/post{inst,rm}.d/zz-update-grub now exist as expected

sudo apt dist-upgrade to install 4.4.0-210-generic kernel from xenial-
proposed (along with other random bits)

Inspecting /boot/grub/grub.cfg shows references to -210-.

Rebooting, and uname shows -210- is booted.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928674

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

2021-05-20 Thread Steve Langasek
Bionic: server install from ubuntu-18.04.5-live-server-amd64.iso.
Security updates applied by subiquity, including grub-efi-amd64
2.04-1ubuntu44.  /etc/kernel/post{inst,rm}.d/zz-update-grub are not
present (to my surprise - then I worked out this was because grub wasn't
installed in the source squashfs, so this was a new install of the
package from -security rather than an upgrade).

grub-pc is not installed.

Enabled -proposed in sources.list.

sudo apt install grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed

/etc/kernel/post{inst,rm}.d/zz-update-grub now exist as expected

sudo apt dist-upgrade to install 4.15.0-144-generic kernel from bionic-
proposed (along with other random bits)

Inspecting /boot/grub/grub.cfg shows references to -144-.

Rebooting, and uname shows -144- is booted.

Disabled -proposed again.

sudo do-release-upgrade to focal, to my surprise, does not fail with
conffile conflicts when -proposed is disabled.  However, it does fail to
upgrade grub-efi-amd64* due to focal-updates having an earlier version
than bionic-proposed.

$ dpkg -S /etc/kernel/postinst.d/zz-update-grub
grub2-common: /etc/kernel/postinst.d/zz-update-grub
$

I do not understand what's happening here with the silent takeover of
the conffiles without an explicit Replaces allowing this; this is not
how I understood dpkg to behave.

I think this is verification-done for bionic and verification-failed for grub2 
in focal (which should be withdrawn).
I do not understand what's happening with the conffile being 

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928674

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915571] Re: Cannot start bash session for buildd vm images in LXD vm

2021-05-20 Thread Steve Langasek
** Changed in: livecd-rootfs (Ubuntu Focal)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915571

Title:
  Cannot start bash session for buildd vm images in LXD vm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1915571/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915571] Re: Cannot start bash session for buildd vm images in LXD vm

2021-05-20 Thread Steve Langasek
** Changed in: livecd-rootfs (Ubuntu Groovy)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915571

Title:
  Cannot start bash session for buildd vm images in LXD vm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1915571/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

2021-05-20 Thread Steve Langasek
** Description changed:

  [Impact]
  
   * /etc/kernel/{postinst.d,postrm.d}/zz-update-grub missing on arm64
  with grub-efi-arm64 (a dependency of grub-efi-arm64-signed) installed
  
   * /etc/kernel/{postinst.d,postrm.d}/zz-update-grub missing on amd64
  with grub-efi-amd64 (an ORed dependency of grub-efi-amd64-signed)
  installed.
  
   * This results in newly installed kernels not getting added to grub.cfg
  and thus upon reboot one does not boot into the new kernel.
  
   * In later series these scripts moved to grub2-common, which is why
  they are absent in the backported grub-efi-* packages.  They should be
  restored to these packages in the backport.
  
  [Test Plan]
- 
+  * install grub packages from -updates
+  * ensure that /etc/kernel/post{inst,rm}.d/zz-update-grub are absent; if 
necessary, remove them
   * Install new grubs
- 
-  * If testing on amd64 ensure that grub-efi-amd64 is installed, not
- grub-pc.
- 
+  * If testing on amd64 ensure that grub-efi-amd64 is installed, not grub-pc.
   * Install a new kernel that was not installed before
- 
   * Observe that grub.cfg is regenerated and new kernel is present
- 
   * Remove an old kernel
- 
-  * Observe that grub.cfg is regenerated and new kernel is removed from
- grub.cfg
- 
-  * From bionic, verify that a dist-upgrade to focal works without
- conflicts.
+  * Observe that grub.cfg is regenerated and new kernel is removed from 
grub.cfg
+  * From bionic, verify that a dist-upgrade to focal works without conflicts.
  
  [Where problems could occur]
  
   * These are conffiles. Although nobody should modify them, care should
  be taken when moving conffiles around.
  
  [Other Info]
  
   * First reported by klebers

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928674

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

2021-05-20 Thread Steve Langasek
** Changed in: grub2 (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928674

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

2021-05-20 Thread Steve Langasek
technically, the replaces in groovy and hirsute are incomplete; however,
we don't support direct upgrades from bionic to any release later than
focal, so this is not worth SRUing.

** Changed in: grub2 (Ubuntu Groovy)
   Status: New => Won't Fix

** No longer affects: grub2 (Ubuntu Hirsute)

** No longer affects: grub2-signed (Ubuntu Hirsute)

** No longer affects: grub2-unsigned (Ubuntu Hirsute)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928674

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   5   6   7   8   9   10   >