After installing dev-libs/cyrus-sasl I always get this messages: * Generating an empty sasldb2 with correct permissions ... /var/tmp/portage/dev-libs/cyrus-sasl-2.1.23-r1/temp/environment: line 4671: //usr/sbin/saslpasswd2: No such file or directory * ERROR: dev-libs/cyrus-sasl-2.1.23-r1 failed: * Failed to generate sasldb2 * * Call stack: * ebuild.sh, line 49: Called pkg_postinst * environment, line 4671: Called die * The specific snippet of code: * echo "p" | "${ROOT}/usr/sbin/saslpasswd2" -f "${ROOT}/etc/sasl2/sasldb2" -p login || die "Failed to generate sasldb2"; * * If you need support, post the output of 'emerge --info =dev-libs/cyrus-sasl-2.1.23-r1', * the complete build log and the output of 'emerge -pqv =dev-libs/cyrus-sasl-2.1.23-r1'. !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH="" JAVA_HOME="" JAVACFLAGS="" COMPILER="" and of course, the output of emerge --info * The complete build log is located at '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.23-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.23-r1/temp/environment'. * S: '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.23-r1/work/cyrus-sasl-2.1.23' !!! FAILED postinst: 1 Reproducible: Always
Created attachment 207808 [details] emerge --info
Hmm the ebuild reads: echo "p" | "${EROOT}/usr/sbin/saslpasswd2" -f "${EROOT}/etc/sasl2/sasldb2" -p login \ || die "Failed to generate sasldb2" whereas your error reads: echo "p" | "${ROOT}/usr/sbin/saslpasswd2" -f "${ROOT}/etc/sasl2/sasldb2" -p login || die "Failed to generate sasldb2"; Do you have cyrus-sasl already installed and try to upgrade it? Then maybe you need to unmerge it and reinstall it. Anyway, try syncing, uninstalling and reinstalling cyrus-sasl.
(In reply to comment #2) > Hmm the ebuild reads: > echo "p" | "${EROOT}/usr/sbin/saslpasswd2" -f "${EROOT}/etc/sasl2/sasldb2" -p > login \ > || die "Failed to generate sasldb2" > whereas your error reads: > echo "p" | "${ROOT}/usr/sbin/saslpasswd2" -f "${ROOT}/etc/sasl2/sasldb2" -p > login || die "Failed to generate sasldb2"; > > Do you have cyrus-sasl already installed and try to upgrade it? Then maybe you > need to unmerge it and reinstall it. Anyway, try syncing, uninstalling and > reinstalling cyrus-sasl. > Ok, screw my post, i was thinking that was about Gentoo/Prefix rather than Gentoo/Alt-FreeBSD. Sorry for the noise :/
(In reply to comment #3) > > Do you have cyrus-sasl already installed and try to upgrade it? Then maybe you > > need to unmerge it and reinstall it. Anyway, try syncing, uninstalling and > > reinstalling cyrus-sasl. > > > > Ok, screw my post, i was thinking that was about Gentoo/Prefix rather than > Gentoo/Alt-FreeBSD. Sorry for the noise :/ > I have a server with Gentoo/FreeBSD-6.2 and now trying 7.2. I seen this error during all other installations. I don't really use sasl now, so can't diagnose whether it works at all. I see that /usr/sbin/saslpasswd2 not installed.
my use-flags: berkdb crypt ldap* pam postgres ssl -authdaemond -gdbm (-java) (-kerberos) -mysql -ntlm_unsupported_patch -sample -sqlite -srp -urandom
Created attachment 211667 [details] emerge_info
I have this error too. * * ERROR: dev-libs/cyrus-sasl-2.1.23-r1 failed. * Call stack: * ebuild.sh, line 49: Called pkg_postinst * environment, line 4635: Called die * The specific snippet of code: * echo "p" | "${ROOT}/usr/sbin/saslpasswd2" -f "${ROOT}/etc/sasl2/sasldb2" -p login || die "Failed to generate sasldb2"; * The die message: * Failed to generate sasldb2 * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.23-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.23-r1/temp/environment'. * * GNU info directory index is up-to-date. my emerge info: http://bugs.gentoo.org/attachment.cgi?id=211667&action=edit
There is no problem in g/fbsd-8.0 with =dev-libs/cyrus-sasl-2.1.23-r2. /usr/sbin/saslpasswd2 present. Can't change Version field of this bug.
This no longer reproduced i think.
