'PPA for PHP' to 'Use packages.sury.org/php instead'

Community Support General Questions
1

Hey Team,

I’ve had my Hestia CP on Ubuntu for quite some time … I did my usual upgrade today, but when i do sudo apt-get update && sudo apt-get upgrade … I am now seeing the following issue;

Hit:5 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu noble InRelease
Hit:6 https://nginx.org/packages/mainline/ubuntu noble InRelease
Get:7 https://ppa.launchpadcontent.net/ondrej/php/ubuntu noble InRelease [24.4 kB]
Hit:8 https://apt.hestiacp.com noble InRelease
Reading package lists... Done
E: Repository 'https://ppa.launchpadcontent.net/ondrej/php/ubuntu noble InRelease' changed its 'Label' value from 'PPA for PHP' to 'Use packages.sury.org/php instead'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

a dump of my /etc/os-release is as follows;

PRETTY_NAME="Ubuntu 24.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.4 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

My Hestia CP version is VERSION=‘1.9.6’

Is there any fix for this?

2

Hi,

It’s not an error. Sury’s PPA for Ubuntu will eventually be replaced by the same repository used for the Debian packages. I’m not sure why the label has changed already, since there hasn’t been any “official” announcement yet.

3

Hey @sahsanu .. Ok, so i should wait until it sorts itself out?

4

Yes, for the moment, just wait. Sury is expected to provide a way to handle the migration, but if that doesn’t happen, we’ll take care of it ourselves, no worries.

5

@sahsanu … Beautiful … Thank you for your help, appreciate you :folded_hands:

6

If you want to get rid of the error message you can run
apt-get --allow-releaseinfo-change update
But yes, I’m hoping that Sury will sort out the change of PPA url and probably the key too.

7

Just a guess here, but maybe because the recent update to PHP 8.3.32 allows (optimistically) for the longest amount of time before another update rolls out (and this becomes a high priority change)? In the spirit of getting a heads up as early as possible…

Thanks for what all y’all do!

8

In case anyone wants to switch to the new repo, I made this script:

Warning: Use it at your own risk :wink:

curl -fsSLm30 https://7j.gg/switchsuryrepo | sudo bash -s --
9

But for the time being the current PPA will work, right? No need to switch, right?

10

Yes, the PPAs are still working, but I don’t know for how long. He said four months ago that he would make the proper arrangements in time so that people could easily switch from the PPA to the new repo. So I don’t understand why he changed the repo label without making an official announcement about the switch.

11

so up until now, We can ignore that warning and PHP still being able to update?

12

First you must answer yes to que question when doing apt update, after that, yes, it should update php normally untill Sury decides to close the PPA.

13

Hello,
I was able to update PHP (for Jammy) without any issues this evening using the PPA. For now, the message prompting a switch to a different repository isn’t appearing. We’ll see what happens tomorrow morning with the cron update.