[pkg-wine-party] Bug#889158: Package wine-development is less recent than wine

Jens Reyer jre.winesim at gmail.com
Mon Feb 5 21:20:47 UTC 2018


On 02/02/2018 08:10 PM, Joerg Schiermeier, Bielefeld/Germany wrote:
> the package version of 'wine-development' is lower than the version of 'normal' wine:
> 
> wine-development: 3.0~rc6-1
> wine: 3.0-1
> 
> Since January 18th, 2018 until today the WineHQ versions were set to v3.0. This was the version from their stable wine and also from their developer version of wine.
> So this should also be in Debians package 'wine' and 'wine-development'! The version of 'wine-development' has to be minimum the version of 'wine' and not below. This is what the prefix '-development' means. Or not? Maybe I'm wrong.
> And: No, I didn't want to change the packages in my installation from 'wine-development' to 'wine' for this period of same version between WinHQs 'Wine stable release' and WineHQs 'Wine development release'
> 
> So this is a bug.

No.  Latest is not the same as development.  I didn't see 3.0 offered
upstream as -development (at least it's not in
https://dl.winehq.org/wine/source/3.x/), but that wouldn't change my mind.

And because of the duplication I definitely won't package stable 3.0
also as src:wine-development.

An exception to my first point might be if the stable upstream release
is too late in the Debian release cycle, so that src:wine gets the
previous stable, and src:wine-development the current stable release -
but currently we're just in the middle of the release cycle.

I'm just packaging 3.1 which will close this bug anyway.  If you just
wanted to request that version packaged: 36 minutes after its release is
a bit early.  But you're interest in wine-development is appreciated!

Greets
jre



More information about the pkg-wine-party mailing list