Package: ruby Version: 1:1.9.3.4 Severity: important Hi,
I understand and appreciate there's an effort to make ruby1.8 go away, and this is fine. However, the current situation is forcing users to remove the ruby1.8 package that they have installed and working on their machines. It's very nice to remove all ruby1.8 dependencies from the archive. However, you can't know what ruby1.8 dependencies the users have in their machines. By forcing the removal of ruby1.8, you are forcing the migration work that users need to do. The current state is that ruby1.8 cannot be installed alongside ruby1.9.1, although this has been the case for ages. I don't ask you to support ruby1.8, it's perfectly fine to stop supporting it and remove it from the archive. However, conflicts shouldn't be used to retire packages from users' systems. So, please either remove the conflicts from the ruby package or the dependency on ruby for the ruby1.9.1 package. Thanks. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ruby depends on: ii ruby1.9.1 1.9.3.484-2 ruby recommends no packages. Versions of packages ruby suggests: pn ri <none> pn ruby-dev <none> -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
