that fixed it and during the commands I got the following message which you might of expected.
thanks.
jammy InRelease’ changed its ‘Label’ value from '*****
shoulders@server:~$ sudo apt clean
[sudo] password for shoulders:
shoulders@web:~$ sudo apt update
Hit:1 http://gb.archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://gb.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://gb.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:4 http://gb.archive.ubuntu.com/ubuntu jammy-security InRelease
Hit:5 https://software.virtualmin.com/vm/7/pro/apt virtualmin InRelease
Get:6 https://ppa.launchpadcontent.net/ondrej/php/ubuntu jammy InRelease [24.6 kB]
E: Repository 'https://ppa.launchpadcontent.net/ondrej/php/ubuntu jammy InRelease' changed its 'Label' value from '***** The main PPA for supported PHP versions with many PECL extensions *****' to 'PPA for PHP'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
Get:7 https://ppa.launchpadcontent.net/ondrej/php/ubuntu jammy/main amd64 Packages [138 kB]
Get:8 https://ppa.launchpadcontent.net/ondrej/php/ubuntu jammy/main Translation-en [43.7 kB]
Fetched 206 kB in 11s (18.1 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
53 packages can be upgraded. Run 'apt list --upgradable' to see them.
shoulders@server:~$
I had the same exact problem as @shoulders with the ondrej repository. So I executed apt clean and apt update. I now have 2 issues.
The update command returned some warnings (command output at the end of post)
a) “The following signatures were invalid:”
EXPKEYSIG D9F9010760D62A6B Virtualmin, Inc.
EXPKEYSIG D9F9010760D62A6B Virtualmin, Inc.
EXPKEYSIG 78BD65473CB3BD13 Google Inc.
EXPKEYSIG D9F9010760D62A6B Virtualmin, Inc.
EXPKEYSIG D9F9010760D62A6B Virtualmin, Inc.
EXPKEYSIG 78BD65473CB3BD13 Google Inc.
b) The following signatures couldn’t be verified because the public key is not available:
NO_PUBKEY 35696F43FC7DB4C2
Should I do something about these?
On the Virtualmin dashboard it still shows 127 package updates are available. When I click that, it shows me those packages and when I click ‘Update selected packages’, it lists only a single package (msodbcsql17 17.9.1.1-1 17.10.6.1-1 ODBC Driver for Microsoft(R) SQL Server(R)) which I always have to manually update. So essentially there are zero updateable packages, but Virtualmin still lists 127! How can I fix this?
Unsolved posts (posts that the OP hasn’t marked a solution comment on) remain open for a couple of months (I think, I don’t remember specifics). Solved posts auto-close after a couple of weeks. Trying to balance the need for people to follow up later with the desire to prevent zombie posting. Sometimes we just need post to read the guidelines and post politely. Not a big deal, we just ask folks to make a new topic when it happens.
You can help by checking the checkbox that indicates which comment solved your problem.
They auto-close after a couple of months of no activity, as I mentioned.
This specific thread has had spam activity that kept it open. The comments have been deleted, but it updated the activity counter so it didn’t close. Spammers like old threads because they assume no one is paying attention to them.
Again, if you want topics to close faster, mark the comment that solved the problem with the Solved checkbox, and it’ll close in a week or two (I don’t remember details).
