Open paulmenzel opened 3 years ago
Purging the package jitsi-archive-keyring again, and manually installing the keyring as described in the Self-Hosting Guide worked around the issue. (s/stable/unstable/
for my usecase.)
curl https://download.jitsi.org/jitsi-key.gpg.key | sudo sh -c 'gpg --dearmor > /usr/share/keyrings/jitsi-keyring.gpg'
echo 'deb [signed-by=/usr/share/keyrings/jitsi-keyring.gpg] https://download.jitsi.org unstable/' | sudo tee /etc/apt/sources.list.d/jitsi-unstable.list > /dev/null
The the packages could be installed. It looks like jitsi-meet also has some scripts to remove the old key.
Setting up jitsi-meet (2.0.5792-1) ...
We found the old key EF8B479E2DC1389C, which is no longer valid and we removed it.
Still a working upgrade path to rotate keys seems to be missing.
Still a working upgrade path to rotate keys seems to be missing.
Yes, this is known and we will work on fixing that. This concerns all debian packages we create.
Purging the package jitsi-archive-keyring again, and manually installing the keyring ...
Purging the package also solved the NO_PUBKEY B4D2D216F1FD7806 issue for me. Chased my tail for much time until google-fu got me to that comment - thanks for making it. Wish the solution had been more prominent in my googling. Maybe this comment will help with that. Manual install done but not helpful until.
Did purge, but remove might have worked too.
# apt-get purge jitsi-archive-keyring
is what fixed the problem for me, however, it auto-removed jitsi too.
# apt-get install jitsi
showed it did nothing - so the auto-removed jitsi apt-get message seems not credible.
With
running
apt update
, the messages below are shown.Installing
jitsi-archive-keyring/unstable
does not help either.