Debian Bug report logs - #479659
RFH: wine -- Windows API implementation

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Ove Kaaven <ovek@arcticnet.no>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: RFH: wine -- Windows API implementation

Date: Tue, 06 May 2008 03:09:08 +0200

Package: wnpp
Severity: normal

Since my time may be limited in the future, I am seeking comaintainers
for the Wine package in Debian, at least to ensure that new Wine releases
may continue to be uploaded in a timely fashion, and to keep the package's
bug count down. (And given that pretty much half the open bugs are "missing
manpage" bugs, documentation writers would also help...)

I have created a project for this on alioth.debian.org. I've loaded the
current packaging (all versions since etch) into a Git repository there, and
put up some instructions on http://pkg-wine.alioth.debian.org/

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.ISO-8859-1, LC_CTYPE=en_US.ISO-8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Message #10 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Reinhard Tartler <siretart@debian.org>

To: Ove Kaaven <ovek@arcticnet.no>

Cc: 479659@bugs.debian.org, Scott Ritchie <scottritchie@ubuntu.com>, Stephan Hermann <sh@linux-server.org>

Subject: Re: Bug#479659: RFH: wine -- Windows API implementation

Date: Tue, 06 May 2008 09:16:44 +0200

Ove Kaaven <ovek@arcticnet.no> writes:

> Package: wnpp
> Severity: normal
>
> Since my time may be limited in the future, I am seeking comaintainers
> for the Wine package in Debian, at least to ensure that new Wine releases
> may continue to be uploaded in a timely fashion, and to keep the package's
> bug count down. (And given that pretty much half the open bugs are "missing
> manpage" bugs, documentation writers would also help...)
>
> I have created a project for this on alioth.debian.org. I've loaded the
> current packaging (all versions since etch) into a Git repository there, and
> put up some instructions on http://pkg-wine.alioth.debian.org/

Have you considered talking to Scott Ritchie <scottritchie@ubuntu.com>
and/or to Stephan Hermann <sh@linux-server.org>? They both have worked
on the wine package in ubuntu quite successfully AFAIS, and TBH, I don't
see a particular reason why the package should be diverged across the
two distributions.

I'm CC'ing the two in order to make them aware of this RFH bug and offer
sponsoring uploads, since the two are not DDs but UDs.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

Message #15 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Stephan Hermann <sh@sourcecode.de>

To: Reinhard Tartler <siretart@debian.org>

Cc: Ove Kaaven <ovek@arcticnet.no>, 479659@bugs.debian.org, Scott Ritchie <scottritchie@ubuntu.com>

Subject: Re: Bug#479659: RFH: wine -- Windows API implementation

Date: Tue, 6 May 2008 09:50:08 +0200

hi Ove, Reinhard, Scott,

On Tue, 06 May 2008 09:16:44 +0200
Reinhard Tartler <siretart@debian.org> wrote:

> Ove Kaaven <ovek@arcticnet.no> writes:
> 
> > Package: wnpp
> > Severity: normal
> >
> > Since my time may be limited in the future, I am seeking
> > comaintainers for the Wine package in Debian, at least to ensure
> > that new Wine releases may continue to be uploaded in a timely
> > fashion, and to keep the package's bug count down. (And given that
> > pretty much half the open bugs are "missing manpage" bugs,
> > documentation writers would also help...)
> >
> > I have created a project for this on alioth.debian.org. I've loaded
> > the current packaging (all versions since etch) into a Git
> > repository there, and put up some instructions on
> > http://pkg-wine.alioth.debian.org/
> 
> Have you considered talking to Scott Ritchie <scottritchie@ubuntu.com>
> and/or to Stephan Hermann <sh@linux-server.org>? They both have worked
> on the wine package in ubuntu quite successfully AFAIS, and TBH, I
> don't see a particular reason why the package should be diverged
> across the two distributions.
> 

the problem here is, that debian has a totally different structure
regarding the wine package.
If Debian, or actually Ove :), would like to go the way Ubuntu went
since Breezy, I think we can manage to provide a package which helps to
transition to new Wine World Order, derived from Scotts package.

It would make it also easier the Maintaing of the Ubuntu package,
because we can start to sync it from Debian in the Future.

IMHO, Scotts package is quite in a good shape, regarding support and
bugfixes + Win32 support on x86_64 archs...
We don't need to rely on anything else then some lib32* compiled
packages on amd64 and the stuff inside ia32-libs...

