[Bug 1749774] Re: include fwupd packages in Server Seed

Christian Ehrhardt  1749774 at bugs.launchpad.net
Fri May 10 06:07:40 UTC 2019


Thanks Steve for the ping for awareness!

It still all is in main, and I checked the old MIR bug 1536871 for any
extra context that might have been mentioned there.

It already is in desktop-common (and due to that in all desktop tasks).
It is there as recommends which I appreciate for the rare case that someone really runs into issues due to the package.

It also is in system-image for ubuntu core.

And finally it also is in d-i-requirements for being on the disk image
if needed by d-i.

---


I checked in a XLD container and a cloud image with only main enabled that we can install it and how much "extra" that would be on small server instances.

It is 13.9 MB extracted and 3742 kB of archives which seems ok space-
wise.

The content will be:
- a bunch of libs (ok)
- a bunch of glib-* packages (still sort of ok)
- dconf-service and some related dbus things (dbus runs anyway, just one more endpoint)
- bolt (system daemon to manage thunderbolt 3 devices)
  That service seems well isolated and only runs if thunderbolt are found (udev)

---

Overall I agree that it makes sense to add this to the server meta task
as well, but also as recommends for some flexibility where needed.

Since version 1.1.0 the requested fwupdate no more is important, but fwupd+fwupd-signed are.
So we use those as recommends.

I prepared a seed change and will propose it for a second Team pair of
eyes to commit

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

Title:
  include fwupd packages in Server Seed

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  fwupd is the closest we have to a standard mechanism currently for
  doing in-band firmware updates in a vendor agnostic way.  As long as
  the vendors provide firmware blobs in an appropriately formatted
  package, fwupd (or fwupdate) can install those firmware blobs from
  within Ubuntu.

  Because of this, we should include the related packages in the server
  seed.  The main components all live in Main currently.  As far as I
  can tell (verified on a Bionic install), nothing in the current server
  seed pulls in fwupd, fwupdate, or fwupdate-signed as a dependency.

  ubuntu at xwing:~$ apt-cache policy fwup*

  fwupdate:
    Installed: (none)
    Candidate: 10-2
    Version table:
       10-2 500
          500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  fwupd:
    Installed: (none)
    Candidate: 1.0.4-3build1
    Version table:
       1.0.4-3build1 500
          500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  fwupdate-signed:
    Installed: (none)
    Candidate: 1.17+10-2
    Version table:
       1.17+10-2 500
          500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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



More information about the foundations-bugs mailing list