[Bug 2051181] Re: apt cannot upgrade phased updates if the current security version is same as updates

[Robie Basak]

Hello Andy, or anyone else affected,

Accepted apt into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.7.3ubuntu0.1 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-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. 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.

** Tags added: verification-needed verification-needed-mantic

** Tags added: 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/2051181

Title:
  apt cannot upgrade phased updates if the current security version is
  same as updates

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Mantic:
  Fix Committed
Status in apt source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  A package that has the same version in -security and -updates, with the latter having a Phased-Update-Percentage set is subject to phasing which is not expected by the security team.

  [Test plan]
  An automatic test case has been added to apt's comprehensive integration test suite that simulates the problem. Passing of the autopkgtests is a successful test.

  [Where problems could occur]
  The fix in question changes the behavior, some people may have relied on that, but also this should not have happened server side (normally security updates do not receive a value but the real one in this case went a different route).

  Otherwise the fix is fairly contained, it removes a single OtherVer++
  increment which made it go one version below the current version, so
  we do not expect any problems; setting aside the usual regression
  potential from bugs in the compiler and so on.

  [Original bug report]
  When I finished installation with Jammy 22.04.3, I noticed that nvidia-driver-535 cannot be upgrade by either `apt upgrade` nor `apt dist-upgrade`.

  Below is the log of apt upgrade:
  ubuntu at ubuntu:~$ sudo apt -o Debug::pkgProblemResolver=1 upgrade --dry-run                                                                                                            [2/1878]
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Entering ResolveByKeep 10%
    Dependencies are not satisfied for nvidia-driver-535:amd64 < 535.129.03-0ubuntu0.22.04.1 | 535.154.05-0ubuntu0.22.04.1 @ii pumH NPb Ib >
  Package nvidia-driver-535:amd64 nvidia-driver-535:amd64 Depends on nvidia-dkms-535:amd64 < none | 535.154.05-0ubuntu0.22.04.1 @un umH > (<= 535.129.03-1)
    Keeping Package linux-modules-nvidia-535-oem-22.04c:amd64 due to Depends
    Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib >
  Keeping package linux-modules-nvidia-535-oem-22.04c:amd64
    Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib >
  Package linux-modules-nvidia-535-oem-22.04c:amd64 linux-modules-nvidia-535-oem-22.04c:amd64 Depends on linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU Ib > (= 6.1.0-1027.27)
    Keeping Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 due to Depends
    Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1028-oem:amd64 < none -> 6.1.0-1028.28+2 @un uN Ib >
  Keeping package linux-modules-nvidia-535-6.1.0-1028-oem:amd64
    Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib >
  Keeping package linux-modules-nvidia-535-6.1.0-1027-oem:amd64
    Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib >
  Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on linux-signatures-nvidia-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27)
    Keeping Package linux-signatures-nvidia-6.1.0-1027-oem:amd64 due to Depends
    Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib >
    Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib >
    Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib >
  Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on linux-objects-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27)
    Keeping Package linux-objects-nvidia-535-6.1.0-1027-oem:amd64 due to Depends

  https://pastebin.canonical.com/p/7frwTKZG6D/

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