Furthermore, Ubuntus wine package does compile without any hassle on
lpia archs..

Ove, when you are interested to pick up Scotts Packages (he's the
winehq debian package maintainer actually) I think we would be glad to
help in the transition.

Regards,
\sh

PS: please use sh@sourcecode.de as email address in the future :)

Message #20 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Ove Kaaven <ovek@arcticnet.no>

To: Reinhard Tartler <siretart@debian.org>

Cc: 479659@bugs.debian.org, Scott Ritchie <scottritchie@ubuntu.com>, Stephan Hermann <sh@linux-server.org>

Subject: Re: Bug#479659: RFH: wine -- Windows API implementation

Date: Tue, 06 May 2008 09:52:07 +0200

Reinhard Tartler skrev:
> Have you considered talking to Scott Ritchie <scottritchie@ubuntu.com>
> and/or to Stephan Hermann <sh@linux-server.org>? They both have worked
> on the wine package in ubuntu quite successfully AFAIS, and TBH, I don't
> see a particular reason why the package should be diverged across the
> two distributions.

I don't have anything against them helping, but I don't think we agree 
on how to package Wine. For example, I (and some people who agree with 
me for some reason) think the package should be split (like other big 
packages in Debian) with each subpackage having strict dependencies, 
while Scott thinks it's better to make it one big package, with each 
Wine component working or failing (gracefully) according to what 
dependencies the user happen to have installed. That means our packages 
will be different.

I'm pretty sure they would have seen this RFH anyways since I did Cc 
wine-devel (which they presumably read) when filing it, but I only 
expected them to answer if they're fine not doing things the Ubuntu way 
- which pretty much means I don't *really* expect them to answer, I guess.

Message #25 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Stephan Hermann <sh@sourcecode.de>

To: Ove Kaaven <ovek@arcticnet.no>

Cc: Reinhard Tartler <siretart@debian.org>, 479659@bugs.debian.org, Scott Ritchie <scottritchie@ubuntu.com>

Subject: Re: Bug#479659: RFH: wine -- Windows API implementation

Date: Tue, 6 May 2008 10:00:22 +0200

hi,

On Tue, 06 May 2008 09:52:07 +0200
Ove Kaaven <ovek@arcticnet.no> wrote:

> Reinhard Tartler skrev:
> > Have you considered talking to Scott Ritchie
> > <scottritchie@ubuntu.com> and/or to Stephan Hermann
> > <sh@linux-server.org>? They both have worked on the wine package in
> > ubuntu quite successfully AFAIS, and TBH, I don't see a particular
> > reason why the package should be diverged across the two
> > distributions.
> 
> I don't have anything against them helping, but I don't think we
> agree on how to package Wine. For example, I (and some people who
> agree with me for some reason) think the package should be split
> (like other big packages in Debian) with each subpackage having
> strict dependencies, while Scott thinks it's better to make it one
> big package, with each Wine component working or failing (gracefully)
> according to what dependencies the user happen to have installed.
> That means our packages will be different.

Fun part, do we know how many people are using the official wine
packages from debian, and how many debian user are using the inofficial
ones provided from winehq?

AFAIK (this happens at least on Ubuntu) most people are using the new
crack packages from winehq...since Scotts not in the Ubuntu MOTU team,
we have at least a sync between winehq and ubuntu in general. And it
seems, this pleases the user much more...:)

> I'm pretty sure they would have seen this RFH anyways since I did Cc 
> wine-devel (which they presumably read) when filing it, but I only 
> expected them to answer if they're fine not doing things the Ubuntu
> way 
> - which pretty much means I don't *really* expect them to answer, I
> guess.

You guessed wrong :) At least it would be good to follow the "one way
to go" policy for both distros :) for the users sake...not the
developers ;)

\sh

Message #30 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Arthur Loiret <arthur.loiret@u-psud.fr>

To: Ove Kaaven <ovek@arcticnet.no>, 479659@bugs.debian.org

Subject: Re: Bug#479659: RFH: wine -- Windows API implementation

Date: Tue, 6 May 2008 10:45:33 +0200

[Message part 1 (text/plain, inline)]

Hi,

I'm interested in helping you maintaining wine, esp. I'd like to try again to
replace the amd64 hack. Thanks for creating an alioth group. :-)


Arthur.

