[Bug 2130617] Re: [SRU] profile fixes for AppArmor in Questing

[Ryan Lee]

** Description changed:

  [ Impact ]
  
  This SRU to Questing contains bugfixes for a number of bugs:
-  - tnftp could not read the ~/.netrc config file (LP: #2127491)
-  - systemd-detect-virt gave permission denials on some device tree based non-x86_64 platforms (LP: #2127111)
-  - lsblk on Azure systems could not read NVMe ACPI hierarchy info (LP: #2126920)
-  - Parts of the regression test suite would spuriously fail due to Rust coreutils adoption (LP: #2129779)
+  - tnftp could not read the ~/.netrc config file (LP: #2127491)
+  - systemd-detect-virt gave permission denials on some device tree based non-x86_64 platforms (LP: #2127111)
+  - lsblk on Azure systems could not read NVMe ACPI hierarchy info (LP: #2126920)
+  - Parts of the regression test suite would spuriously fail due to Rust coreutils adoption (LP: #2129779)
  
  [ Test Plan ]
  
  Each of the individual bugs have corresponding test plans. AppArmor as a
  whole is also tested by QRT (run as part of LP: #2129779's test plan).
  
  [ Where problems could occur ]
  
  Potential problems with each patch have been documented on the
  corresponding individual bugs.
  
  [ Other Info ]
  
- This upload is tagged 5.0.0~alpha1-0ubuntu9~25.10 to match up with the
- 5.0.0~alpha1-0ubuntu9 version in 26.04. It does not contain the
- debian/rules temporary workaround for python3.14-tk brokenness, as
- Questing does not ship Python 3.14 and does not need this workaround.
- However, I do not consider this a "meaningful difference" as per
- https://documentation.ubuntu.com/project/how-ubuntu-is-
- made/concepts/version-strings/#version-backport-from-ubuntu-devel, as
- the workaround only affects package testing and not the built contents
- of the package itself.
+ This upload matches the 5.0.0~alpha1-0ubuntu9 version in 26.04, besides
+ of not containing the debian/rules temporary workaround for
+ python3.14-tk brokenness, since Questing does not ship Python 3.14 and
+ does not need this workaround.
  
- If this is indeed a "meaningful difference", then the version number
- should be changed to -0ubuntu8.3, as -0ubuntu8.2 in Resolute is a no-
- change rebuild of -0ubuntu8.1 for Python 3.14.
+ The version number is changed to -0ubuntu8.3, as -0ubuntu8.2 in Resolute
+ is a no-change rebuild of -0ubuntu8.1 for Python 3.14.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2130617

Title:
  [SRU] profile fixes for AppArmor in Questing

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Questing:
  New
Status in apparmor source package in Resolute:
  Fix Released

Bug description:
  [ Impact ]

  This SRU to Questing contains bugfixes for a number of bugs:
   - tnftp could not read the ~/.netrc config file (LP: #2127491)
   - systemd-detect-virt gave permission denials on some device tree based non-x86_64 platforms (LP: #2127111)
   - lsblk on Azure systems could not read NVMe ACPI hierarchy info (LP: #2126920)
   - Parts of the regression test suite would spuriously fail due to Rust coreutils adoption (LP: #2129779)

  [ Test Plan ]

  Each of the individual bugs have corresponding test plans. AppArmor as
  a whole is also tested by QRT (run as part of LP: #2129779's test
  plan).

  [ Where problems could occur ]

  Potential problems with each patch have been documented on the
  corresponding individual bugs.

  [ Other Info ]

  This upload matches the 5.0.0~alpha1-0ubuntu9 version in 26.04,
  besides of not containing the debian/rules temporary workaround for
  python3.14-tk brokenness, since Questing does not ship Python 3.14 and
  does not need this workaround.

  The version number is changed to -0ubuntu8.3, as -0ubuntu8.2 in
  Resolute is a no-change rebuild of -0ubuntu8.1 for Python 3.14.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2130617/+subscriptions