[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[pkg-wine-party] Bug#758312: closed by Michael Gilbert <mgilbert@debian.org> (Re: Bug#758312: wine-development: please provide an upgrade path)



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 instead of reinstalling it from scratch every time or having to do dirty hacking? Many libraries have many upgrade cycles before the freeze and other maintainers handle a proper migration wether or not this will be the final version for the release or not. This ensure rdeps and maintainer's test systems can be upgraded without pain. Even you have rdeps such as playonlinux. You cannot expect people to follow you very specific ML and handle things manually each time you "feel like" to rename a package.

I know there is nothing clearly stated in the policy about this, but this is how all key packages are handled and this has proved good for us all, so i really urge you to rethink about it (for the future).

Regards.

--
Marc Dequènes (Duck)

Attachment: pgptM1tNDoIp_.pgp
Description: PGP Digital Signature


Reply to: