| 2020-07-20 15:14:59 |
Iain Lane |
bug |
|
|
added bug |
| 2020-07-20 15:15:11 |
Iain Lane |
nominated for series |
|
Ubuntu Focal |
|
| 2020-07-20 15:15:11 |
Iain Lane |
bug task added |
|
ubiquity (Ubuntu Focal) |
|
| 2020-07-20 15:42:07 |
Iain Lane |
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.
[ 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. |
[ 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. |
|
| 2020-07-21 13:40:31 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~laney/ubiquity/+git/ubiquity/+merge/387747 |
|
| 2020-07-21 13:50:49 |
Iain Lane |
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. |
[ 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 ]]
3. Connect to the internet when prompted. Uncheck 'download updates while installing Ubuntu' and ensure that the OEM meta package gets installed.
[[ QA 5 ]]
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 6 ]]
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. |
|
| 2020-07-21 16:31:47 |
Brian Murray |
ubiquity (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2020-07-21 16:31:49 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-07-21 16:31:53 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2020-07-21 16:31:56 |
Brian Murray |
tags |
|
verification-needed verification-needed-focal |
|
| 2020-07-21 17:36:33 |
Iain Lane |
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 ]]
3. Connect to the internet when prompted. Uncheck 'download updates while installing Ubuntu' and ensure that the OEM meta package gets installed.
[[ QA 5 ]]
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 6 ]]
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. |
[ 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** (20.04.0) live session on a newly-enabled SKU **which has its oem-meta package in focal-updates**.
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 ]]
3. Connect to the internet when prompted. Uncheck 'download updates while installing Ubuntu' and ensure that the OEM meta package gets installed.
[[ QA 5 ]]
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 6 ]]
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. |
|
| 2020-07-22 05:29:36 |
Launchpad Janitor |
ubiquity (Ubuntu): status |
New |
Fix Released |
|
| 2020-07-22 09:49:06 |
Shih-Yuan Lee |
attachment added |
|
syslog https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1888241/+attachment/5394843/+files/syslog |
|
| 2020-07-22 09:59:29 |
Shih-Yuan Lee |
tags |
verification-needed verification-needed-focal |
verification-failed verification-failed-focal |
|
| 2020-07-23 08:32:32 |
Iain Lane |
bug |
|
|
added subscriber Shih-Yuan Lee |
| 2020-07-23 14:58:24 |
Shih-Yuan Lee |
tags |
verification-failed verification-failed-focal |
verification-needed verification-needed-focal |
|
| 2020-07-23 16:56:37 |
Dimitri John Ledkov |
tags |
verification-needed verification-needed-focal |
verification-done verification-done-focal |
|
| 2020-07-23 17:04:18 |
Launchpad Janitor |
ubiquity (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-07-23 17:04:24 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-01-19 13:55:31 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~mfo/ubiquity/+git/ubiquity/+merge/396499 |
|
