39447 2004-01-26 06:08 0000 cyrus-sasl-2.1.17 setup invalid options 2004-01-28 06:58:55 0000 1 1 1 Unclassified Gentoo Linux Ebuilds unspecified x86 Linux RESOLVED FIXED P2 normal --- 1 moonwalker@astro.nu net-mail@gentoo.org dberkholz@gentoo.org max@gentoo.org tseng@gentoo.org moonwalker@astro.nu 2004-01-26 06:08:02 0000 The 2.1.17 build is still insisting on adding the -T and -H options to /etc/conf.d/saslauthd, although thos been now is reported as invalid by sasl. Also, on emerge those entries are triggered in /var/log/auth.log by the ebuild: Jan 26 13:40:33 merc saslpasswd2: setpass succeeded for login Jan 26 13:40:33 merc saslpasswd2: Couldn't delete entry in /var/tmp/portage/cyrus-sasl-2.1.17/image//etc/sasl2/sasldb2: gdbm_errno=15 Jan 26 13:40:33 merc saslpasswd2: Couldn't delete entry in /var/tmp/portage/cyrus-sasl-2.1.17/image//etc/sasl2/sasldb2: gdbm_errno=15 Jan 26 13:40:33 merc saslpasswd2: Couldn't delete entry in /var/tmp/portage/cyrus-sasl-2.1.17/image//etc/sasl2/sasldb2: gdbm_errno=15 Jan 26 13:40:33 merc saslpasswd2: setpass succeeded for login Jan 26 13:40:33 merc saslpasswd2: Couldn't delete entry in /var/tmp/portage/cyrus-sasl-2.1.17/image//etc/sasl2/sasldb2: gdbm_errno=15 Jan 26 13:40:33 merc saslpasswd2: Couldn't delete entry in /var/tmp/portage/cyrus-sasl-2.1.17/image//etc/sasl2/sasldb2: gdbm_errno=15 Jan 26 13:40:33 merc saslpasswd2: Couldn't delete entry in /var/tmp/portage/cyrus-sasl-2.1.17/image//etc/sasl2/sasldb2: gdbm_errno=15 Which possibly have to do with this WARNING in the ebuild: ******************************************************** * WARNING: * Plugins are being installed into /var/tmp/portage/cyrus-sasl-2.1.17/image//usr/lib/sasl2, * but the library will look for them in /usr/lib/sasl2. * You need to make sure that the plugins will eventually * be in /usr/lib/sasl2 -- the easiest way is to make a * symbolic link from /usr/lib/sasl2 to /var/tmp/portage/cyrus-sasl-2.1.17/image//usr/lib/sasl2, * but this may not be appropriate for your site, so this * installation procedure won't do it for you. * * If you don't want to do this for some reason, you can * set the location where the library will look for plugins * by setting the environment variable SASL_PATH to the path * the library should use. ******************************************************** Which is quite miss guiding as the path refered to are gone as portage cleans it out on finalizing. Reproducible: Always Steps to Reproduce: 1. 2. 3. max@gentoo.org 2004-01-28 06:58:55 0000 Fixed in 2.1.17 (much more flexible /etc/conf.d/saslauthd conf file). Also, you can ignore those warnings during emerge. However, if they persist during regular operations, open another bug. Thanks.