On Tue, May 06, 2008 at 03:09:08AM +0200, Ove Kaaven wrote:
> Package: wnpp
> Severity: normal
> 
> Since my time may be limited in the future, I am seeking comaintainers
> for the Wine package in Debian, at least to ensure that new Wine releases
> may continue to be uploaded in a timely fashion, and to keep the package's
> bug count down. (And given that pretty much half the open bugs are "missing
> manpage" bugs, documentation writers would also help...)
> 
> I have created a project for this on alioth.debian.org. I've loaded the
> current packaging (all versions since etch) into a Git repository there, and
> put up some instructions on http://pkg-wine.alioth.debian.org/
> 
> -- System Information:
> Debian Release: lenny/sid
>   APT prefers testing
>   APT policy: (650, 'testing'), (600, 'unstable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
> Locale: LANG=en_US.ISO-8859-1, LC_CTYPE=en_US.ISO-8859-1 (charmap=ISO-8859-1)
> Shell: /bin/sh linked to /bin/bash

[signature.asc (application/pgp-signature, inline)]

Message #35 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Ove Kaaven <ovek@arcticnet.no>

To: Stephan Hermann <sh@sourcecode.de>

Cc: Reinhard Tartler <siretart@debian.org>, 479659@bugs.debian.org, Scott Ritchie <scottritchie@ubuntu.com>

Subject: Re: Bug#479659: RFH: wine -- Windows API implementation

Date: Tue, 06 May 2008 12:02:39 +0200

Stephan Hermann skrev:
> Fun part, do we know how many people are using the official wine
> packages from debian, and how many debian user are using the inofficial
> ones provided from winehq?

No, but such a figure would only be meaningful if all else was equal, 
which is not the case. Debian has a very long release cycle, so the Wine 
version in etch is ancient (0.9.25). So when etch users get desperate 
for something newer, where do you think most of them will go? On WineHQ, 
they'll only find the Ubuntu-like packages, nothing based on the 
official Debian packaging (and they don't even know it). So for these 
users, it's a Hobson's choice: Ubuntu-like packages or nothing.

I'm sure even a lot of testing users were driven there during the long 
periods when I just wasn't updating the official packages. And ever 
since, I've had bug reports from people using the winehq packages, 
because they didn't know there was a difference, not because they liked 
the winehq ones better. Most users really only care getting the newest 
version, and Debian hasn't had an edge in that department (though 
hopefully a comaintainer would do something about that).

So, "fun" perhaps, but nothing else.

> AFAIK (this happens at least on Ubuntu) most people are using the new
> crack packages from winehq...since Scotts not in the Ubuntu MOTU team,
> we have at least a sync between winehq and ubuntu in general. And it
> seems, this pleases the user much more...:)

New versions are always pleasing.

>> I'm pretty sure they would have seen this RFH anyways since I did Cc 
>> wine-devel (which they presumably read) when filing it, but I only 
>> expected them to answer if they're fine not doing things the Ubuntu
>> way 
>> - which pretty much means I don't *really* expect them to answer, I
>> guess.
> 
> You guessed wrong :) At least it would be good to follow the "one way
> to go" policy for both distros :) for the users sake...not the
> developers ;)

I'm not sure there's a real need for that. Debian and Ubuntu has 
different target audiences, different development models, and different 
policies. Debian is an "universal" OS, designed to be deployed on 
anything from a PDA to a supercomputing cluster. This means a bunch of 
package customization is appropriate, and there are lots of guidelines 
and rules to follow when doing packages, which may easily involve not 
doing things the way upstream does. Ubuntu is really more of an end-user 
desktop distro, where RPM-like solutions and development models are fine 
- and if it works, it gets shipped. (Ubuntu in general doesn't exactly 
shine in the technical excellence department, if I understand my fellow 
Debian Developers correctly.)

So the packaging for Debian and Ubuntu could perfectly reasonably be 
different, if users could get both on WineHQ.

From your other mail:

> IMHO, Scotts package is quite in a good shape, regarding support and
> bugfixes + Win32 support on x86_64 archs...
> We don't need to rely on anything else then some lib32* compiled
> packages on amd64 and the stuff inside ia32-libs...

So? That's trivial. My packages are also available for amd64, and it 
would be easy to compile it natively on them if Debian actually had a 
decent ia32-libs that wasn't broken. This has nothing to do with 
differences in Wine packaging.

