I have the Ubuntu Game Pack and I’m trying to use sudo apt-get update and it’s returing the error
W: https://download.01.org/gfx/ubuntu/16.04/main/dists/xenial/InRelease: Signature by key 09D6EF97BFB38E916EF060E756A3DEF863961D39 uses weak digest algorithm (SHA1)
W: GPG error: http://deb.playonlinux.com trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 73F0D6E88E3D6C3A
W: The repository 'http://deb.playonlinux.com trusty InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://download.opensuse.org/repositories/home:/strycore/xUbuntu_16.04 ./ Release: The following signatures were invalid: KEYEXPIRED 1484261108
W: The repository 'http://download.opensuse.org/repositories/home:/strycore/xUbuntu_16.04 ./ Release' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
How can I resolve this?
Giacomo1968
52.6k19 gold badges162 silver badges211 bronze badges
asked Jan 31, 2018 at 18:23
remove sources.list and index.html in /etc/apt dir
cp /etc/apt/preferences.d/index.html /tmp
rm -rf /etc/apt/preferences.d/index.html
cp /etc/apt/sources.list /tmp
rm -rf sources.list
then reboot
tinlyx
1,4406 gold badges26 silver badges42 bronze badges
answered Aug 28, 2019 at 11:20
Just go to update GUI and ‘unclick’ every «other software». Refresh cache is going to work well now, and ‘sudo apt update’ as well.
answered Dec 12, 2020 at 16:47
Asked
5 years, 3 months ago
Viewed
700 times
While updating getting error when running
sudo apt-get update
The error:
The repository 'http://security.ubuntu.com/ubuntu yakkety-security Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://in.archive.ubuntu.com/ubuntu yakkety Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://in.archive.ubuntu.com/ubuntu yakkety-updates Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://in.archive.ubuntu.com/ubuntu yakkety-backports Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Zanna♦
68.9k56 gold badges215 silver badges327 bronze badges
asked Feb 21, 2018 at 14:22
1
Ubuntu 16.10 is not supported any more (since July 2017), hence there are no information about packages available anymore (as indicated by the does no longer have a Release file message.
Your choices are to downgrade to 16.04 or upgrade to 17.10
answered Feb 21, 2018 at 14:29
mbeyssmbeyss
9688 silver badges22 bronze badges
1
Content
- Introductory
- The symptom
- The solution
- Conclusion
Introductory
If there is a major change in your Debian system — so you don’t just need to upgrade one or two sub-versions — you will get an error message during a smooth upgrade. So it was with me when I picked up the Debian 10 is my perfect server virtual machine and I wanted to update. On the machine a luggage racks they were still up-to-date on March 2021, 6, so my system missed a major update.
The symptom
When your Debian system is about to upgrade to a larger version and you want to upgrade the repositories rootas
apt-get updatecommand, you receive the following error message:
[...] N: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Version' value from '10.8' to '10.11' E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. E: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. E: Repository 'https://packages.sury.org/php buster InRelease' changed its 'Suite' value from '' to 'buster' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
What happened here was that when I last used this virtual machine, Debian 10 (Buster) was the stable release, but it has been Debian 11 (Bullseye) is out (August 2021, 14), so Debian 10 was moved to the «oldstable» series, and Debian 11 took its place as a stable release. So this corresponds to a major version switch in the repositories, so further interaction is required to update our repositories.
The solution
The solution is simple. The The manual page of the apt-get command includes the solution:
man apt-get[...]
--allow-releaseinfo-change
Allow the update command to continue downloading data from a repository which changed
its information of the release contained in the repository indicating e.g a new major
release. APT will fail at the update command for such repositories until the change is
confirmed to ensure the user is prepared for the change. See also apt-secure(8) for
details on the concept and configuration.
Specialist options (--allow-releaseinfo-change-field) exist to allow changes only for
certain fields like origin, label, codename, suite, version and defaultpin. See also
apt_preferences(5). Configuration Item: Acquire::AllowReleaseInfoChange.
[...]
In short, this switch allows the update command to continue downloading data from repositories where release information has changed. In the present example, for Debian 10, the «stable» version has changed to the «oldstable» version.
Of course, only the names of the releases will change here, and our packages will be updated in the same way as before.
So run the repository update again with the «—allow-releaseinfo-change» option:
apt-get update --allow-releaseinfo-changeThe boot database update is now running:
At the end, you’ll even update your release info:
[...] N: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable' N: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Version' value from '10.8' to '10.11' N: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable' N: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates' N: Repository 'https://packages.sury.org/php buster InRelease' changed its 'Suite' value from '' to 'buster'
From now on, the update will go as usual. For example, if you run the refresh command again smoothly:
apt-get updateIt will update as smoothly as before:
Then you can upgrade your standard packages:
apt-get upgrade
Here it is clear that this system has not been updated for a very long time, so now you have quite a few packages to deal with.
Conclusion
So it’s a good idea to keep your system up to date at all times, because then updates before major changes already include the required boot release information for the subsequent migration. So, for example, on my desktop Debian 10 machine, I didn’t get this error message, but it switched nicely to the «oldstable» release when the time came. But if we don’t have the ability to update often, it’s not a problem either, because this «—allow-releaseinfo-change» switch can easily fix this little inconvenience.
Хотя пакеты Flatpak набирают популярность с каждым днем, я осмелюсь сказать, что большинство из нас по-прежнему предпочитает программное обеспечение для репозиториев независимо от распространения. По этой причине, например, в Ubuntu легко добавить репозиторий с последней версией OBS Studio с его наиболее актуальными зависимостями. Но что, если мы сделаем это и увидим текст «Ошибка GPG»? Это то, что имеет решение.
Когда мы видим ошибку GPG или просим нас просмотреть страницу руководства apt-secure (8), происходит следующее: мы пытаемся использовать неподписанный репозиторий, или он просто недоступен для нашей версии Debian / Ubuntu. Это может произойти, например, если мы находимся в системе, которая больше не получает или еще не поддерживается, такой как Ubuntu 22.04 Jammy Jellifish, которая сейчас находится в разработке. Имейте в виду, что при принудительном пополнении счета мы пропустим предупреждение системы безопасности, поэтому будьте осторожны с этим. Даже если мы будем использовать официальные источники, такие как OBS или Pipewire, что-то может перестать работать. Это не новая ошибка, но здесь, в LxA, о ней ничего не говорилось.
Чтобы избежать ошибки GPG, отредактируйте файл sources.list
Сделать это довольно просто. Здесь мы собираемся использовать репозиторий Pipewire в качестве примера, в котором говорится, что проблема зависания Kooha в последних версиях решена (это не было моим случаем в Jammy Jellyfish …). Для принудительная перезагрузка, мы бы сделали следующее:
- Мы должны добавить репозиторий в файл sources.list, который находится в / etc / apt, поэтому самый быстрый способ — открыть терминал и написать:
sudo nano /etc/apt/sources.list
- Вводим пароль нашего пользователя.
- Теперь, в конце, мы добавим репозиторий и отметим его как надежный. В случае Pipewire и для Ubuntu 21.10, или 22.04, поскольку нет опции «jammy», мы бы добавили следующее:
deb [trusted=yes] http://ppa.launchpad.net/pipewire-debian/pipewire-upstream/ubuntu/ hirsute main
- После добавления вышеуказанного мы нажимаем Ctrl + O для сохранения, Enter для подтверждения и Ctrl + X для выхода.
Из того, что мы ввели, «[доверенный = да]» — вот что отмечает его как заслуживающий доверия, то идет URL-адрес репозитория, и «hirsute» будет обозначением версии, 21.10 в случае Ubuntu. Как мы уже объясняли, он также работает в Ubuntu 22.04, где выдает ошибку просто потому, что он еще не доступен для версии, которая будет выпущена в апреле следующего года.
И все. Это простой процесс это может избавить нас от многих головных болей, но мы не должны исключать возможность того, что это даст нам еще один. Лично я бы рекомендовал его только для программного обеспечения, которое нам нужно и которое недоступно другими способами, но этому есть объяснение.
Содержание статьи соответствует нашим принципам редакционная этика. Чтобы сообщить об ошибке, нажмите здесь.
Вы можете быть заинтересованы
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Closed
TonderaiZR opened this issue
Feb 20, 2018
· 8 comments
Comments
Hello
I need some help as I am receiving the error below every time I am running sudo apt-get update.
Please help
W: GPG error: https://raw.githubusercontent.com/DT42/BerryNet-repo/master stretch InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A3211A87D7ACFE23
E: The repository ‘https://raw.githubusercontent.com/DT42/BerryNet-repo/master stretch InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
@tondy @tuansacer Sorry for hitting the issue because you find the easter egg!
We’re working on Python-based BerryNet which has not been announced yet.
To resolve this issue, please use this command below:
$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys A3211A87D7ACFE23
$ sudo apt update
I will keep this issue open until Python-based BerryNet is announced officially.
This issue is fixed in v2.3.0.
i am facing same problem. help me
remove sources .list and index.html in /etc/apt dir
cp /etc/apt/preferences.d/index.html /tmp
rm -rf /etc/apt/preferences.d/index.html
#cp /etc/apt/sources.list /tmp
rm -rf sources.list
@tondy @tuansacer Sorry for hitting the issue because you find the easter egg!
We’re working on Python-based BerryNet which has not been announced yet.
To resolve this issue, please use this command below:
$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys A3211A87D7ACFE23 $ sudo apt updateI will keep this issue open until Python-based BerryNet is announced officially.
Each time I try these type of fixes it just says «command not found» in debian 9.5
Hi PrinsZuko,
Can you check if sudo is installed? apt-key and apt must be run as root.
If your system admin doesn’t install «sudo» package, please install it first.