[Bug 2067585] Re: Upgrades to noble chmod /dev/null 644

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-release-upgrader - 1:24.10.4

---------------
ubuntu-release-upgrader (1:24.10.4) oracular; urgency=medium

  * DistUpgrade: drop quirk for systems with BIOS and XFS /boot (LP: #2067886)
  * DistUpgrade: use tempfile for apt extended_states during simulation
    (LP: #2067585)
  * DistUpgradeQuirks: drop t64 replacement quirk
  * Run pre-build.sh: updating mirrors, demotions, and translations.

 -- Nick Rosbrook <enr0n at ubuntu.com>  Wed, 05 Jun 2024 16:58:21 -0400

** Changed in: ubuntu-release-upgrader (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/2067585

Title:
  Upgrades to noble chmod /dev/null 644

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Noble:
  In Progress

Bug description:
  [Impact]
  Upgrades to noble chmod /dev/null 644, breaking use of the device on multi-user systems for non-root.

  [Test plan]
  1. do-release-upgrade mantic -> noble
  2. check that /dev/null remains 666

  [Where problems could occur]

  [Details]
  This is a regression of the fix for bug 2064090, where we pointed apt_pkg.config["Dir::State::extended_states"] = "/dev/null" in the simulation to not lose the automatically installed bit, as we need that later, apt chmod's it extended_states.

  The fix for this is to create a temporary file for extended_states,
  and then remove the temporary file at the end of the simulation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2067585/+subscriptions