https://bugs.winehq.org/show_bug.cgi?id=52439
--- Comment #10 from Sveinar Søpler cybermax@dexter.no --- (In reply to Osamu Aoki from comment #8)
Hi,
Sveinar, We are talking about cryptographic key mechanism which is used by the software package management tool APT during the normal package update. Without having public key installed in advance, the package installation of packages from wine-hq signed repo will be rejected by APT.
For Distribution itself, installer can by-pass this restriction for the public key file package during the initial installation.
Distribution's key file package can be updated as long as it is signed by a installed key. So something similar can be used to update the key file if wine-hq changes its public and secret key pair.
Cheers,
Osamu
Not really sure why you felt this was relevant?
(In reply to jkfloris from comment #9)
I think it is most convenient for the end user to have one manual that works everywhere. The following approach works on Debian Buster, Bullseye and Bookworm and I expect that it should not cause any problems on Ubuntu either.
Yeah, worked fine for Ubuntu 20.04 too. Don't have 18.04 installed atm, so can't tell if it would work there. 18.04 uses apt_1.6 vs. Buster uses 1.8. (It should work from apt>=1.1 onwards i think, but maybe needs testing?)
--- Types: deb URIs: https://dl.winehq.org/wine-builds/ubuntu Suites: focal Components: main Architectures: amd64 i386 Signed-By: /usr/share/keyrings/winehq-archive.key ---
So, only thing needed really is to provide .sources file for the various distro's and a minor update to the install wiki's.