Re: Possibility of getting an up-to-date version of Wine into Squeeze

2010-09-06 Thread Stephen Kitt
On Sun, Sep 05, 2010 at 03:06:35PM +0200, Andreas Barth wrote:
 * Andreas Barth (a...@not.so.argh.org) [100829 15:55]:
  * Andreas Barth (a...@not.so.argh.org) [100822 23:18]:
   * Stephen Kitt (li...@sk2.org) [100820 00:02]:
The version of Wine Squeeze is going to ship with (1.0.1) is nearly two 
years
old and for many users its use is greatly limited. The recently released
stable version, 1.2, has vastly improved support for a large number of
applications and games. I have prepared packages in the same style as 
the
current maintainer's, and a few people have tested them. I haven't had 
much
reaction from Ove but I do know he is aware of their existence; I 
haven't
consulted him regarding this particular request.
   
   Can we please see this version of wine in experimental first
  
  Any news on uploading wine to experimental?
 
 ping?

Sorry for the delay, I was waiting to see if Ove answered. I've had
packages ready on http://www.sk2.org/wine/ for a while, but they're
probably not ready for experimental (apart from the wine package, but
that needs wine-gecko).

As it stands, the packages build an updated gcc-mingw32 based on gcc
4.5.0, and a replacement runtime for mingw32-runtime based on
mingw-w64. This is where things get a bit complicated; Robert Millan's
packages based on mingw-w64 have been orphaned, but they pretended to
provide a build environment for mingw32msvc which doesn't match (or no
longer matches, I'm not sure) the upstream usage which is w64-mingw32
(with x86_64 and i686 variants, which would become amd64 and i586 or
i686 on Debian I guess). I could keep the existing targets and prepare
packages for experimental, but given that gcc 4.5 won't be in squeeze
(as I understand it), I thought it would be better to prepare a
complete set of w64-mingw32 packages, with proper build dependencies
on binutils-source and gcc-4.5-source. This would also help clearly
differenciate the mingw32 and mingw-w64 packages.

Thus the plan would be:
1. adopt mingw-w64 (I'll update #594371)
2. prepare binutils-mingw-w64 and gcc-4.5-mingw-w64 packages
3. update the mingw-w64 runtime (version 1.0 has been released)
4. update the wine-gecko 1.0.0 package
5. package wine-gecko 1.1.0 (this is required for wine-unstable 1.3.2)
6. update wine and wine-unstable

I do know that Ove has a wine-gecko (1.0.0) package which builds using
the existing mingw32-runtime, but it still needs an updated
gcc-mingw32. I don't know if wine-gecko 1.1.0 builds with
mingw32-runtime, but the official build instructions use mingw-w64. I
also know that Ove has worked on moving the wine packaging in a new
direction, so I wouldn't want to package wine against his wishes (but
my wine package hardly changes his existing packaging at all).

All in all it seems rather unrealistic to try hard now to get wine 1.2
into squeeze...

Regards,

Stephen


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100906212356.gc17...@sk2.org



Re: Possibility of getting an up-to-date version of Wine into Squeeze

