When emerging subversion (either upgrading or reemerging the same version, doesn't matter), this error is printed: * : Now you have dev-util/subversion-1.0.6 * Subversion has changed the repository filesystem schema from 0.34.0. * So you MUST dump your repositories before upgrading. * * After doing so call emerge with SVN_DUMPED=1 emerge !! It seems that portage knows what version I have installed (1.0.6), and since my previous version is not <= 0.34.0, I don't need to dump the repository. Having to set this variable every time I upgrade subversion is kind of a pain (I never remember to do it the first time) Reproducible: Always Steps to Reproduce: upgrade/reemerge subversion with any version > 0.34.0 Actual Results: ebuild requires SVN_DUMPED=1, even though no dumping is required Expected Results: The ebuild should detect versions and only require this variable if a dump/restore is actually required. Portage 2.0.50-r9 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.4.20040619-r0,2.2.5-r7, 2.6.4-rc2) ================================================================= System uname: 2.6.4-rc2 i686 Intel(R) Pentium(R) 4 CPU 1700MHz Gentoo Base System version 1.5.1 distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r4,sys-devel/autoconf-2.53a Automake: sys-devel/automake-1.6.1-r6,sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer -fexpensive-optimizations -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3.3/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache" GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://mirrors.acm.cs.rpi.edu/gentoo/ http://open-systems.ufl.edu/mirrors/gentoo http://gentoo.binarycompass.org" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/overlays/gnome-current /usr/local/overlays/bmg-main" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib alsa apache2 apm arts avi berkdb bonobo cdr crypt cups curl directfb doc dvd encode esd foomaticdb gdbm gif gnome gphoto2 gpm gtk gtk2 gtkhtml guile imlib ipv6 java jpeg ldap libg++ libwww lirc mad matroska mikmod motif mozilla moznocompose moznoirc moznomail mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python quicktime readline sdl slang spell sse ssl svga tcltk tcpd tetex theora tiff truetype x86 xml2 xmms xv zlib"
Could you output the result of "emerge -pP subversion"? Ten to one you have an old stale version laying about (the code actually uses some different code to check than to show the version). It will give this behaviour if you have an old version (Any of the installed versions would do). The version it shows however is the best currently available (the message is not that smart about SLOT's ;-))
it turns out this was the problem - it's kind of odd that there were old versions lying around on every machine around, but I guess one of those really old ebuilds didn't clean up after itself properly. Thanks.
