https://bugs.winehq.org/show_bug.cgi?id=53688
Bug ID: 53688 Summary: Ubuntu install instruction are wrong and not working Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs@winehq.org Reporter: sayanel@protonmail.com Distribution: ---
As of today (2022-09-15) the ubuntu install instructions (https://wiki.winehq.org/Ubuntu) do not work properly
The repo key is placed in /usr/share/keyrings
But the source info (https://dl.winehq.org/wine-builds/ubuntu/dists/jammy/winehq-jammy.sources) indicates to search /etc/apt/keyrings/
Either change instruction to copy the key to /etc or change the .source file to point to /usr
https://bugs.winehq.org/show_bug.cgi?id=53688
--- Comment #1 from sayanel sayanel@protonmail.com --- Note: the switch from /usr to /etc is only for ubuntu 22.04
Older versions (18.04, 20.04) are fine
https://bugs.winehq.org/show_bug.cgi?id=53688
jkfloris@dds.nl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jkfloris@dds.nl
--- Comment #2 from jkfloris@dds.nl --- You are right, the instructions should be updated.
Unfortunately, not all servers are synchronized yet. For me, the Signed-By line still points to /usr/share/keyrings
--- $ host dl.winehq.org dl.winehq.org is an alias for osff.map.fastly.net. osff.map.fastly.net has address 151.101.38.217
$ lynx -dump https://dl.winehq.org/wine-builds/ubuntu/dists/jammy/winehq-jammy.sources Types: deb URIs: https://dl.winehq.org/wine-builds/ubuntu Suites: jammy Components: main Architectures: amd64 i386 Signed-By: /usr/share/keyrings/winehq-archive.key ---
I expect that the servers will be synchronized soon.
I recommend you move the key from /usr/share/keyrings to /etc/apt/keyrings
https://bugs.winehq.org/show_bug.cgi?id=53688
--- Comment #3 from jkfloris@dds.nl --- Resolved
The wiki has been updated.
https://bugs.winehq.org/show_bug.cgi?id=53688
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |instantrice@gmail.com
--- Comment #4 from Ken Sharp imwellcushtymelike@gmail.com --- *** Bug 53543 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=53688
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abcfy2@163.com
--- Comment #5 from Ken Sharp imwellcushtymelike@gmail.com --- *** Bug 53535 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=53688
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Summary|Ubuntu install instruction |winehq-jammy.sources is |are wrong and not working |incorrect Severity|normal |major Status|UNCONFIRMED |NEW
--- Comment #6 from Ken Sharp imwellcushtymelike@gmail.com --- https://dl.winehq.org/wine-builds/ubuntu/dists/jammy/winehq-jammy.sources
Signed-By: /usr/share/keyrings/winehq-archive.key
NEEDS to be
Signed-By: /etc/apt/keyrings/winehq-archive.key
https://bugs.winehq.org/show_bug.cgi?id=53688
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |imwellcushtymelike@gmail.co | |m
https://bugs.winehq.org/show_bug.cgi?id=53688
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |53554
https://bugs.winehq.org/show_bug.cgi?id=53688
--- Comment #7 from jkfloris@dds.nl --- When I look at geopeeker.com, the change has been implemented on several servers and not on others. Why the sync takes so long is also a mystery to me.
https://bugs.winehq.org/show_bug.cgi?id=53688
--- Comment #8 from Ken Sharp imwellcushtymelike@gmail.com --- Interesting. I wonder if the cache can be flushed. Need an admin to do this.
https://bugs.winehq.org/show_bug.cgi?id=53688
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu
--- Comment #9 from Ken Sharp imwellcushtymelike@gmail.com --- This is still incorrect in the UK. Obviously someone (an admin) needs to force a cache flush.
https://bugs.winehq.org/show_bug.cgi?id=53688
Ulf Zibis Ulf.Zibis@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Ulf.Zibis@gmx.de
--- Comment #10 from Ulf Zibis Ulf.Zibis@gmx.de --- (In reply to Ken Sharp from comment #6)
https://dl.winehq.org/wine-builds/ubuntu/dists/jammy/winehq-jammy.sources
Signed-By: /usr/share/keyrings/winehq-archive.key
NEEDS to be
Signed-By: /etc/apt/keyrings/winehq-archive.key
This seems to be fixed now.
https://bugs.winehq.org/show_bug.cgi?id=53688
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED
--- Comment #11 from Ken Sharp imwellcushtymelike@gmail.com --- Yup
https://bugs.winehq.org/show_bug.cgi?id=53688
--- Comment #12 from jkfloris@dds.nl --- Are you sure? According to geopeeker.com, the server in Singapore is still pointing to /usr/share
https://bugs.winehq.org/show_bug.cgi?id=53688
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED
--- Comment #13 from Ken Sharp imwellcushtymelike@gmail.com --- True. It doesn't look like anyone is going to fix it though.
https://bugs.winehq.org/show_bug.cgi?id=53688
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.wheez@gmail.com
--- Comment #14 from Ken Sharp imwellcushtymelike@gmail.com --- *** Bug 53662 has been marked as a duplicate of this bug. ***