When I run this command, it says it cannot resolve the name.
If I use the http://127.0.0.1:8082 proxy, I get a 403 and then an error message saying that the name could not be resolved.I think it would be easier after that if I could wget, but is there any solution?
gpg: directory '/home/user/.gnupg' created
gpg: keybox '/home/user/.gnupg/pubring.kbx' created
gpg: key 76F1A20FF987672F: 1 signature not checked due to a missing key
gpg: /home/user/.gnupg/trustdb.gpg: trustdb created
gpg: key 76F1A20FF987672F: public key "WineHQ packages <wine-devel@winehq.org>" imported
gpg: Total number processed: 1
gpg: imported: 1
gpg: no ultimately trusted keys found
This is the answer to your topic’s subject.
From there, you can install wine.
Be aware that prior to all of this, if your system is 64 bit, you’d need to enable 32 bit architecture (if you haven’t already):
sudo dpkg --add-architecture i386
EDIT: don’t forget to add repository to /etc/apt/sources.list and to run apt update after this. I’m adding it manually, usually:
sudo nano /etc/apt/sources.list
Now add the package repository line to the file and save it:
deb https://dl.winehq.org/wine-builds/debian bookworm main
Finally run apt update and install winehq-staging, I’d suggest.
I also ran this and added the sources.list manually, but when I do an apt-update, it seems that the repository is not signed and cannot be updated. The following signature could not be verified because the public key is not available. The following signature could not be verified because the public key is not available.
Do I need to change multiple configuration items? If it is easy to import repositories etc. with wget without using curl, simply by loading the script into a template, I would like to try it.
For the time being, what seems to be easy to do? One method is
I tried running this in a template, but the name resolution error message did not change.
I have also tried a workaround using curl, but this time I cannot verify the public key and cannot proceed. For me, even if I have to use curl, it is OK if I can get it right, and if I can also authenticate the public key, the existing system is OK enough. I don’t want to risk having to re-install the system if I don’t want to change the settings.
Yes, the newly presented command is still able to retrieve winehq.key. However, when sudo apt update, the repository is not signed, and updates cannot be safely performed from such a repository, and updates are disabled by default.
If the public key of the repository in winehq.key were available, I would be able to check the signature and apt update would be successfully defeated…
Great to hear you made it, especially both ways. Please pick one post and choose it as a solution so it could help future users too. This is question very, very often asked. I’d leave this topic as is then, to be short. If issues arise in further stages, I’d open separate topics for them. People tend to find answers ASAP while reading ALAP, haha.