On Mon, 12 May 2014 13:02:12 +0200 Bill Allombert wrote: > Package: libruby2.1 > Version: 2.1.2-1 > Severity: important > > Hello Antonio, > > There is a circular dependency between libruby2.1, ruby and ruby2.1: > > libruby2.1 :Depends: ruby2.1 (= 2.1.2-1) > ruby :Depends: ruby2.1 > ruby2.1 :Depends: ruby (>= 1:1.9.3.1), libruby2.1 (>= 2.1.0) > > Complex circular dependencies are known to cause problems during upgrade, so > we > should try to get rid of them.
What is worse, it seems to me that these dependencies are not even strict enough to prevent troublesome situations. For instance, a partially upgraded system may have ruby-debian/0.3.8+b4 and ruby/1:2.0.0.2 simultaneously installed (and configured), since ruby-debian/0.3.8+b4 :Depends: libruby2.1 (>= 2.1.0), ruby | ruby-interpreter libruby2.1/2.1.2-2 :Depends: ruby2.1 (= 2.1.2-2) ruby2.1/2.1.2-2 :Depends: ruby (>= 1:1.9.3.1), libruby2.1 (>= 2.1.0) But ruby-debian/0.3.8+b4 does not support Ruby 2.0 and hence, a Ruby program using ruby-debian (such as apt-listbugs or how-can-i-help) will fail when interpreted by ruby/1:2.0.0.2 ... I hope there's a better strategy to prevent such situations without causing problems during upgrades... -- http://www.inventati.org/frx/ fsck is a four letter word... ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpfPliQBd6OY.pgp
Description: PGP signature
