What is wrong with this Debian to update Vivaldi?
-
I have not updated Vivaldi since several weeks, and i decided to do this today. I use Debian 11, and my Vivaldi version is 4.0.2312.33 (Stable channel) stable (64 bits).
I have this repository configured:
URI: https://repo.vivaldi.com/stable/deb/
distribution: stable
section: mainBut when i ask synaptic to refresh the package data, it gives me this error:
The translation of it is something like:
It was not possible to download all repository indexes
The repository may not be available anymore, or a contact with it was not possible for a network blackout. If available, an older index version might be used. Check your network connection is working, and the repository settings is correct.
An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.vivaldi.com/stable/deb stable Release: As assinaturas a seguir não puderam ser verificadas devido à chave pública não estar disponível: NO_PUBKEY FEB6023DC27AA466Falhou ao buscar https://repo.vivaldi.com/stable/deb/dists/stable/Release.gpg As assinaturas a seguir não puderam ser verificadas devido à chave pública não estar disponível: NO_PUBKEY FEB6023DC27AA466Falhou o download de alguns ficheiros de índice. Foram ignorados ou os antigos foram usados em seu lugar.
How can i fix this problem, and be able to update Vivaldi again?
-
@dedeco Hi. After reading your post, i fired up my SparkyLinux [=Debian 11 Testing] KDE VM, installed V-Stable
5.1.2567.57-1
from the repos, launched it to confirm correct operation, then checked its configured repo:Ie, it appears to be identical to yours. Unfortunately, given this was a fresh installation, i can't yet verify if it updates properly or not, but i'll let you know later [unless in the meantime your problem is solved].
EDIT:
OMZ, i just realised how obsolete your current V is!
4.0.2312.33
I suspect you're going to need to install a new instance of V; there's been many big V changes since your old version.
//Added a bit later: If you uninstall your obsolete version, then fresh-install the current version, you will not lose any of your data, as that will stay safe in your
$HOME/.config/vivaldi
directory. -
See this
tl;dr:
/etc/apt/sources.list.d/vivaldi-archive.list
contains a fixed key that did not roll over correctly. You can verify this by looking at the file and finding the stringdeb [signed-by=/usr/share/keyrings/vivaldi-browser.gpg
If this is the case, this command should solve your issue:wget -qO- https://repo.vivaldi.com/archive/linux_signing_key.pub | gpg --dearmor | sudo dd of=/usr/share/keyrings/vivaldi-browser.gpg
-
@jumpsq said in What is wrong with this Debian to update Vivaldi?:
See this
tl;dr:
/etc/apt/sources.list.d/vivaldi-archive.list
contains a fixed key that did not roll over correctly. You can verify this by looking at the file and finding the stringdeb [signed-by=/usr/share/keyrings/vivaldi-browser.gpg
If this is the case, this command should solve your issue:wget -qO- https://repo.vivaldi.com/archive/linux_signing_key.pub | gpg --dearmor | sudo dd of=/usr/share/keyrings/vivaldi-browser.gpg
This command did not fix the situation here. After running this line as root, i tried to update the repository data, but still get a GPG error with Vivaldi repository:
Erro GPG: http://repo.vivaldi.com/stable/deb stable Release: As assinaturas a seguir não puderam ser verificadas devido à chave pública não estar disponível: NO_PUBKEY FEB6023DC27AA466The repository 'http://repo.vivaldi.com/stable/deb stable Release' is not signed.
I will uninstall and reinstall Vivaldi, then.
-
@dedeco I tested with a old 4.0 Stable deb package on my Debian 11.
This can help to add the key in terminal:
wget -qO- https://repo.vivaldi.com/archive/linux_signing_key.pub | sudo apt-key add -
-
@doctorg removing the keyring file may affect other 3rd party repos.
@dedeco the 2nd line (wget … | sudo …
) is sufficient.Vivaldi
tries to ship the GPG keys for its repo in the same package.
Keys provided by ancient versions are not usable/used anymore (expired).
A pure uninstall and reinstall fromdeb
file should be the cleanest approach.@jumpsq given the archive path (
https://repo.vivaldi.com/stable/deb/
) a manual repo setup is unlikely in this case. -
@becm said in What is wrong with this Debian to update Vivaldi?:
A pure uninstall and reinstall from deb file should be the cleanest approach
Hmmmm, now where have i heard that idea, recently...?
-
@becm said in What is wrong with this Debian to update Vivaldi?:
@doctorg removing the keyring file may affect other 3rd party repos.
Yes, you are true. That can be a risk.
I will remove the line now in post.