When will the Chromium PPA be CORRECTLY updated?

Asked by Snooper on 2020-01-29

When will the Chromium PPA be CORRECTLY updated?
There is NO INFORMATION (That is NOT OUTDATED) in the Ubuntu Help addressing how to get the CORRECT current PPA.

Err:12 http://ppa.launchpad.net/libratbag-piper/piper-libratbag-git/ubuntu xenial Release
  404 Not Found [IP: 91.189.95.83 80]
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/chrome/deb stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 78BD65473CB3BD13
E: The repository 'http://ppa.launchpad.net/libratbag-piper/piper-libratbag-git/ubuntu xenial Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu ubuntu-docs Edit question
Assignee:
No assignee Edit question
Last query:
2020-01-29
Last reply:
2020-01-29
Manfred Hampl (m-hampl) said : #1

If you have problems with a PPA you have to contact the provide of that PPA.

PPAs are "Personal Package Archives" outside the responsibility of the Ubuntu developers amd Canonical.
The responsibility lies fully in the hands of the provider of the PPA.

Since Ubuntu is not responsible for PPAs, you cannot expect to find instructions on Ubuntu Help "how to find the correct PPA". All Ubuntu Software is in the Ubuntu repositories, and not in PPAs.

In your case:
go to https://launchpad.net/~libratbag-piper/+archive/ubuntu/piper-libratbag-git
You will see a hint what to do in case of questions, but you should also be able to see that that PPA does not provide software for Ubuntu xenial. Who told you to add this PPA? It does not work with Ubuntu xenial!

And for the "NO_PUBKEY" message: Just do a web search for that message and you will see hundreds of instructions how to correct that with an "apt-key ..." command.

Can you help with this problem?

Provide an answer of your own, or ask Snooper for more information if necessary.

To post a message you must log in.