In fact, it would be on amd64 that my packaging scheme really shines. 
Let's say the ia32-libs split finally happened, and everything was 
available as individual lib32* packages. What mess would users be in then?

You want to print on Debian? If you got libwine-print, you can print. 
You want to print on Ubuntu? "WTF? I didn't know I needed to install 
lib32cups *and* cupsys-bsd, my other Linux apps can print without"

You want to play sounds using JACK? If you got libwine-jack, you can 
play audio. You want to use JACK on Ubuntu? "WTF? I need to install 
lib32jack, sounds work everywhere else without"

You want to scan with SANE? If you got libwine-sane, you can, and so on, 
and so forth. Nothing would work differently between i386 and amd64, or 
be more difficult on either.

And if you install the "wine" metapackage on Debian, you can of course 
get everything all at once, where everything Wine can offer would Just 
Work, even on the amd64 platform after the ia32-libs split.

I'm not abandoning such user convenience for the RPM-like packaging 
Ubuntu uses. I personally chose Debian as my distro to try to get away 
from such broken models. To Debian, technical excellence matters (which 
is where all the bureaucracy, procedures, and rigid policy documents 
come from).

(That said, if someone got consensus on the debian-devel ML that your 
way *is* better, I'd probably have to give in...)

> Furthermore, Ubuntus wine package does compile without any hassle on
> lpia archs..

And what's that supposed to mean?

> Ove, when you are interested to pick up Scotts Packages (he's the
> winehq debian package maintainer actually) I think we would be glad to
> help in the transition.

Unfortunately probably not gonna happen anytime soon...

Oh, and sorry if I seem to be flaming a little. I just want my POV to be 
clear.

Message #40 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Ove Kaaven <ovek@arcticnet.no>

To: arthur.loiret@u-psud.fr

Cc: 479659@bugs.debian.org

Subject: Re: Bug#479659: RFH: wine -- Windows API implementation

Date: Tue, 06 May 2008 14:50:53 +0200

Arthur Loiret skrev:
> Hi,
> 
> I'm interested in helping you maintaining wine, esp. I'd like to try again to
> replace the amd64 hack. Thanks for creating an alioth group. :-)

The amd64 hack is there because the ia32-libs package is broken, not 
because anything in particular needs to be done to Wine itself.

Anyway, are you a Debian Developer? What Debian packages have you worked 
on before?

Message #45 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Arthur Loiret <arthur.loiret@u-psud.fr>

To: Ove Kaaven <ovek@arcticnet.no>

Cc: 479659@bugs.debian.org

Subject: Re: Bug#479659: RFH: wine -- Windows API implementation

Date: Tue, 6 May 2008 15:11:55 +0200

[Message part 1 (text/plain, inline)]

On Tue, May 06, 2008 at 02:50:53PM +0200, Ove Kaaven wrote:
> Anyway, are you a Debian Developer? What Debian packages have you worked  
> on before?

NM, here's my QA page [0]. I've mainly worked on toolchain (see binutils,
gcc-4.3, gdc-4.1 and gdc-4.2 changelogs), llvm, and a few other things.

[0] http://qa.debian.org/developer.php?login=arthur.loiret@gmail.com

[signature.asc (application/pgp-signature, inline)]

Message #50 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Shachar Shemesh <shachar@debian.org>

To: Ove Kaaven <ovek@arcticnet.no>, 479659@bugs.debian.org

Subject: Re: Bug#479659: RFH: wine -- Windows API implementation

Date: Wed, 11 Jun 2008 12:58:37 +0300

Is this bug still open? Is help still needed?

I don't have a huge amount of time, but Wine releases are just once a 
month, so I doubt that'll be a major problem.

