Verification for jammy: As mentioned in the bug description, this bug happens on focal and earlier. On Jammt, apt already has the phasing implemented, and update-notifier will not fail even with the bug being present.
apt show apt 2>&1 | grep Phase # nothing faked yet
/usr/lib/update-notifier/apt-check -p 2>&1 | grep apt apt libapt-pkg6.0 apt-utils
(Faking phasing on -proposed apt package)
apt show apt 2>&1 | grep Phase Phased-Update-Percentage: 0
# Currently installed version: apt-cache policy update-notifier-common | head -n 3 update-notifier-common: Installed: 3.192.54.5 Candidate: 3.192.54.6
/usr/lib/update-notifier/apt-check -p 2>&1 | grep apt libapt-pkg6.0
# after upgrade to -proposed: apt-cache policy update-notifier-common | head -n 3 update-notifier-common: Installed: 3.192.54.6 Candidate: 3.192.54.6
/usr/lib/update-notifier/apt-check -p 2>&1 | grep apt libapt-pkg6.0 #
# same behavior, was respecting the phasing even before.
Verification for jammy:
As mentioned in the bug description, this bug happens on focal and earlier.
On Jammt, apt already has the phasing implemented, and update-notifier will not fail even with the bug being present.
apt show apt 2>&1 | grep Phase
# nothing faked yet
/usr/lib/ update- notifier/ apt-check -p 2>&1 | grep apt
apt
libapt-pkg6.0
apt-utils
(Faking phasing on -proposed apt package)
apt show apt 2>&1 | grep Phase Update- Percentage: 0
Phased-
# Currently installed version: notifier- common | head -n 3 notifier- common:
apt-cache policy update-
update-
Installed: 3.192.54.5
Candidate: 3.192.54.6
/usr/lib/ update- notifier/ apt-check -p 2>&1 | grep apt
libapt-pkg6.0
# after upgrade to -proposed: notifier- common | head -n 3 notifier- common:
apt-cache policy update-
update-
Installed: 3.192.54.6
Candidate: 3.192.54.6
/usr/lib/ update- notifier/ apt-check -p 2>&1 | grep apt
libapt-pkg6.0
#
# same behavior, was respecting the phasing even before.