PROPOSAL

NOT APPROVED YET, BEING DRAFTED.

Introduction

These packages exist to hint parts of the installer / upgrade tooling that the running hardware is certified, and should have certain packages installed.

They follow the naming scheme oem-*-meta.

SRU Bug template

XXX to be filled in

[ 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. (when this is ready in Ubuntu) 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.

Procedure

There is an existing MIR exception, allowing these packages to be accepted directly into main. As long as the package complies with the template required for the MIR exception to apply, it can be similarly accepted into -proposed without further review. SRU team members can use the script oem-metapackage-mir-check from lp:ubuntu-archive-tools to satisfy themselves that this is the case.

Canonical's Commercial Engineering team are expected to perform the required testing as outlined in the template above. This must be done on the package *as it exists in the Ubuntu archive*, so after acceptance into -proposed. Providing this is done, the 10-day aging period does not apply.