When I have mailwrapper v0.1 installed, portage wants to upgrade to version 0.2. After installation of version 0.2, portage wants to downgrade to version 0.1. And on it goes... Reproducible: Always Steps to Reproduce: 1. emerge -puD 2. emerge -uD 3. emerge -puD 4. emerge -uD 5. emerge -puD Actual Results: Whenever I have mailwrapper installed as version 0.1, the emerge -uD will upgrade to version 0.2. Next emerge -puD shows that mailwrapper should be downgraded to version 0.1. emerge -uD does the downgrading to 0.1 and emerge -puD shows that portage wants to upgrade to version 0.2 again, all in an endless loop. And I have done emerge sync inbetween, several times. This happens to me on four different computers. Expected Results: portage should decide to use either version 0.1 or 0.2, not juggle back and forth between the two. # emerge info Portage 2.0.50-r7 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.5-gentoo-r1) ================================================================= System uname: 2.6.5-gentoo-r1 i686 Pentium II (Klamath) Gentoo Base System version 1.4.15 Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=i686 -funroll-loops -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=i686 -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS=" http://tsp.yggdrasil.home/tsp-cache/gentoo.oregonstate.edu http://tsp.yggdrasil.home/tsp-cache/sunsite.cnlab-switch.ch/ftp/mirror/gentoo http://tsp.yggdrasil.home/tsp-cache/www.ibiblio.org/pub/Linux/distributions/gentoo http://sunsite.cnlab-switch.ch/ftp/mirror/gentoo http://gentoo.oregonstate.edu " MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="apm arts avi berkdb crypt cups encode foomaticdb gdbm gif gpm gtk gtk2 imlib jpeg libg++ libwww mad mikmod motif mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl svga tcpd truetype x86 xml2 xmms xv zlib" #
You probably have one of the following packages installed, which all still depend on mailwrapper-0.1. I think they should be updated or scrapped. exim/exim-4.30.ebuild: =net-mail/mailwrapper-0.1 exim/exim-4.24-r3.ebuild: =net-mail/mailwrapper-0.1 exim/exim-4.33-r1.ebuild: =net-mail/mailwrapper-0.1 postfix/postfix-2.0.19-r2.ebuild: =net-mail/mailwrapper-0.1" sendmail/sendmail-8.12.11-r1.ebuild: =net-mail/mailwrapper-0.1" sendmail/sendmail-8.12.11-r2.ebuild: =net-mail/mailwrapper-0.1" ssmtp/ssmtp-2.60.4-r2.ebuild:RDEPEND="=net-mail/mailwrapper-0.1 ssmtp/ssmtp-2.60.7.ebuild:RDEPEND="=net-mail/mailwrapper-0.1
Yeah, it's essentially a portage glitch that there's no simple way to only upgrade mailwrapper if the corresponding mta is upgraded as well. I'm going to remove the mailwrapper-0.1-based mta ebuilds soon, but I would like to get the 0.2-based versions a little better tested first. To prevent mailwrapper from upgrading you can # echo 'net-mail/mailwrapper' >> /etc/portage/package.mask but you'll probably want to remove the mask eventually.
Yes, I use ssmtp/ssmtp in these computers. They are hardware challenged computers built for specific purposes. Installing postfix would be way overkill. But I still need to get out cron-related mail to the mail server in the LAN, which ssmtp does quite well. Is there no way to say in the ssmtp ebuld that it needs mailwrapper version 0.1 *or*higher* ? Biker
When I follow Grant's instructions: echo 'net-mail/mailwrapper' >> /etc/portage/package.mask and then perform: emerge -up --deep world I get: !!! all ebuilds that could satisfy "=net-mail/mailwrapper-0.1" have been masked.!!! possible candidates are: - net-mail/mailwrapper-0.1 (masked by: package.mask) !!! (dependency required by "mail-mta/ssmtp-2.60.7" [ebuild]) !!! Problem with ebuild sys-apps/anacron-2.3 !!! Possibly a DEPEND/*DEPEND problem. !!! Depgraph creation failed.
CVS now has a stable ssmtp ebuild w/ "mailwrapper" as a USE flag. If you don't want mailwrapper (and most people don't), and you can survive a moment or two of mta downtime, just kill ssmtp, unmerge mailwrapper, and emerge the new ssmtp.
Should be fixed now.
