If you are using Ubuntu 24.04 LTS, you are likely to come across this message while updating the system in the terminal:
The following upgrades have been deferred due to phasing
Actually, a reader contacted me with this error he faced with his newly installed Ubuntu 24.04 system.
admn@dell:~$ sudo apt update && sudo apt upgrade -y
[sudo] password for admn:
Hit:1 http://security.ubuntu.com/ubuntu noble-security InRelease
Hit:2 http://in.archive.ubuntu.com/ubuntu noble InRelease
Get:3 http://in.archive.ubuntu.com/ubuntu noble-updates InRelease [89.7 kB]
Hit:4 http://in.archive.ubuntu.com/ubuntu noble-backports InRelease
Hit:5 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu noble InRelease
Hit:6 https://ppa.launchpadcontent.net/texworks/stable/ubuntu noble InRelease
Fetched 89.7 kB in 21s (4,340 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
W: https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/dists/noble/InRelease: Signature by key 0AB215679C571D1C8325275B9BDB3D89CE49EC21 uses weak algorithm (rsa1024)
W: https://ppa.launchpadcontent.net/texworks/stable/ubuntu/dists/noble/InRelease: Signature by key 3EAF6A811849A711A6D5F781ACBAE083CDF2E7E8 uses weak algorithm (rsa1024)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
apturl-common python3-dateutil ubuntu-advantage-desktop-daemon
Use 'sudo apt autoremove' to remove them.
The following upgrades have been deferred due to phasing:
distro-info-data
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
admn@dell:~$
Now, if you see this message, do not panic. Nothing to be worried about.
It’s not an error and your system is fine. It’s just a message that tells you that the package in question has an update but it is rolling out in phases. So that if the package causes regression, the update is rolled back and fewer users are impacted.
Perhaps if you run update again after a few days, the same package will be updated just fine.