Upon more thinking on this issue, it occurred to me that the reason why you might have added the artificial conflict is the removal of the alternatives system.
Personally, I don't see any gain and many losses by removing the alternatives system. However, I accept that this is your call to make. One possibility would be to upload a ruby1.8 package that doesn't have the alternatives system in it, and have a versioned Conflicts that allows that package to stay. The problem with this solution is that the intended result is that jessie shouldn't have ruby1.8, and so users upgrading from wheezy will never get such a package. So I don't see this as a real solution. As I said in my previous email, it's fine to drop support for ruby1.8 and remove all deps and packages from the archive. What is not fine is breaking current scripts that users might have on their machines, that still depend on ruby1.8, without a valid technical reason. This has always been the way Debian operates: we don't remove packages from users' machines that still work just because we dropped support for them. I don't think that the decision to drop the alternatives system is a good enough reason to break side-by-side for ruby1.8 and ruby1.9.1, which has been working fine for years. Please do reconsider. -- Regards, Marga -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
