[Merge] ~paelzer/ubuntu-seeds/+git/ubuntu:eoan-server-meta-updates into ~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu:eoan

[Christian Ehrhardt ]

Non x86 is interesting but not too complex I'd think.

fwupd works there as well, no matter if it today might not provide anything reasonable to update.
I'd still make the package available for the infrastructure.

fwupd-signed is different, that does not exist for non EFI as you'd expect.

fwupd        | 1.2.6-1ubuntu1     | eoan | amd64, arm64, armhf, i386, ppc64el, s390x
fwupd-signed | 1.7+1.2.6-1ubuntu1 | eoan | amd64, arm64, armhf, i386

But in fact apt would resolve all that for us.
$ apt-cache show fwupd | grep '^Recommend'
  Recommends: python3, bolt, fwupd-signed

It will pull in -signed for us "if available" and it will not fail if not available.

$ sudo apt install fwupd
[...]
The following NEW packages will be installed:
  bolt fwupd libfwupd2 libgcab-1.0-0 libgusb2 libxmlb1

A direct install would fail as expected:
$ sudo apt install fwupd-signed
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package fwupd-signed is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'fwupd-signed' has no installation candidate



So the solution is easy - we only seed (still as recommends) fwupd and it will drag in fwupd-signed where appropriate.

Making that change and answering the next question in an extra update for more readability.
-- 
https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/ubuntu/+merge/367238
Your team Ubuntu Core Development Team is subscribed to branch ~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu:eoan.