186

When I run apt-get update on my ubuntu 17.10 I receive the following error:

E: Repository 'http://ppa.launchpad.net/ondrej/php/ubuntu artful InRelease' changed its 'Label' value from '*****
The main PPA for PHP (5.6, 7.0, 7.1) with many PECL extensions *****' to '*****
The main PPA for supported PHP versions with many PECL extensions *****'
N: This must be accepted explicitly before updates for this repository can be applied.
See apt-secure(8) manpage for details."

The man page doesn't really point to a solution. My question is, how do I explicitly accept the change?

Zanna
  • 72,471
Rick
  • 1,911

5 Answers5

353

It would help if you posted your repositories, but, with that said, you sort of have 2 ways to fix this.

First would be to use apt rather than apt-get. apt is preferred over apt-get for interactive use in recent Ubuntu versions; and apt should, in theory, fix this for you.

sudo apt update
sudo apt upgrade

Your second option is to use --allow-releaseinfo-change

sudo apt-get update --allow-releaseinfo-change

If those options do not resolve the issue, please post your repositories, are you using mixed repositories or pinning, and, finally, tell us, is this an upgrade ?

Lorenz Keel
  • 9,551
Panther
  • 104,796
  • 1
    I get an error when using the second command:

    sudo apt-get --allow-release-info-change update

    E: Command line option --allow-release-info-change is not understood in combination with the other options

     – Roel Van de Paar Jul 29 '18 at 21:25
  • 10
    Using sudo apt update fixed the issue. I was prompted: "Do you want to accept these changes and continue updating from this repository? [y/N]". – Ruben O. Chiavone Oct 19 '18 at 04:26
  • 3
    the apt-get command worked for me, with the --allow-releaseinfo-change after the update command. – SpinUp __ A Davis Nov 12 '18 at 20:17
  • None of those options work if you invoke apt non-interactively (e.g. the shell does not have a controlling terminal). Even the --yes option is ignored without a controlling terminal. Only if you run those commands from a gnome-terminal (or xterm, or whatever terminal) do those options work. – bgoodr Nov 18 '18 at 15:34
  • it works great ! – Kamil Naja Apr 30 '19 at 19:42
  • I would strongly suggest against using -̶-̶a̶l̶l̶o̶w̶-̶r̶e̶l̶e̶a̶s̶e̶i̶n̶f̶o̶-̶c̶h̶a̶n̶g̶e̶ as it's meant for ALL repositories (unless some specific option configs are made) which could pose a security threat. apt update asks you per repo. – jave.web May 02 '25 at 22:00
90

You need to use apt instead of apt-get. It will ask you to accept the changes interactively. Simply run:

sudo apt update

It should ask you:

Do you want to accept these changes and continue updating from this repository? [y/N]
Roy de Jong
  • 1,011
  • Sorry for the late comment but small things like this are the reason we need to stop using apt-get and start using apt – site80443 May 29 '25 at 12:17
16

If you want to deploy it e.g. run in on many servers at once then execute:

apt-get update --allow-releaseinfo-change
apt-get update
apt-get install packagename
Zoe - Save the data dump
  • 72
TaaviT
  • 161
  • 1
  • 3
1

For me, anyhow, the answer was here:

https://neon.kde.org/faq#command-to-update

And I give you the link because I assume it's updated as needed. Currently, it reads that you must run:

pkcon refresh
pkcon update

Which is what I'm running. Hopefully, my computer will still work once it's done.

guest
  • 11
  • While updating Ubuntu 24.04.1 LTS using command sudo apt-get update getting below error: Repository 'https://ppa.launchpadcontent.net/ondrej/php/ubuntu noble InRelease' changed its 'Label' value from '***** The main PPA for supported PHP versions with many PECL extensions *****' to 'PPA for PHP'

    Resolved this using

    pkcon refresh sudo apt-get update --allow-releaseinfo-change

    all good then

     – muhammadanish May 11 '25 at 15:37
0

I had this when trying to update/upgrade buster packages.

First, I had to update /etc/sources.list to use the archive paths:

deb http://archive.debian.org/debian buster main
deb http://archive.debian.org/debian-security buster/updates main
deb http://archive.debian.org/debian-volatile buster/volatile main
deb http://archive.debian.org/backports.org buster-backports main

Then the usual steps:

sudo apt-get update
sudo apt-get upgrade

Version upgrade

To get the latest version (bullseye) I updated /etc/apt/sources.list to:

deb http://deb.debian.org/debian bullseye main
deb-src http://deb.debian.org/debian bullseye main


deb http://deb.debian.org/debian bullseye-updates main
deb-src http://deb.debian.org/debian bullseye-updates main


deb http://security.debian.org/debian-security/ bullseye-security main
deb-src http://security.debian.org/debian-security/ bullseye-security main

and repeat but with the full-upgrade option:

sudo apt-get update
sudo apt-get full-upgrade

xscreensaver warning

If during the upgrade it says:

One or more running instances of xscreensaver or xlockmore have been detected on this system. Because of incompatible library changes, the upgrade of the GNU libc library will leave you unable to authenticate to these programs. You should arrange for these programs to be restarted or stopped before continuing this upgrade, to avoid locking your users out of their current sessions.

then use these steps:

pgrep -l screensaver
pkill screensaver
pgrep -l screensaver
SharpC
  • 115