[winswitch] public keys

[Mark Couteau]

Thank you.

The detailed instructions on the page fixed it.

I did get a configured multiple times warning, but was

able to remove xpra from 
/etc/apt/sources.list.d/additional-repositories.list

and it went away. My distro is Jammy.

for reference:

Step by step example for installing the stable repository on Ubuntu 
Focal Fossa

|DISTRO=jammy #install https support for apt (which may be installed 
already): sudo apt-get update sudo apt-get install apt-transport-https 
software-properties-common sudo apt install ca-certificates # add Xpra 
GPG key(s) sudo wget -O "/usr/share/keyrings/xpra-2022.gpg" 
https://xpra.org/xpra-2022.gpg # older distributions may also need: # 
sudo wget -O "/usr/share/keyrings/xpra-2018.gpg" 
https://xpra.org/xpra-2018.gpg # add Xpra repository wget -O 
"/etc/apt/sources.list.d/xpra.list" 
https://xpra.org/repos/$DISTRO/xpra.list # optional beta channel: # wget 
-O "/etc/apt/sources.list.d/xpra-beta.list" 
https://xpra.org/repos/$DISTRO/xpra-beta.list # install Xpra package 
sudo apt-get update sudo apt-get install xpra |

For other distributions, simply change |DISTRO| to match your 
distribution name.

MEC

On 9/15/22 09:33, Antoine Martin via shifter-users wrote:
> On 14/09/2022 02:46, Mark Couteau via shifter-users wrote:
> > Hello List:
> >
> > I keep having a failure to update from the xpra software server due 
> to a
> > public key issue.
> >
> > I'm not very familiar with this sort of thing.
> >
> > Here is the error message from the apt update command on Linux Mint 21
> > Vanessa.
> >
> > Hit:9 https://xpra.org jammy InRelease
> > Err:9 https://xpra.org jammy InRelease
> >  ? The following signatures couldn't be verified because the public key
> > is not available: NO_PUBKEY 18ADB31CF18AD6BB
> > Reading package lists... Done
> > Building dependency tree... Done
> > Reading state information... Done
> > All packages are up to date.
> > W: An error occurred during the signature verification. The repository
> > is not updated and the previous index files will be used. GPG error:
> > https://xpra.org jammy InRelease: The following signatures couldn't be
> > verified because the public key is not available: NO_PUBKEY
> > 18ADB31CF18AD6BB
> > W: Failed to fetch https://xpra.org/dists/jammy/InRelease? The 
> following
> > signatures couldn't be verified because the public key is not 
> available:
> > NO_PUBKEY 18ADB31CF18AD6BB
> > W: Some index files failed to download. They have been ignored, or old
> > ones used instead.
> >
> > Any help is appreciated.
> You have not specified how you installed xpra or which GPG keys you have
> imported.
> Did you follow the instructions here:
> https://github.com/Xpra-org/xpra/wiki/Download#-for-debian-based-distributions 
>
> Or something else?
>
> The gory details explaining why we now have 2 different sets of keys for
> signing the packages is explained here:
> https://github.com/Xpra-org/xpra/issues/3499#issuecomment-1077136429
>
> Cheers,
> Antoine
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> https://lists.devloop.org.uk/mailman/listinfo/shifter-users