[Bug 1912496] Re: update-notifier-common pulls in ubuntu-drivers-common including on server where it is not required

Launchpad Bug Tracker 1912496 at bugs.launchpad.net
Thu Jan 21 00:53:36 UTC 2021


This bug was fixed in the package update-notifier - 3.192.38

---------------
update-notifier (3.192.38) hirsute; urgency=medium

  * control: Move ubuntu-drivers-common dep to update-notifier. It's only
    needed when launching update-manager, which happens from
    /usr/bin/update-notifier which is in the update-notifier package. Having
    it in update-notifier-common causes ubuntu-drivers-common and all its deps
    to be pulled in on all flavours, even ones without update-manager. (LP:
    #1912496)

 -- Iain Lane <iain.lane at canonical.com>  Wed, 20 Jan 2021 16:42:37 +0000

** Changed in: update-notifier (Ubuntu)
       Status: In Progress => Fix Released

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

Title:
  update-notifier-common pulls in ubuntu-drivers-common including on
  server where it is not required

Status in update-notifier package in Ubuntu:
  Fix Released
Status in update-notifier source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  update-notifier 3.192.37 (https://git.launchpad.net/ubuntu/+source
  /update-notifier/commit/?id=f766bda4ab5032a5af84311fabd2e6d9e56b3254)
  added a dependency on ubuntu-drivers-common, which causes ubuntu-
  server to bloat, for example by pulling in alsa-utils.

  [ Fix ]

  Move the dependency to update-notifier, which contains /usr/bin
  /update-notifier and also the dependency on update-manager, which is
  launched after we run the script which uses ubuntu-drivers-common.

  [ QA ]

  1. Make sure ubuntu-drivers-common isn't on the referenced server image.
  2. Make sure it is still on images where update-notifier is installed.

  [ Where problems could occur ]

  If we lose the dependency, then update-manager will not be able to
  auto launch, since we require it to be available to run a script
  before auto launching.

  [ Original description ]

  I don't know if there's an easy solution to this, or if we just need
  to live with it. If the latter, this bug can be Won't Fix'd.

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



More information about the foundations-bugs mailing list