If apt-get update on your Ubuntu server recently started to complain with
E: Repository 'https://ppa.launchpadcontent.net/ondrej/php/ubuntu jammy InRelease' changed its 'Label' value from 'PPA for PHP' to 'Use https://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.
there is nothing broken on your machine. Ondřej Surý, who maintains the PHP packages most Nextcloud installations on Ubuntu and Debian rely on, is moving his Ubuntu packages from the launchpad PPA to his own package server, the same server that has always served the Debian packages:
The changed label is the announcement of that move.
Right now the packages for jammy(22.04) and noble(24.04) are still served from both locations, but the packages for resolute(26.04) are served exclusively from packages.sury.org, the PPA does not carry them at all.
Accepting the changed label - interactively, or with
sudo apt-get update --allow-releaseinfo-change-label
only silences the message and does not migrate anything: the PPA will stop receiving updates. The apt source itself has to be replaced.
For exactly this I have written a new argument into the well-known and thousandfold proven → php-updater ← :
sudo php-updater --check-sury
It straightens out every Surý apt source configured on the machine, no matter in which format it was created (one-line .list or deb822 .sources): the old launchpad PPA source is deactivated (the file is kept, renamed to *_deactivated.*) and a fresh source pointing to packages.sury.org, signed with the current key, is created in its place. This covers the php and the apache2 repository, and defects it encounters on the way (outdated signing key, wrong suite, http instead of https) are repaired in the same manner. Nothing is changed without showing you first what was found and what is going to happen.
And if no Surý source is configured at all, it offers to add one, exactly as a normal php-updater run has always done, now of course pointing to the new URL.
Afterwards apt-get update runs clean again and your PHP packages follow the new server.
h.t.h.
ernolf