2010-09-06 Thread Andreas Barth
* Stephen Kitt (li...@sk2.org) [100906 23:24]:
 Thus the plan would be:
 1. adopt mingw-w64 (I'll update #594371)
 2. prepare binutils-mingw-w64 and gcc-4.5-mingw-w64 packages
 3. update the mingw-w64 runtime (version 1.0 has been released)
 4. update the wine-gecko 1.0.0 package
 5. package wine-gecko 1.1.0 (this is required for wine-unstable 1.3.2)
 6. update wine and wine-unstable

 [...]

 All in all it seems rather unrealistic to try hard now to get wine 1.2
 into squeeze...

Agreed. However, it still would make sense to fix the issues in
experimental - we need that anyways. Of course, only with an
appropriate priority.

Thanks for your effort.


Andi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100906213050.gp2...@mails.so.argh.org



Re: Possibility of getting an up-to-date version of Wine into Squeeze

2010-09-05 Thread Andreas Barth
* Andreas Barth (a...@not.so.argh.org) [100829 15:55]:
 * Andreas Barth (a...@not.so.argh.org) [100822 23:18]:
  * Stephen Kitt (li...@sk2.org) [100820 00:02]:
   The version of Wine Squeeze is going to ship with (1.0.1) is nearly two 
   years
   old and for many users its use is greatly limited. The recently released
   stable version, 1.2, has vastly improved support for a large number of
   applications and games. I have prepared packages in the same style as the
   current maintainer's, and a few people have tested them. I haven't had 
   much
   reaction from Ove but I do know he is aware of their existence; I haven't
   consulted him regarding this particular request.
  
  Can we please see this version of wine in experimental first
 
 Any news on uploading wine to experimental?

ping?


Andi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100905130635.gm15...@mails.so.argh.org



Re: Possibility of getting an up-to-date version of Wine into Squeeze

2010-08-29 Thread Andreas Barth
* Andreas Barth (a...@not.so.argh.org) [100822 23:18]:
 * Stephen Kitt (li...@sk2.org) [100820 00:02]:
  The version of Wine Squeeze is going to ship with (1.0.1) is nearly two 
  years
  old and for many users its use is greatly limited. The recently released
  stable version, 1.2, has vastly improved support for a large number of
  applications and games. I have prepared packages in the same style as the
  current maintainer's, and a few people have tested them. I haven't had much
  reaction from Ove but I do know he is aware of their existence; I haven't
  consulted him regarding this particular request.
 
 Can we please see this version of wine in experimental first

Any news on uploading wine to experimental?


Andi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100829135451.gj15...@mails.so.argh.org



Re: Possibility of getting an up-to-date version of Wine into Squeeze

2010-08-22 Thread Andreas Barth
* Stephen Kitt (li...@sk2.org) [100820 00:02]:
 The version of Wine Squeeze is going to ship with (1.0.1) is nearly two years
 old and for many users its use is greatly limited. The recently released
 stable version, 1.2, has vastly improved support for a large number of
 applications and games. I have prepared packages in the same style as the
 current maintainer's, and a few people have tested them. I haven't had much
 reaction from Ove but I do know he is aware of their existence; I haven't
 consulted him regarding this particular request.

Can we please see this version of wine in experimental first (instead
the current 1.1.24-1), e.g. also with a version number as 1.2~exp0.1
or so? That would also allow us to judge the open issues (I have some
symphathy for this request, but obviously it's quite late or even too
late for squeeze.)



Andi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100822211744.gg15...@mails.so.argh.org



Re: Possibility of getting an up-to-date version of Wine into Squeeze

2010-08-22 Thread Andreas Barth
* Ove Kaaven (o...@arcticnet.no) [100821 04:03]:
 1. Get wine-gecko built on Debian. Apparently gcc-mingw32 4.4.4 did not  
 solve all the problems with it, gcc-mingw32 would apparently have to be  
 upgraded all the way to 4.5.0 to build a fully working package. Not sure  
 if the release team will accept that, and even if they did, packaging  
 Wine 1.2 for squeeze will, by now, be a rush job that may result in a  
 package with serious problems.

Same here - can we please first see gcc-mingw32 in experimental before
discussing about unstable?

 2. Allow wine to download upstream's wine-gecko binaries over the  
 Internet, as it does by default.

Not an option. Even not for experimental.

 3. Disable the wine-gecko download. This results in a crippled Wine, and  
 both upstream and users will hate us.

Still better than 2.

 4. Leave things as they are. If users want Wine 1.2, let them use  
 backports.org or similar, or even download upstream's own Debian  
 packages if they prefer.

Even in that case, we need to fix the issues (perhaps not in the same
hurry, but we need to).



Andi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100822211936.gh15...@mails.so.argh.org



Re: Possibility of getting an up-to-date version of Wine into Squeeze

2010-08-21 Thread Stephen Kitt
On Sat, Aug 21, 2010 at 04:02:37AM +0200, Ove Kaaven wrote:
 Den 21. aug. 2010 03:01, skrev Svante Signell:
 Please take this request seriously. Even if Squeeze is frozen,
 distributing the same version (1.0.x) of Wine as Lenny does not look
 good! People are trying to help out!
 
 I wouldn't hold much hope. These are the options:
 
 1. Get wine-gecko built on Debian. Apparently gcc-mingw32 4.4.4 did
 not solve all the problems with it, gcc-mingw32 would apparently
 have to be upgraded all the way to 4.5.0 to build a fully working
 package. Not sure if the release team will accept that, and even if
 they did, packaging Wine 1.2 for squeeze will, by now, be a rush job
 that may result in a package with serious problems.

Have you had a chance to take a look at my packages?  I took the time
to separate each patch out so that you'd be able to integrate them
into your git tree without to much trouble.

Note that building wine-gecko also requires an updated version of
mingw-w64 (used to produce an updated replacement for
mingw32-runtime).

You've convinced me as far as requiring wine-gecko is concerned,
which, given the new build environment involved, means pushing for
release in squeeze is unrealistic.

The one thing I do hope now is that you'll accept the various offers
of help you've received so that squeeze+1 can have a current version
of Wine when it comes out!

Regards,

Stephen


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100821085511.ga18...@sk2.org



Re: Possibility of getting an up-to-date version of Wine into Squeeze

2010-08-21 Thread Ove Kaaven

Den 21. aug. 2010 10:55, skrev Stephen Kitt:

On Sat, Aug 21, 2010 at 04:02:37AM +0200, Ove Kaaven wrote:

Den 21. aug. 2010 03:01, skrev Svante Signell:

Please take this request seriously. Even if Squeeze is frozen,
distributing the same version (1.0.x) of Wine as Lenny does not look
good! People are trying to help out!


I wouldn't hold much hope. These are the options:

1. Get wine-gecko built on Debian. Apparently gcc-mingw32 4.4.4 did
not solve all the problems with it, gcc-mingw32 would apparently
have to be upgraded all the way to 4.5.0 to build a fully working
package. Not sure if the release team will accept that, and even if
they did, packaging Wine 1.2 for squeeze will, by now, be a rush job
that may result in a package with serious problems.


Have you had a chance to take a look at my packages?  I took the time
to separate each patch out so that you'd be able to integrate them
into your git tree without to much trouble.


I'll take a look when the time comes. Until gcc-mingw32 is updated, 
there's not much that can be done anyway.


Note that I already did some preliminary work a while ago (including a 
complete wine-gecko package, just waiting for a working compiler), and 
have had some long-term plans for the Wine package itself, and probably 
not in the direction you might expect or have worked on. So I might not 
have use for such patches, but we'll see when it finally becomes 
possible to update Wine.


For now, I suggest working on a working gcc-mingw32, if anything.


Note that building wine-gecko also requires an updated version of
mingw-w64 (used to produce an updated replacement for
mingw32-runtime).


My own wine-gecko package does not need this. (Though if mingw32-runtime 
were to be updated, its build system could be simplified a bit, I guess.)



--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c6f9c83.6070...@arcticnet.no



Re: Possibility of getting an up-to-date version of Wine into Squeeze

2010-08-20 Thread Svante Signell
Please take this request seriously. Even if Squeeze is frozen,
distributing the same version (1.0.x) of Wine as Lenny does not look
good! People are trying to help out! 


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1282352478.3623.41.ca...@hp.my.own.domain



Re: Possibility of getting an up-to-date version of Wine into Squeeze

2010-08-20 Thread Ove Kaaven

Den 21. aug. 2010 03:01, skrev Svante Signell:

Please take this request seriously. Even if Squeeze is frozen,
distributing the same version (1.0.x) of Wine as Lenny does not look
good! People are trying to help out!


I wouldn't hold much hope. These are the options:

1. Get wine-gecko built on Debian. Apparently gcc-mingw32 4.4.4 did not 
solve all the problems with it, gcc-mingw32 would apparently have to be 
upgraded all the way to 4.5.0 to build a fully working package. Not sure 
if the release team will accept that, and even if they did, packaging 
Wine 1.2 for squeeze will, by now, be a rush job that may result in a 
package with serious problems.


2. Allow wine to download upstream's wine-gecko binaries over the 
Internet, as it does by default. Wine 1.2 will do this even if you're 
not using any software which actually needs HTML rendering. It downloads 
wine-gecko binaries from a particular URL on SourceForge. There is no 
verification of the binaries; no signatures, no MD5 hashes. And Wine 
doesn't do sandboxing. IOW, there is no security.


3. Disable the wine-gecko download. This results in a crippled Wine, and 
both upstream and users will hate us.


4. Leave things as they are. If users want Wine 1.2, let them use 
backports.org or similar, or even download upstream's own Debian 
packages if they prefer.


I'm certainly willing to settle for 4...


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c6f33bd.3020...@arcticnet.no



Possibility of getting an up-to-date version of Wine into Squeeze

2010-08-19 Thread Stephen Kitt
Dear release team,

I know what the answer ought to be at this stage, but I thought I'd ask
anyway; is there any chance whatsoever that, should updated packages of Wine
be ready soon (and satisfy the usual quality requirements), they could be
accepted into Squeeze?

The version of Wine Squeeze is going to ship with (1.0.1) is nearly two years
old and for many users its use is greatly limited. The recently released
stable version, 1.2, has vastly improved support for a large number of
applications and games. I have prepared packages in the same style as the
current maintainer's, and a few people have tested them. I haven't had much
reaction from Ove but I do know he is aware of their existence; I haven't
consulted him regarding this particular request.

The changelog for my packages is as follows:

wine (1.2-0.1) unstable; urgency=low
  
  [ Stephen Kitt ]

  * Non-maintainer upload.
  * New upstream version. Closes: #585409, #589773.
- winebrowser correctly passes URLs via DDE. Closes: #491186.
  * Include ptrace speedup to avoid lag in Steamworks-based games.
  * Now that stable has debhelper 7, use it:
- use dh_lintian;
- add ${misc:Depends};
- drop dh_desktop.
  * Install new utilities into libwine-bin:
- attrib.exe;
- mshta.exe;
- ngen.exe;
- ping.exe;
- sc.exe.
  * Install new French and German translations of winemaker.1 into
libwine-dev.
  * Install new NLS file into libwine.
  * Remove obsolete build dependencies (dependencies no longer present in
stable). Closes: #578975.
  * Switch to 3.0 (quilt) source format and split existing patches.
  * Build on kfreebsd (thanks Tuco!). Closes: #591837.
  
  [ Ove Kaaven ]
  
  * Install function_grep.pl into libwine-dev, in /usr/share/wine, and
modify winedump accordingly. Closes: #555645.
  * Replace @SUFFIX@ with current suffix in preprocessed maintainer
scripts.
  * Add proper package suffixes to the installed reportbug control files.
  * Use wine-safe start /unix as the MIME handler for the
application/x-msdos-program type.

 -- Stephen Kitt st...@sk2.org  Thu, 05 Aug 2010 00:00:14 +0200


I realise this request utterly flies in the face of the minimal changes
requirement, I'm not even the maintainer of the package, and Wine doesn't
have any RC-bug filed against it; hence my initial comment. I'm at least
hoping I won't waste too much of anyone's time...

Regards,

Stephen


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2010082215.2ebcb...@sk2.org