[pkg-wine-party] Bug#585409: Bug#585409: wine 1.2/1.3 on Debian: what's the blocker?

Michael Gilbert michael.s.gilbert at gmail.com
Sun Nov 20 23:26:19 UTC 2011

On Sun, Nov 20, 2011 at 5:59 PM, Stephen Kitt wrote:
> The blocker's effectively Ove - after I did what was necessary to get
> wine-gecko into Debian (with a sourceful rebuild, not just repackaging
> upstream's binaries) I was hoping Wine uploads would resume and we'd catch up
> with upstream within a reasonable timeframe. Unfortunately only four releases
> followed, packaging three upstream versions (1.1.33 to 1.1.35 inclusive), and
> since August there hasn't been any activity, including in the git repository.
> Ove's reason for uploading every single version of Wine is so that all
> versions of Wine end up available in the Debian snapshots archive, which can
> come in handy given that some Windows programs work better with older
> versions of Wine. It also means changes to the contents of Wine releases and
> packaging requirements can be made progressively.
> Unfortunately we're so far behind now that even with one release a day it
> would take a month and a half to catch up (10 remaining 1.1.x versions, 7 1.2
> release candidates, 4 1.2.x versions and 34 1.3.x versions), not counting
> updating wine-gecko, and the effort involved seems enormous to me - at least
> I don't have the time and energy for that.

Couldn't this be greatly simplified if only the 1.2.x (stable)
versions were uploaded?  I assume the plan is to release wheezy with
one of the stable wine releases (either 1.2.x or 1.4.x if its ready in
time); thus nothing really needs to be done with wine-unstable
(especially since that is never going into a stable Debian release);
let's just work on wine.

Best wishes,

More information about the pkg-wine-party mailing list