The ebuild for cyrus-sasl was change with version 2.1.17 to build with '--with-dblib=berkeley' only if gdbm wasn't used as a USE statement. This, however, broke my setup which uses berkeley as for some reason the current ebuilds only use gdbm. I tried first specifying berkdb as before and when this didn't work looked to figure out why. Reproducible: Always Steps to Reproduce: 1. emerge cyrus-sasl 2. check sample sasl2db with file, it shows gdbm as the type 3. adding back the logic from the 2.1.14 ebuild to emerge with 'berkdb' makes it work Actual Results: I was unable to recieve or check mail in my user accounts. Expected Results: This is a bad bug as I run gentoo-stable here for my mailserver deliberately so things like this wont suddenly hit me from behind. I read through some other bug reports and feel that the new version was pushed to stable too quickly with insufficient testing. Portage 2.0.50-r9 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3.20040420-r0, 2.6.5-gentoo-r1) ================================================================= System uname: 2.6.5-gentoo-r1 i686 Pentium III (Katmai) Gentoo Base System version 1.4.16 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium3 -fprefetch-loop-arrays -funroll-loops -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium3 -fprefetch-loop-arrays -funroll-loops -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="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X apm avi berkdb bonobo cdr crypt cups directfb encode esd evo fam foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml guile imap imlib jpeg ldap libg++ libwww mad maildir mikmod mozilla mpeg ncurses nls ofx oggvorbis opengl oss pam pdflib perl png ppds python quicktime readline samba sasl sdl slang slp spell ssl svga tcpd truetype usb x86 xinerama xml2 xmms xv zlib"
IMO, the ebuild should abort if USE="gdbm berkdb". 2.1.14 default to berkdb if both in USE while >=2.1.17 build with gdbm support if both present. As of now, you can do `echo "dev-libs/cyrus-sasl -gdbm" >> /etc/portage/package.use ; emerge cyrus-sasl` man 5 portage /package.use for more info if you are not familiar with /etc/package.* usages.
I see that cyrus-sasl-2.1.19 (and perhaps earlier versions) issues the following messages when both gdbm and berkdb are in USE flags: ------ new messages start here ------ * You have both "gdbm" and "berkdb" in your USE flags. * please choose only one for your SASLdb database backend. * It would be best practice to add the set of USE flags that you use for this * package to the file: /etc/portage/package.use. Example: * `echo "dev-libs/cyrus-sasl gdbm -berkdb" >> /etc/portage/package.use` * to build cyrus-sasl with GNU database as your SASLdb backend. ------ new messages end here ------ I think this is a great warning and I appreciate it. However, I make one further request: Could you add to the message something like: "We recommend choosing..." or "To help you choose, see the following web page..." or something similar. I don't know enough about the differences to know which one to choose. I don't expect Gentoo developers to make the choice for me, or to hold my hand. However, a reference to an appropriate web page seems to me to be a good idea. As I said earlier. I appreciate the new warning. My suggestion is a possible improvement. Thanks.
merc root # echo "dev-libs/cyrus-sasl berkdb -gdbm" >> /etc/portage/package.use -bash: /etc/portage/package.use: No such file or directory
*** Bug 58355 has been marked as a duplicate of this bug. ***
fixed in cyrus-sasl-2.1.20. closing.