I am a Debian developer 
(http://qa.debian.org/developer.php?login=shachar@debian.org), where I 
co-maintain the packages in Debian Hebrew. I also maintain on my own 
libargtable, rsyncrypto, fakeroot-ng, sshpass and privbind (for all but 
the first I am also upstream). I am a (currently inactive) Wine hacker, 
and I subscribe to Ove's point of view vis what is right packaging wise.

If you still need help, let me know.

Shachar

Message #55 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Ove Kaaven <ovek@arcticnet.no>

To: Shachar Shemesh <shachar@debian.org>

Cc: 479659@bugs.debian.org

Subject: Re: Bug#479659: RFH: wine -- Windows API implementation

Date: Wed, 11 Jun 2008 14:03:09 +0200

Shachar Shemesh skrev:
> Is this bug still open? Is help still needed?

Yes, it's open.

I did get help from Arthur Loiret, but he's involved in a ton of other 
packages, so his time is limited too. Also I think he said he's still in 
the NM queue. Can't hurt to get more help.

> I don't have a huge amount of time, but Wine releases are just once a 
> month, so I doubt that'll be a major problem.

Actually, for the last few years (ever since 0.9), they've been twice a 
month.

Anyway, my memory tells me that you sent patches for bidi support in the 
Wine packages a few years back (and that sometime the last year, I've 
lost that biditest.exe).

So, sure, you're welcome to help. Just request to join the pkg-wine 
project on Alioth, and subscribe to the mailing list...

Message #60 received at 479659@bugs.debian.org (full text, mbox, reply):

From: ivan <ivan1986@list.ru>

To: ovek@arcticnet.no

Subject: Re: Bug#479659: RFH: wine -- Windows API implementation

Date: Tue, 29 Jul 2008 21:36:38 +0400

Hello!
I build wine 1.1.2 in deb, all work fine.
Please tell me, what i must do now to help You?
Hou i may add pack to repository.
I build debs, dsc and diff.gz what me do now?

Sorry for my English...

Message #65 received at 479659@bugs.debian.org (full text, mbox, reply):

From: ivan <ivan1986@list.ru>

To: 479659@bugs.debian.org

Subject: wine 1.1.4

Date: Mon, 8 Sep 2008 23:15:10 +0400

Hello!
I repare build script in wine 1.1.4 and build this version.

Hou i may upload package to sid?

Message #70 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Utku Somer <utku@parkyeri.com>

To: ivan <ivan1986@list.ru>, 479659@bugs.debian.org

Subject: Re: Bug#479659: wine 1.1.4

Date: Tue, 09 Sep 2008 18:18:41 +0300

ivan wrote:
> Hello!
> I repare build script in wine 1.1.4 and build this version.
>
> Hou i may upload package to sid?
>   

I'll recommend checking pkg-wine-party list first, and creating some 
traffic there:

http://lists.alioth.debian.org/mailman/listinfo/pkg-wine-party

utku

Message #75 received at 479659@bugs.debian.org (full text, mbox, reply):

From: ivan <ivan1986@list.ru>

To: 479659@bugs.debian.org

Subject: RFH: wine -- Windows API implementation

Date: Sun, 14 Sep 2008 18:42:19 +0400

Hello, i upload wine 1.1.4 

http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=wine

Update Wine to version 1.1.4
Fix install-man for 1.1.4
Remove build-depends: xlibs-dev (<< 4.3)

Message #80 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Julian Aloofi <jlnaloofi.private@googlemail.com>

To: 479659@bugs.debian.org

Subject: Help with manpages

Date: Sat, 20 Dec 2008 00:04:36 +0100

Hello,
I would like to help writing the missing manpages. I don't know git yet, so I 
will read the Git User's Manual tomorrow. This is one of my first active 
contributions to the Debian Project, except from some package description I 
translated, so please tell me if I make any terrible mistakes ;)

Julian Aloofi

Message #85 received at 479659@bugs.debian.org (full text, mbox, reply):

From: ivan <ivan1986@list.ru>

To: 479659@bugs.debian.org

Subject: wine 1.1.21

Date: Sat, 9 May 2009 21:08:33 +0400

[Message part 1 (text/plain, inline)]

Hello!
Are you going to update the package? 
I have an updated package to version 1.1.21, it also removed some old 
dependencies. Everything is work fine. 
How can I update the package in the repository can be, I send you the files or 
something else?

Sorry for my English - it is google translate.

[signature.asc (application/pgp-signature, inline)]

Message #90 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Hae-woo Park <starlet@iris.snu.ac.kr>

To: 479659@bugs.debian.org

Subject: Dead wine packages

Date: Wed, 29 Jun 2011 01:56:30 +0900

[Message part 1 (text/plain, inline)]

Hello .. Ha-ah ..

To users, Wine packages are no better than orphaned ones.
We have ancient 1.0.x packages (yes, there are 1.1.x in experimental),
while the official Wine goes into 1.3.x.
For years, we can only see the packing methods in this worn-out thread.

