Hi, as you see, vsftpd is to be upgraded to 2.0.3-r1 which is not "<2.0.3-r1". Portage wrongly considers vsftpd to be blocking ftpbase. Installing ftpbase manually doesn't work. tux peter # emerge -atv vsftpd These are the packages that I would merge, in reverse order: Calculating dependencies ...done! [blocks B ] <net-ftp/vsftpd-2.0.3-r1 (is blocking net-ftp/ftpbase-0.00) [ebuild U ] net-ftp/vsftpd-2.0.3-r1 [2.0.3] +pam +ssl +tcpd -xinetd 149 kB [ebuild N ] net-ftp/ftpbase-0.00 +pam 0 kB Total size of downloads: 149 kB !!! Error: The above package list contains packages which cannot be installed !!! on the same system. tux peter # tux peter # emerge info Portage 2.0.51.22-r1 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r0, 2.6.11-gentoo-r8 i686) ================================================================= System uname: 2.6.11-gentoo-r8 i686 AMD Athlon(tm) XP 1800+ Gentoo Base System version 1.6.12 ccache version 2.4 [enabled] dev-lang/python: 2.3.5, 2.4.1-r1 sys-apps/sandbox: 1.2.9 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.18 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -march=athlon-xp -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks fixpackages sfperms strict" GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://pandemonium.tiscali.de/pub/gentoo/" LINGUAS="de" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow alsa apache2 apm arts avi bitmap-fonts cdparanoia cdr crypt cups dba directfb dvd emboss fam foomaticdb ftp gd gdbm gif imagemagick imap imlib jabber jpeg kde kdeenablefinal libg++ libwww mad maildir mikmod mmx mp3 mpeg mysqli nls nomotif nptl nptlonly nvidia ogg oggvorbis opengl pam pdflib php pic png posix qt readline scanner sdl sqlite sse ssl svga tcpd tetex tiff truetype truetype-fonts type1-fonts unicode userlocales vorbis xml2 xv zlib video_cards_nvidia linguas_de userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS tux peter #
Unmerge the old vsftpd version and emerge the new one. Portage is working OK. net-ftp/ftpbase-0.00 <snip> DEPEND="pam? ( || ( virtual/pam sys-libs/pam ) ) !<net-ftp/proftpd-1.2.10-r6 !<net-ftp/pure-ftpd-1.0.20-r2 !<net-ftp/vsftpd-2.0.3-r1" </snip>
I think it is not working ok because the upgrade function aborts with the error I mentioned, but unmerging the old version an reemerging the new basically _is_ an upgrade. So why doesn't Portage ignore those dependency pseudo errors which are automatically solved after an upgrade? Why do I have to intervene? I first thougt this was a typo in ftpbase-0.00.ebuild which is why I assigned this to component Server, but I really think Portage could handle this in a better way.
...
See Bug 79606. Portage won't handle this for you, sorry. *** This bug has been marked as a duplicate of 79606 ***
*** Bug 97534 has been marked as a duplicate of this bug. ***
*** Bug 100783 has been marked as a duplicate of this bug. ***
*** Bug 102182 has been marked as a duplicate of this bug. ***
*** Bug 104724 has been marked as a duplicate of this bug. ***
*** Bug 157345 has been marked as a duplicate of this bug. ***