Add lrm autogenerated transitional independent of variants

Bug #1991130 reported by Kleber Sacilotto de Souza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-restricted-modules (Ubuntu)
Fix Released
Undecided
Unassigned
Focal
Invalid
Undecided
Unassigned
Jammy
Invalid
Undecided
Unassigned
Lunar
Invalid
Undecided
Unassigned
Mantic
New
Undecided
Unassigned
linux-restricted-modules-hwe-5.15 (Ubuntu)
Invalid
Undecided
Unassigned
Focal
Fix Released
High
Kleber Sacilotto de Souza
Jammy
Invalid
Undecided
Unassigned
Lunar
Invalid
Undecided
Unassigned
Mantic
Invalid
Undecided
Unassigned
linux-restricted-modules-hwe-5.19 (Ubuntu)
Invalid
Undecided
Unassigned
Focal
Invalid
Undecided
Unassigned
Jammy
In Progress
Undecided
Unassigned
Lunar
Invalid
Undecided
Unassigned
Mantic
Invalid
Undecided
Unassigned

Bug Description

[Impact]

The kernel lrm packages have a mechanism to auto-generate transitional packages by adding a line to 'debian/package.config' in the following format

transitional <from> <to> <archs>

Example:

transitional 450-oem-20.04 450-generic amd64

When being processed by 'debian/scripts/gen-rules.lrm' the autogenerated contents are added to 'debian/control.d/transitionals-local'. However, this file is not included in the final 'debian/control' for packages which does not contain the default variant '--' (see debian/rules.in). This is intentional to prevent unwanted transitionals.

However, there are some cases where we want to transition packages to kernels which are not the default variant in a series (e.g. hwe kernels).

[Fix]

The proposed fix is to add a new command "migrate", which does exactly what "transitional" does but adding the content to 'debian/control.d/migrate-local' which would get added to the final 'debian/control' independently of the source's variants.

[Test Case]

Add "migrate" entries to 'debian/package.config' and check whether they get added to 'debian/control' even for non default variant packages.

[Where problems could occur]

If not used correctly, unwanted transitionals could be generated causing issues to the archive. However, this is a new command and should not impact any of the previously set transitionals and it needs to be explicitly used.

Changed in linux-restricted-modules-hwe-5.15 (Ubuntu Focal):
status: New → In Progress
Changed in linux-restricted-modules-hwe-5.15 (Ubuntu):
status: New → Invalid
Changed in linux-restricted-modules-hwe-5.15 (Ubuntu Focal):
importance: Undecided → High
assignee: nobody → Kleber Sacilotto de Souza (kleber-souza)
description: updated
summary: - Fix lrm transitional autogenerate
+ Add lrm autogenerated transitional independent of variants
Timo Aaltonen (tjaalton)
Changed in linux-restricted-modules (Ubuntu Focal):
status: New → Invalid
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (linux-restricted-modules-hwe-5.15/5.15.0-70.77~20.04.1)

All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15 (5.15.0-70.77~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#linux-restricted-modules-hwe-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (linux-restricted-modules-hwe-5.15/5.15.0-70.77~20.04.1+1)

All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15 (5.15.0-70.77~20.04.1+1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#linux-restricted-modules-hwe-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-restricted-modules-hwe-5.15 - 5.15.0-70.77~20.04.1+1

---------------
linux-restricted-modules-hwe-5.15 (5.15.0-70.77~20.04.1+1) focal; urgency=medium

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (adhoc/2023.03.20)
    - update spin to 2023.03.20-4

linux-restricted-modules-hwe-5.15 (5.15.0-70.77~20.04.1) focal; urgency=medium

  * Master version: 5.15.0-70.77~20.04.1

  * Migrate oem-20.04 to hwe-5.15 (LP: #1987507)
    - [Packaging] Migrate oem-20.04 to hwe-5.15

  * Add lrm autogenerated transitional independent of variants (LP: #1991130)
    - [Packaging] add a new migrate autogenerate option

  * Miscellaneous Ubuntu changes
    - debian/tracking-bug -- update from master

 -- Andy Whitcroft <email address hidden> Thu, 13 Apr 2023 10:29:37 +0100

Changed in linux-restricted-modules-hwe-5.15 (Ubuntu Focal):
status: In Progress → Fix Released
Timo Aaltonen (tjaalton)
Changed in linux-restricted-modules-hwe-5.15 (Ubuntu Lunar):
status: New → Invalid
Changed in linux-restricted-modules (Ubuntu Lunar):
status: New → Invalid
Changed in linux-restricted-modules-hwe-5.19 (Ubuntu Focal):
status: New → Invalid
Changed in linux-restricted-modules (Ubuntu Jammy):
status: New → Invalid
Changed in linux-restricted-modules-hwe-5.15 (Ubuntu Jammy):
status: New → Invalid
Changed in linux-restricted-modules-hwe-5.19 (Ubuntu Lunar):
status: New → Invalid
Changed in linux-restricted-modules-hwe-5.19 (Ubuntu Mantic):
status: New → Invalid
Changed in linux-restricted-modules-hwe-5.19 (Ubuntu Jammy):
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-restricted-modules - 6.8.0-28.28

---------------
linux-restricted-modules (6.8.0-28.28) noble; urgency=medium

  * Main version: 6.8.0-28.28

  * Packaging resync (LP: #1786013)
    - [Packaging] debian/tracking-bug -- resync from main package

 -- Paolo Pisati <email address hidden> Tue, 16 Apr 2024 19:03:14 +0200

Changed in linux-restricted-modules (Ubuntu):
status: New → Fix Released
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.