qpkg -I -v swig dev-lang/swig-1.3.20 * qpkg -I -v subversion dev-util/subversion-0.37.0 * emerge -upDv world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild U ] dev-lang/swig-1.3.21 [1.3.20] -guile +java -perl +python -ruby -tcltk 1,975 kB [ebuild UD] dev-lang/swig-1.3.19 [1.3.20] -guile +java -perl +python -ruby -tcltk 0 kB [ebuild U ] dev-util/subversion-1.0.0 [0.37.0] +apache2 +berkdb -emacs +python +ssl 5,939 kB I've deleted the 1.0.0 subversion ebuild, but the upgrade/downgrade game still continues... I see this in the subversion ebuild: python? ( || ( =dev-lang/swig-1.3.19 >=dev-lang/swig-1.3.21 ) ) Maybe this has something to do with the problem...
Strange, try manually upgrading to swig 1.3.21. The ebuild for 1.3.20 is broken, and the depend should say that either 1.3.19 or anything bigger than 1.3.21 is ok.
I did that and it seems to work. After updating subversion too, emerge doesn't want to downgrade swig... thanks.
I have a similar problem: Installed is swig-1.3.21 and Subversion-1.0.0 running "emerge -uUDp world" tells me that it will downgrade swig and subversion (to 1.3.19 and 0.37.0 respectively). If you let portage downgrade it and then run "emerge -uUDp world" again it says it will now (re-) upgrade swig and subversion (back to 1.3.21 and 1.0.0). It will keep doing this downgrade/upgrade cycle forever.
Martin, it seems that you have both rapidsvn and subversion in world. I believe that the rapidsvn version in portage does not yet support subversion-1.0.0 so it wants to downgrade to 0.37.0 which will downgrade swig too. Remove either subversion or rapidsvn from your world file and this will be solved.
Durrr, that was the issue yes.
