[pkg-wine-party] Debian wine package maintenance / debian bug 479659

Austin English austinenglish at gmail.com
Sat Nov 13 23:22:41 UTC 2010

Howdy Ove,

I've seen quite a few people asking for Wine on Debian recently. I've
read up on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479659, as
well as a few other pages. I got your git repository from
http://pkg-wine.alioth.debian.org/, and after a bit of setup, got it
to compile the 1.1.33 debs.

I'd like to take over maintaining the Debian Wine packages, presumably
with your mentoring/sponsoring.

For reference, I've uploaded the 1.1.33 debs I made to
http://www.austinenglish.com/wine-1.1.33.tar (sha1sum:

Please check these and let me know if they look okay. The install okay
for me on squeeze32.

If so, we can get started and get debian wine up to date :-).

A few starting questions:
Do I need a 64-bit debian machine to make the build, or will it be
enough to make the 32-bit packages and have the build bots take care
of 64 bit.
Same for old debian versions, will the build bots take care of this?

Should my first 'real' package be 1.1.34, or 1.2?

I also noticed that wine --version reports wine-1.1.33-359-g680678e,
e.g., it's reporting the git sha1, rather than wine-1.1.33 or
wine-1.1.33-debian1 or something. The package is named correctly, just
wine is screwing it up...Has this always been a problem, or did I do
something wrong?


More information about the pkg-wine-party mailing list