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

[Iain Lane]

Uploaded.

** Description changed:

+ [ 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.

-- 
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:
  In Progress
Status in update-notifier source package in Focal:
  In Progress

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