Bug#889158: [pkg-wine-party] Bug#889158: Package wine-development is less recent than wine
On 02/10/2018 06:58 PM, Joerg Schiermeier, Bielefeld/Germany wrote: > Jens Reyer wrote: >> Still, I'd love to understand what this bug was about. > Maybe I'm too "German": Maybe, welcome in the club ;) > in WinHQ.orgs website both version were set to 3.0 when wine v3.0 was > published. "wine-development" didn't follow this. > In my point of view this was an error, which means: a bug. Every time when > WineHQ.org publish a stable version also "wine-development" should have the > same version as "wine". This will happen only one time a year. I agree the current solution is not optimal, but duplicating one release in two source package is not an option in Debian (tell me if I'm wrong here). If there's any other idea how to handle this, I'd be happy to look into it, especially for the next release, which will probably be shortly before the next Debian freeze/release (buster). > At the end (this is to Jens Reyer): > ¡Thank you for your great work about wine in Debian! Thanks a lot! But I can't do the intensity of Wine releated work, as I did it recently, on a permanent basis. I'm really just a part of this team, and I hope to see others (old and new) to contribute here more again. Greets jre
Bug#889158: [pkg-wine-party] Bug#889158: Package wine-development is less recent than wine
[Adding the bugreport back in the address field] On 02/06/2018 06:56 PM, Joerg Schiermeier, Bielefeld/Germany wrote: > WineHQ | Debian Package > > stable version == wine > devel. version == wine-development > > Is this correct? Yes, that's correct. And it's what we are doing: wine: 1.8.x, 2.0.x, 3.0.x (all stable releases) wine-development: 2.1, 2.2, ..., 2.22, 3.0-rcx (all development releases, and release candidates) Maybe it's about the release candidates and where to put them? For the 1.8 release they were in wine, for 2.0 and 3.0 in wine-development. You wrote: > The version of 'wine-development' has to be minimum the version of > 'wine' and not below. This is correct 52 weeks a year, but not when the stable release is the most recent release. So if the latest release is 3.0 (stable) and the previous release 3.0-rc6 (development) then we will (and did) ship a higher version number in wine: wine/3.0-1 wine-development/3.0~rc6-1 > If not you may close this bug as solved/won't fix please. I'll close it with wine-development/3.1-1. Still, I'd love to understand what this bug was about. Greets jre