It would be better to orphan these packages,
so that someone can try making another wine packages.
(At least, someone can migrate WineHQ's or Ubuntu's ones.)

Yes, the Debian users may be different from theirs.
However, I don't think there is any Debian user who want to use ancient
version of software.


Regards,
Hae-woo Park

[Message part 2 (text/html, inline)]

Message #95 received at 479659@bugs.debian.org (full text, mbox, reply):

From: nr@cs.tufts.edu (Norman Ramsey)

To: 479659@bugs.debian.org

Subject: any hope for progress?

Date: Sun, 18 Dec 2011 23:53:47 -0500 (EST)

It's a real shame that disagreements about packaging have left us with
wine packages that are wildly out of date.  Perhaps it is better to have
badly packaged software that is up to date than to have well-packaged
software that is never updated?

Message #100 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Boris Pek <tehnick-8@mail.ru>

To: 479659@bugs.debian.org

Subject: Re: Bug#479659: RFH: wine -- Windows API implementation

Date: Thu, 22 Dec 2011 19:00:13 +0400

Hi,

Any solution in this thread?

I am successfully using the wine package from PPA in Launchpad in my Debian Sid
systems. But this is not good advise for most users.

Best regards,
Boris

Message #105 received at 479659@bugs.debian.org (full text, mbox, reply):

From: James Huber <jhuber72@gmail.com>

To: 479659@bugs.debian.org

Subject: Update package before Wheezy freeze?

Date: Thu, 29 Mar 2012 11:18:20 -0700

[Message part 1 (text/plain, inline)]

Hey guys, we should at least try to get wine 1.4 into testing before
Wheezy freezes this summer.  Wine 1.4 works great when compiled from
source, and it would be very sad if Wheezy got stuck with a version of
wine that at the time will be over 4 years old.

I think it is time to look at other packaging methods for wine, because
absolutely nothing is getting done at the moment.

[Message part 2 (text/html, inline)]

Message #110 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Michael Gilbert <mgilbert@debian.org>

To: 479659@bugs.debian.org

Subject: re: wine request for help

Date: Wed, 9 May 2012 20:13:48 -0400

Hi,

I hereby declare my intention to (continue to) help with the wine
package and declare my request for uploader status to be authorized.

In the past, I helped NMU maintain wine 1.0 for the squeeze release,
and I'm currently NMU maintaining the more recent wine releases in
preparation for the wheezy release.

Best wishes,
Mike

Message #115 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Bruno Melo <brunosonic@gmail.com>

To: 479659@bugs.debian.org

Date: Thu, 10 May 2012 21:14:27 -0300

[Message part 1 (text/plain, inline)]

hi,
i'd like to help, but i'm a noob and i don't know to pack yet.
i have wine 1.4 compiled here with crysis fix patch.
bye

[Message part 2 (text/html, inline)]

Message #120 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Boris Pek <Tehnick-8@yandex.ru>

To: Ove Kaaven <ovek@arcticnet.no>,479659@bugs.debian.org

Subject: Re: RFH: wine -- Windows API implementation

Date: Thu, 21 Jun 2012 10:54:24 +0300

Hi,

I see new versions of wine in Debian Sid:
http://packages.qa.debian.org/w/wine.html

Is it time to close this RFH?

Best regards,
Boris

Message #125 received at 479659@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Boris Pek <Tehnick-8@yandex.ru>

Cc: wine@packages.debian.org, 479659@bugs.debian.org

Subject: Re: RFH: wine -- Windows API implementation

Date: Sat, 7 Jul 2012 19:51:38 -0500

Hi,

Boris Pek wrote:

> I see new versions of wine in Debian Sid:
> http://packages.qa.debian.org/w/wine.html
>
> Is it time to close this RFH?

I think a new "state of the package" message would be nice, yes. :)

Jonathan
who would love to see a mingw partial architectures and wine64
packaged, but those are stories for another day

Message #130 received at 479659-close@bugs.debian.org (full text, mbox, reply):

From: Michael Gilbert <mgilbert@debian.org>

To: 479659-close@bugs.debian.org

Subject: re: wine request for help

Date: Sun, 5 May 2013 18:32:31 -0400

Hi,

I'm closing this RFH.  We have a few wine helpers now; enough to keep
things in decent shape.  We're always open to new helpers though.

Best wishes,
Mike

Send a report that this bug log contains spam.