https://bugs.winehq.org/show_bug.cgi?id=46356
Bug ID: 46356 Summary: Debian testing wine-hq repo is misconfigured on the server Product: Wine Version: 3.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: shtetldik@gmail.com Distribution: ---
I set WineHQ repo source for Debian testing as follows:
deb https://dl.winehq.org/wine-builds/debian/ testing main
It used to work fine until very recently. Now, I'm getting this when trying to run apt-get update:
W: Conflicting distribution: https://dl.winehq.org/wine-builds/debian testing InRelease (expected testing but got )
https://bugs.winehq.org/show_bug.cgi?id=46356
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Product|Wine |Packaging Component|-unknown |wine-packages CC| |michael@fds-team.de, | |sebastian@fds-team.de Version|3.20 |unspecified
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #1 from Shmerl shtetldik@gmail.com --- I also see such messages:
E: Repository 'https://dl.winehq.org/wine-builds/debian testing InRelease' changed its 'Suite' value from 'buster' to 'testing' E: Repository 'https://dl.winehq.org/wine-builds/debian testing InRelease' changed its 'Codename' value from '' to 'buster' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #2 from Shmerl shtetldik@gmail.com --- I did this to accept the change:
sudo apt-get --allow-releaseinfo-change update
https://bugs.winehq.org/show_bug.cgi?id=46356
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #3 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to Shmerl from comment #0)
I set WineHQ repo source for Debian testing as follows:
deb https://dl.winehq.org/wine-builds/debian/ testing main
That's incorrect, and was never what our instructions said to do, even if it somehow managed to work for you before.
Please follow the instructions on https://wiki.winehq.org/Debian.
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #4 from Shmerl shtetldik@gmail.com --- (In reply to Rosanne DiMesio from comment #3)
That's incorrect, and was never what our instructions said to do, even if it somehow managed to work for you before.
Please follow the instructions on https://wiki.winehq.org/Debian.
Those instructions aren't flexible, because they don't allow using generic distro name like testing. Rolling Debian setups simply point to testing, not to named releases.
That's how for example my main Debian repo is set up:
deb http://ftp.us.debian.org/debian/ testing main contrib non-free deb-src http://ftp.us.debian.org/debian/ testing main contrib non-free
deb http://security.debian.org/debian-security testing/updates main contrib non-free deb-src http://security.debian.org/debian-security testing/updates main contrib non-free
Please set up Wine repo in the similar fashion. I already opened a bug about it in the past, and Wine developers responded that it would be taken care of.
See bug 42735.
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #5 from Rosanne DiMesio dimesio@earthlink.net --- The WineHQ repository structure has been changed to sync with the OBS, which uses a flat repository structure rather than a Debian-style one. That's why you got those messages about accepting changes. So no, we cannot go back to a strict Debian-style structure.
The good news for you is that you can get your Testing packages directly from the OBS repository, which is set up as a rolling release.
Just download and install the OBS release key (https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/Debian_Te...) and add the repository to your /etc/apt/sources.list: https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/Debian_Te... ./
Note the ./ at the end; that's needed because of the flat structure.
Note also that the OBS only has the latest packages, so if you ever have to downgrade for some reason, you will have to get the old package from the archive here.
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #6 from Shmerl shtetldik@gmail.com --- Thanks for the pointer! Though accepting the change above removed the warnings, so I'm good for now using the wine hq repo.
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #7 from Rosanne DiMesio dimesio@earthlink.net --- Closing invalid packaging bug.
https://bugs.winehq.org/show_bug.cgi?id=46356
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Rosanne DiMesio dimesio@earthlink.net --- Really closing this time...
https://bugs.winehq.org/show_bug.cgi?id=46356
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED
--- Comment #9 from Alexandre Julliard julliard@winehq.org --- Actually the suite name was missing from the release files, this is fixed now so you can use 'testing' as a distro name.
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #10 from Shmerl shtetldik@gmail.com --- Something happened to it again:
Reading package lists... Done W: Conflicting distribution: https://dl.winehq.org/wine-builds/debian testing InRelease (expected testing but got buster) E: Repository 'https://dl.winehq.org/wine-builds/debian testing InRelease' changed its 'Suite' value from 'testing' to 'buster' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. Aborting on non zero error code: 100!
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #11 from Alexandre Julliard julliard@winehq.org --- Yes, the bug crept back in, sorry about that. It's fixed again now.
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #12 from Shmerl shtetldik@gmail.com --- Strangely though, my wine stopped updating on 4.0~rc7~buster, even though 4.0 is already in the repo:
https://dl.winehq.org/wine-builds/debian/dists/testing/main/binary-amd64/
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #13 from Shmerl shtetldik@gmail.com --- OK, something strange is going on. I downloaded deb packages and installed them manually. Somehow Debian thought it's downgrading them:
dpkg: warning: downgrading wine-devel from 4.0~rc7~buster to 4.0~buster (Reading database ... 211863 files and directories currently installed.) Preparing to unpack wine-devel_4.0~buster_amd64.deb ... Unpacking wine-devel (4.0~buster) over (4.0~rc7~buster) ... dpkg: warning: downgrading wine-devel-amd64 from 4.0~rc7~buster to 4.0~buster Preparing to unpack wine-devel-amd64_4.0~buster_amd64.deb ... Unpacking wine-devel-amd64 (4.0~buster) over (4.0~rc7~buster) ... dpkg: warning: downgrading wine-devel-i386:i386 from 4.0~rc7~buster to 4.0~buster Preparing to unpack wine-devel-i386_4.0~buster_i386.deb ... Unpacking wine-devel-i386:i386 (4.0~buster) over (4.0~rc7~buster) ... dpkg: warning: downgrading winehq-devel from 4.0~rc7~buster to 4.0~buster Preparing to unpack winehq-devel_4.0~buster_amd64.deb ... Unpacking winehq-devel (4.0~buster) over (4.0~rc7~buster) ... Setting up wine-devel-amd64 (4.0~buster) ... Setting up wine-devel-i386:i386 (4.0~buster) ... Setting up wine-devel (4.0~buster) ... Setting up winehq-devel (4.0~buster) ...
https://bugs.winehq.org/show_bug.cgi?id=46356
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dimesio@earthlink.net
--- Comment #14 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to Shmerl from comment #13)
OK, something strange is going on. I downloaded deb packages and installed them manually. Somehow Debian thought it's downgrading them:
Yes, package managers think 4.0-rc7 is newer than 4.0 because of the rc7. There's nothing we can do about that. When 4.1 is released it will solve that problem (until next year).
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #15 from Shmerl shtetldik@gmail.com --- For now I just set these packages on hold, otherwise it tries to "upgrade" them to 4.0~rc7 back.
May be usage of tilde creates a problem? I.e. 4.0~rc7 instead of 4.0-rc7? For instance Linux kernels often have rc# in them and work just fine when upgrading. But they use dash:
5.0.0-rc4 and so on.
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #16 from Michael Müller michael@fds-team.de --- As package maintainer, you can always adjust the version string of the package to match the version scheme of the distribution:
dpkg --compare-versions 4.0.0~buster gt 4.0~rc7~buster && echo true
true
dpkg --compare-versions 4.0-0~buster gt 4.0~rc7~buster && echo true
true
dpkg --compare-versions 4.0-buster gt 4.0~rc7-buster && echo true
true
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #17 from Shmerl shtetldik@gmail.com --- Good point. Using 4.0.0 can work indeed.
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #18 from Shmerl shtetldik@gmail.com --- It's interesting that 4.0~buster < 4.0~rc7~buster, but 4.0-buster > 4.0~rc7-buster.
https://bugs.winehq.org/show_bug.cgi?id=46356
--- Comment #19 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to Michael Müller from comment #16)
dpkg --compare-versions 4.0.0~buster gt 4.0~rc7~buster && echo true
true
That one is viable; I'll remember it for next year.
-
wine-bugs＠winehq.org