This bug was fixed in the package apt - 2.7.11
---------------
apt (2.7.11) unstable; urgency=medium
[ David Kalnischkies ]
* Remove erroneous -a flag from apt-get synopsis in manpage
* Support -a for setting host architecture in apt-get source -b
[ Julian Andres Klode ]
* For phasing, check if current version is a security update, not just
previous ones
(LP: #2051181)
* Add public phased update API
* Add a new ?phasing pattern
* Add the ?security pattern
* Show a separate list of upgrades deferred due to phasing (LP: #1988819)
-- Julian Andres Klode <j...@debian.org> Tue, 13 Feb 2024 16:31:00
+0100
** Changed in: apt (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 Released
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 Released
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@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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
