The dependencies seem to be screwed up on the new e-build. To summarize the problem, you must use mit-krb5 package for either kerberos 4 or kerberos 5 support in fetchmail as it currently stands. However, the 2.6.5 ebuild wants to install kth-krb for kerberos support. Simillarly heimdal doesn't work for version 5 support. Besides fixing the dependency it would probably be good to atleast throw something up to mention that kerberos support for version 4 needs to be the MIT version and kth-krb must not be installed. Reproducible: Always Steps to Reproduce: 1. emerge mit-krb5 heimdal -C 2. emerge kth-krb 3. USE="krb4" emerge fetchmail-2.6.5 -or- 1. emerge mit-krb5 kth-krb -C 2. emerge heimdal 3. USE="kerberos" emerge fetchmail2.6.5 -or- 1. emerge mit-krb5 -C 2. emerge kth-krb heimdal 3. USE="kerberos krb4" emerge fetchmail2.6.5 Actual Results: Ebuild aborts durring configure Expected Results: Ebuild should compile properly with kerberos support Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.3-mm1) ================================================================= System uname: 2.6.3-mm1 i686 AMD Athlon(tm) XP 1600+ Gentoo Base System version 1.4.3.13 Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.7.7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O3 -fomit-frame-pointer -mmmx -msse -pipe -m3dnow" 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/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/root/Port-overlay" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="3dnow X alsa apm arts avi berkdb canna cdr crypt cups dga dvd encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib java jpeg kde kerberos libg++ libwww mad mikmod mmx motif mozilla mpeg ncurses nls nocardbus offensive oggvorbis opengl oss pam pda pdflib perl png ppds python qt quicktime readline sdl slang spell sse ssl svga tcltk tcpd tetex truetype usb x86 xml2 xmms xv zlib"
Uh, is anyone going to fix this problem, since the heimdal and kth-krb break this e-build and kth-krb is in the dependncies for the e-build for using kerberos 4?
Actually, with USE="kerberos krb4" the emerge failed: checking for Kerberos IV in /usr/kerberos... not found checking for Kerberos IV in /usr/kerberosIV... not found checking for Kerberos IV in /usr/athena/usr... not found configure: error: Kerberos 4 libraries not found !!! ERROR: net-mail/fetchmail-6.2.5-r2 failed.
Actually when I hacked out the dependencies for kerberos from the e-build and tried various combinations of the 3 libraries I found that fetchmail will not build against either the heimdal or kth-krb kerberos packages. Although I do not know if mit's or heimdal's kerberos 5 implementation is the default virtual kerberos package, the heimdal package may also break the build process. However, with the krb4 flag will ALWAYS break the build because it requires kth-krb to be installed, and kth-krb being installed will always break the build process.
Basically it is possible to build a kerbanized version of fetchmail. However, it requires removing the dependencies on kth-krb and heimdal packages, because fetchmail doesn't properly build against these libraries. Both the Kerberos and Krb4 flags are functional when using mit-krb5 package for kerberos v4 and v5.
I use heimdal for kerberos support. Does this mean I wont be able to compile fetchmail? Maybe I dont need kerberos support in fetchmail. I will try recompile without and see.
Yes, it means with the current version you won't be able to compile fetchmail with kerberos support. However, since you don't need the support it shouldn't be an issue.
Why doesn't someone finally fix this? --- /usr/portage/net-mail/fetchmail/fetchmail-6.2.5-r2.ebuild 2005-07-01 18:35:53.000000000 +0200 +++ /usr/portage/net-mail/fetchmail/fetchmail-6.2.5-r2.ebuild-new 2005-07-15 21:39:11.000000000 +0200 @@ -13,10 +13,12 @@ KEYWORDS="~alpha ~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~s390 ~sparc ~x86" IUSE="ssl nls ipv6 kerberos krb4 hesiod" +# fetchmail support only MIT KRB5, not heimdal, see +# http://www.catb.org/~esr/fetchmail/fetchmail-FAQ.html#K4 +# mmokrejs RDEPEND="hesiod? ( net-dns/hesiod ) ssl? ( >=dev-libs/openssl-0.9.6 ) - kerberos? ( virtual/krb5 ) - krb4? ( app-crypt/kth-krb ) + mit-krb5? ( app-crypt/mit-krb5 ) sys-devel/gettext elibc_FreeBSD? ( sys-libs/com_err )"
Would someone commit the last patch please? ;-)
@net-mail herd - what's going on here?! Upstream explicitly says that this thing does NOT support heimdal or kth-krb, so could someone finally fix the invalid dependencies in >=fetchmail-6.2.4 ? TIA.
fixed in CVS. Not bumped