[Bug 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.

[Łukasz Zemczak]

Hello nuclearsandwich, or anyone else affected,

Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.7 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: apt (Ubuntu Jammy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  Installing libudev1 on a new Jammy installation uninstalls many
  packages.

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Kinetic:
  In Progress

Bug description:
  [Impact]
  On an Ubuntu 22.04 desktop system created using the current installation image without enabling package updates over the network, installing the package libudev1 results in a large number of critical packages being removed and rendering the system essentially unusable.

  [Test plan]
  Comprehensive regression test suite validating a full solver dump with the issue is run as autopkgtest.

  [Where problems could occur]
  We could break other things from resolving. The solver is a bit finicky. Hopefully this is isolated enough.

  [Other info]

  https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile which also demonstrates the issue.
  Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, and then running `apt install libudev1` in the generated image results in

  The following packages will be REMOVED:
    libnss-systemd libpam-systemd systemd-timesyncd udev
  The following packages will be upgraded:
    libudev1

  This is completely prevented by ensuring that updates are installed
  from the jammy-updates repository before installing any additional
  packages and that is almost certainly the correct thing to do. But
  this is a punishing result for such a mistake.

  I would expect the installation to either force the upgrade of the
  other systemd packages or refuse to install libudev1 at the incorrect
  version relative to the other systemd packages until the system is
  upgraded.

  We found this out via a user report for ROS 2 Humble which is
  releasing on top of Ubuntu 22.04 next week:
  https://github.com/ros2/ros2/issues/1272

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