185

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,312
Rick
  • 1,901

5 Answers5

350

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,511
Panther
  • 104,528
88

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
  • 991
15

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
  • 1
  • 3
  • 9
TaaviT
  • 151
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
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