Circular ebuild dependencies. After running emerge -dDUp world, the only reference to autoconf-2.57a-r1 is in the following output. I don't know what the * next to things mean, but I would assume that these dependencies should choose autoconf-2.59-r3 and not autoconf-2.57a-r1. Parent: ebuild / dev-util/subversion-1.0.0-r1 nomerge Depstring: python? ( >=dev-lang/python-2.0 ) apache2? ( >=net-www/apache-2.0.48 ) !apache2? ( !>=net-www/apache-2* ) !dev-libs/apr python? ( || ( =dev-lang/swig-1.3.19 >=dev-lang/swig-1.3.21 ) ) perl? ( >=dev-lang/perl-5.8 ) >=net-misc/neon-0.24.4 berkdb? ( =sys-libs/db-4* ) emacs? ( virtual/emacs ) || ( =sys-devel/autoconf-2.57* >=sys-devel/autoconf-2.59 ) !bootstrap? ( sys-devel/libtool ) python? ( >=dev-lang/python-2.0 ) apache2? ( >=net-www/apache-2.0.48 ) !apache2? ( !>=net-www/apache-2* ) !dev-libs/apr python? ( || ( =dev-lang/swig-1.3.19 >=dev-lang/swig-1.3.21 ) ) perl? ( >=dev-lang/perl-5.8 ) >=net-misc/neon-0.24.4 berkdb? ( =sys-libs/db-4* ) emacs? ( virtual/emacs ) Candidates: ['=sys-devel/autoconf-2.57*', '>=net-www/apache-2.0.48', 'sys-devel/libtool', '>=dev-lang/python-2.0', '>=dev-lang/perl-5.8', '=dev-lang/swig-1.3.19', '=sys-libs/db-4*', '>=net-misc/neon-0.24.4'] ebuild: sys-devel/autoconf-2.57a-r1 binpkg: None Parent: ebuild / sys-devel/autoconf-2.57a-r1 merge Reproducible: Always Steps to Reproduce: 1. emerge -dDUp subversion 2. 3. Expected Results: subversion should not rely on autoconf-2.57a-r1
Also causes circular dependency in [ebuild UD] dev-lang/swig-1.3.19 [1.3.21] [ebuild UD] sys-devel/autoconf-2.57a-r1 [2.59-r3]
autoconf should only be a compile-time dependency. It shouldn't be an issue. Maybe you'd remove autoconf from your world file. Probably removing swig will he similar. This seems more like a portage bug
I have autoconf in my world file. The problem is that emerge does not seem to understand lines like this in the ebuild file: ( || ( =dev-lang/swig-1.3.19 >=dev-lang/swig-1.3.21 ) ) || ( =sys-devel/autoconf-2.57* >=sys-devel/autoconf-2.59 ) If I change this to: - >=dev-lang/swig-1.3.21 >=sys-devel/autoconf-2.59 Everything works correctly. If one has swig-1.3.19 installed, it tries to install 1.3.21 instead, and visa versa.
It will only do so when these packages are in the world file. As both packages are normally only usefull as dependencies they would not need to be in the world file. I will try to reverse the order of the dependencies to depend on the newest version first. That should make things go smoother until the dependency engine of portage gets a big overhaul.
Fixed in more recent portage releases
