Coin,
wine-unstable was never in a stable release (or testing even), so
there is no need for the inconvenience of transitional packages.
I already told you i was aware of that, but did you read my BR?
Aren't you happy to be able to upgrade your unstable test system /
pbuilder / sbuild
Hi,
Make a difference between the stable and unstable version of wine can be a
good idea BUT only in the package's name and not in the application's name.
For me actually, it's very complicated and it will be more difficult to
resolv bug ...
Why you don't create the wine's package like from
Hi,
On 08/16/2014 07:57 PM, Marc Dequènes (Duck) wrote:
I have no idea why you renamed wine-unstable into wine-development,
This was announced and discussed here:
http://lists.alioth.debian.org/pipermail/pkg-wine-party/2014-April/003804.html
Greets
jre
--
To UNSUBSCRIBE, email to
Hi
On 08/17/2014 02:38 PM, LOMBARD Maxime wrote:
Make a difference between the stable and unstable version of wine can be
a good idea BUT only in the package's name and not in the application's
name.
For me actually, it's very complicated and it will be more difficult to
resolv bug ...
Actually, the both wine's package in debian repository don't work correctly
when you install the 32-bits and 64-bits package. The installation is fine
but when you launch wine64, a 64-bits prefix is create but it's impossible
to launch and install a 32-bits applications (like explained here
*Sorry, i sent accidentaly the previous message *
Actually, the both wine's package in debian repository don't work correctly
when you install the 32-bits and 64-bits package. The installation is fine
but when you launch wine64, a 64-bits prefix is create but it's impossible
to launch and
Source: wine-development
Severity: normal
Coin,
I have no idea why you renamed wine-unstable into wine-development,
but since the former existed during a significant time in unstable you
need to provide an upgrade path. How are your fellow developpers and
testers supposed to know about
7 matches
Mail list logo
