[MIR][jammy] oem-somerville-torchic-meta

Bug #1997662 reported by OEM Taipei Bot
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OEM Priority Project
Fix Committed
Critical
OEM Taipei Bot
oem-somerville-torchic-meta (Ubuntu)
Jammy
Fix Committed
Undecided
Unassigned

Bug Description

[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-somerville-torchic-meta for jammy:
    git clone -b torchic-jammy-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta

[Rationale]
We want to improve the hardware support for some Dell 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 Dell platforms.
oem-somerville-torchic-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/202301-31173
https://ubuntu.com/certified/202301-31174
https://ubuntu.com/certified/202301-31175

Changed in oem-priority:
assignee: nobody → OEM Taipei Bot (oem-taipei-bot)
importance: Undecided → Critical
status: New → Confirmed
Revision history for this message
OEM Taipei Bot (oem-taipei-bot) wrote :

Attach oem-somerville-torchic-meta_22.04~ubuntu1.debdiff by oem-scripts 1.85.

description: updated
summary: - [DRAFT][MIR][jammy] oem-somerville-torchic-meta
+ [MIR][jammy] oem-somerville-torchic-meta
Changed in oem-priority:
status: Confirmed → In Progress
tags: added: oem-scripts-1.85
removed: oem-scripts-1.55
Cyrus Lien (cyruslien)
tags: added: oem-scripts-1.88
removed: oem-scripts-1.85
tags: added: certify-planning originate-from-1996187
description: updated
Changed in oem-priority:
status: In Progress → Fix Committed
tags: added: oem-needs-upload ubuntu-certified
Changed in ubuntu:
status: New → In Progress
tags: added: oem-done-upload oem-scripts-1.92
removed: oem-needs-upload oem-scripts-1.88
Revision history for this message
Shih-Yuan Lee (fourdollars) wrote :

I have uploaded the package into https://launchpad.net/ubuntu/jammy/+queue.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "oem-somerville-torchic-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.]

tags: added: patch
Revision history for this message
Steve Langasek (vorlon) wrote :

Why is the modalias for this matching on a pci ID instead of on a DMI string? That seems questionable, especially when the PCI ID in question isn't listed in /usr/share/misc/pci.ids. How is anyone supposed to know that this modalias won't cause false-positives for other Dell models, now or in the future?

I see that I did recently accept a number of other metapackages into jammy-proposed that key on pci id instead of on dmi - specifically, all of the oem-stella-* ones. I didn't notice this at the time and consider the implications. Anything we decide here should bear on those other metapackages.

Changed in ubuntu:
status: In Progress → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote :

Adding Łukasz to cc: as he has also previously reviewed and accepted oem metapackages in jammy that key on pci ID (tentacool)

Revision history for this message
Cyrus Lien (cyruslien) wrote :

@Steve, Łukasz,

Sorry for the late reply.

The BIOS ID=SVID + SSID, SVID is Dell ID and all of the Dell platforms share the same Dell ID, SSID is subsystem ID and it is unique for every platform.

All OEM BIOS will set the SVID and SSID to the PCI device’s space: 2C-2F.

For more detail information, please refer to https://docs.google.com/document/d/1psbB8w2ztwP5YF8qZKRJUYYhKo5CvI_s_VQi-LA8zec/edit

Thanks

Revision history for this message
Steve Langasek (vorlon) wrote :

Thanks. That document explains, but is private. Since SRUs are a public process, please make that documentation available publicly, linked from the exception wiki page.

tags: added: verification-needed verification-needed-jammy
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello OEM, or anyone else affected,

Accepted oem-somerville-torchic-meta into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oem-somerville-torchic-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.

Changed in ubuntu:
status: Incomplete → Fix Committed
Changed in oem-somerville-torchic-meta (Ubuntu Jammy):
status: New → Fix Committed
no longer affects: oem-somerville-torchic-meta (Ubuntu)
no longer affects: Ubuntu Jammy
no longer affects: ubuntu
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.