[Bug 1888241] Re: OEM metapackages added after the ISO was created are not found by the installer

[Iain Lane]

** Description changed:

  [ Description ]
  
  If a piece of hardware is enabled after the latest Ubuntu release is
  created, it is not found by the installer and so people who install
  Ubuntu do not get its extra hardware enablement.
  
  The information the installer needs to know about hardware enablement is
  represented in the Ubuntu archive by "OEM enablement metapackages"; that
  is, packages called oem-*-meta which the installer can match (via
  modaliases) to the running hardware. After release, these are SRUed into
  -updates more or less as normal. The installer needs to 'apt update'
  before running 'ubuntu-drivers list-oem' to learn the latest state.
  
  [ QA ]
  
  1. Boot the focal release live session on a newly-enabled SKU.
  2. *Without updating the apt indexes*, install this SRU, i.e. download it and use "dpkg -i".
  
  [[ QA 1 ]]
  3. Try to install normally. Get online when the wifi page prompts you to. Make sure that the oem-<sku>-meta package is installed.
  
  [[ QA 2 ]]
  3. Do not connect to the internet. Make sure that the install completes (OEM enablement packages will not be installed; work to do this in the session coming soon).
  
  [[ QA 3 ]]
  3. Connect to the internet before launching the installer. Make sure that the oem-<sku>-meta package gets installed.
  
  [[ QA 4 ]]
  
  This one can be done on a non-OEM device. Here we're checking that the
  'apt update' didn't mess things up.
  
  3. Uncheck 'download updates while installing Ubuntu' and ensure that
  it's respected, i.e. that the installed system still offers all the SRUs
  as updates.
  
+ [[ QA 5 ]]
+ 
+ 3. Check the KDE installer still works, i.e. do this on Kubuntu.
+ 
  [ Regression potential ]
  
  This now more-or-less unconditionally runs the equivalent of 'apt
  update' from the installer.
  
  1. It'll slow down the install a bit. But shouldn't be too bad, since
  only post-release pockets will have changed. If you're online before you
  start ubiquity it will be less noticable since it is done in the
  background. If you get online from the installer then there will be a
  short delay.
  
  2. Perhaps some part of the installer gets sad or installs the wrong
  thing if you've update the apt indexes. We have a check box 'download
  updates while installing ubuntu' that should still be respected.

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

Title:
  OEM metapackages added after the ISO was created are not found by the
  installer

Status in ubiquity package in Ubuntu:
  New
Status in ubiquity source package in Focal:
  New

Bug description:
  [ Description ]

  If a piece of hardware is enabled after the latest Ubuntu release is
  created, it is not found by the installer and so people who install
  Ubuntu do not get its extra hardware enablement.

  The information the installer needs to know about hardware enablement
  is represented in the Ubuntu archive by "OEM enablement metapackages";
  that is, packages called oem-*-meta which the installer can match (via
  modaliases) to the running hardware. After release, these are SRUed
  into -updates more or less as normal. The installer needs to 'apt
  update' before running 'ubuntu-drivers list-oem' to learn the latest
  state.

  [ QA ]

  1. Boot the focal release live session on a newly-enabled SKU.
  2. *Without updating the apt indexes*, install this SRU, i.e. download it and use "dpkg -i".

  [[ QA 1 ]]
  3. Try to install normally. Get online when the wifi page prompts you to. Make sure that the oem-<sku>-meta package is installed.

  [[ QA 2 ]]
  3. Do not connect to the internet. Make sure that the install completes (OEM enablement packages will not be installed; work to do this in the session coming soon).

  [[ QA 3 ]]
  3. Connect to the internet before launching the installer. Make sure that the oem-<sku>-meta package gets installed.

  [[ QA 4 ]]

  This one can be done on a non-OEM device. Here we're checking that the
  'apt update' didn't mess things up.

  3. Uncheck 'download updates while installing Ubuntu' and ensure that
  it's respected, i.e. that the installed system still offers all the
  SRUs as updates.

  [[ QA 5 ]]

  3. Check the KDE installer still works, i.e. do this on Kubuntu.

  [ Regression potential ]

  This now more-or-less unconditionally runs the equivalent of 'apt
  update' from the installer.

  1. It'll slow down the install a bit. But shouldn't be too bad, since
  only post-release pockets will have changed. If you're online before
  you start ubiquity it will be less noticable since it is done in the
  background. If you get online from the installer then there will be a
  short delay.

  2. Perhaps some part of the installer gets sad or installs the wrong
  thing if you've update the apt indexes. We have a check box 'download
  updates while installing ubuntu' that should still be respected.

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