[MIR][jammy] oem-sutton-abishag-meta

[OEM Taipei Bot]

[Background]

Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

[Impact]

 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
 2. The background and impact of the situation for this change, and it's impact.

[Testing]

 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the hardware
 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

[Regression Potential]

Most potential regressions will live in the package set that will be installed via dependency of this package, which live in OEM archive (outside of Ubuntu) and control by OEM team. OEM team and other corresponding team need take responsibility of those dependency installed.

[When switching kernel flavour] Check that the new kernel flavour works on the target platform.

[Availability]
This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
The source code of the oem-sutton-abishag-meta for jammy:
    git clone -b abishag-jammy-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

[Rationale]
We want to improve the hardware support for some Lenovo platforms.

[Security]
No CVE/known security issue.

[Quality assurance]
I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
oem-sutton-abishag-meta will be upgraded to 22.04ubuntu1 or the later version from OEM archive.

[Dependencies]
It only depends on ubuntu-oem-keyring.

[Standards compliance]
This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

[Maintenance]
Canonical OEM Enablement Team will take care of the maintenance.

[Background information]
Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to verify this MIR against the reference package in the archive.

https://ubuntu.com/certified/202303-31377
https://ubuntu.com/certified/202304-31446

[Bin Li (binli)]

Attach oem-sutton-abishag-meta_22.04~ubuntu1.debdiff by oem-scripts 1.82.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "oem-sutton-abishag-meta_22.04~ubuntu1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

[Lukas Märdian (slyon)]

Thank you for the git repository. I uploaded this into Jammy/NEW after confirming it follow the process and structure described in: https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM

https://launchpad.net/ubuntu/jammy/+queue?queue_state=0&queue_text=oem-

Once accepted into the archive, this bug report needs to be moved to the corresponding package name "oem-sutton-abishag-meta", instead of the "Ubuntu" bug task.

[Shih-Yuan Lee (fourdollars)]

@slyon, Thanks for the sponsoring.
But we need to upload the OEM metapackage into https://launchpad.net/~canonical-oem-metapackage-uploaders/+archive/ubuntu/oem-metapackage-staging first to get the https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Canonical_OEM_metapackage_packageset before we put it in the queue.

[Shih-Yuan Lee (fourdollars)]

I have included this package into the canonical-oem-metapackages packageset.

[Lukas Märdian (slyon)]

Thank you @fourdollars. I assigned ~ubuntu-archive to this (and the other, related bugs) so that they can now accept it from the NEW queue.

[Steve Langasek (vorlon)]

Although the oem meta packages have been around now for some time, I am coming across this as I believe the first one I have ever reviewed as an SRU Team member / Archive Admin.

And I find that the expectations here are under-documented.

Why is this package uploaded to the NEW queue only in the last LTS, and not to the devel series?

If a user gets such a metapackage installed in an Ubuntu 22.04 LTS install, and then they choose to upgrade to Ubuntu 24.04, which we support; or to Ubuntu 24.04 LTS when it is released; what is supposed to happen?

https://lists.ubuntu.com/archives/technical-board/2020-January/002478.html is referenced by one of the wiki pages, and contains the text:

> Also, eventually, the certified oem metapackages will wean certified
> machines off the oem kernel flavour onto the hwe/generic flavours when
> those incorporate all the needed delta for a given SKU.

However, if these metapackages do not exist in later releases, there seems to be no way at all for this to happen. So what provisions are there in place to see that this does happen?

https://wiki.ubuntu.com/OEMArchive says that the oem package archives are located at http://oem.archive.canonical.com/dists/. oem-sutton-abishag-meta points to lenovo.archive.canonical.com. Why is this different?

[Shih-Yuan Lee (fourdollars)]

I just updated https://wiki.ubuntu.com/OEMArchive that http://*.archive.canonical.com/ are all mapped to the same server.

https://wiki.ubuntu.com/OEMArchive was mentioning "These OEM archives are currently made available for 20.04 only" and "It is worth noting that as the only focus of the OEM experience is currently 20.04, the aforementioned meta-packages are only made available via focal release and focal-updates" and I just modified it to include 22.04.

If the users choose to upgrade to Ubuntu 23.04, it should still use the same OEM kernel or the general kernel on Ubuntu 23.10 while OEM metapackage is not purged.

Certified machines only exist for Ubuntu LTS series in general so OEM metapackages will only follow the certification on https://ubuntu.com/certified/ to publish the corresponding OEM metapackage.

Taking https://ubuntu.com/certified/202303-31377 for example, it is certified on Ubuntu 22.04 so we will prepare the corresponding OEM metapackage, i.e. oem-sutton-abishag-meta, for it.

[Łukasz Zemczak (sil2100)]

Hello OEM, or anyone else affected,

Accepted oem-sutton-abishag-meta into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oem-sutton-abishag-meta/22.04~ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Bin Li (binli)]

After enabled the proposed channel, I could install the meta package successfully.

u@Golem2-AMD-3:~$ ubuntu-drivers list-oem
oem-sutton-abishag-meta
u@Golem2-AMD-3:~$ apt-cache policy oem-sutton-abishag-meta
oem-sutton-abishag-meta:
  Installed: (none)
  Candidate: 22.04~ubuntu1
  Version table:
     22.04~ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages

u@Golem2-AMD-3:~$ sudo apt install oem-sutton-abishag-meta
Need to get 1,926 B of archives.
After this operation, 13.3 kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 oem-sutton-abishag-meta all 22.04~ubuntu1 [1,926 B]
Fetched 1,926 B in 1s (3,112 B/s)
Selecting previously unselected package oem-sutton-abishag-meta.

u@Golem2-AMD-3:~$ sudo apt update

u@Golem2-AMD-3:~$ apt-cache policy oem-sutton-abishag-meta
oem-sutton-abishag-meta:
  Installed: 22.04~ubuntu1
  Candidate: 22.04ubuntu3
  Version table:
     22.04ubuntu3 500
        500 http://lenovo.archive.canonical.com jammy/sutton amd64 Packages ...

[Bin Li (binli)]

Do an offline install. Boot the system. Run update-manager. It could install the meta packages successfully.

[Launchpad Janitor (janitor)]

This bug was fixed in the package oem-sutton-abishag-meta - 22.04~ubuntu1

---------------
oem-sutton-abishag-meta (22.04~ubuntu1) jammy; urgency=medium

  * Meta package for Sutton Abishag. (LP: #2002216)

 -- Bin Li <email address hidden> Thu, 05 Jan 2023 14:22:32 +0800

[Andreas Hasenack (ahasenack)]

The verification of the Stable Release Update for oem-sutton-abishag-meta has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.