After emerging mysql-4.0.23-r1 and recompiling pam_mysql and cyrus-sasl, any request to a mysql authenticated PAM results in: Jan 19 13:34:22 [imap] unable to dlopen /usr/lib/sasl2/libsql.so.2: libmysqlclient.so.12: cannot open shared object file: No such file or directory Jan 19 13:34:22 [saslauthd] PAM unable to dlopen(/lib/security/pam_mysql.so) Jan 19 13:34:22 [saslauthd] PAM [dlerror: /lib/security/pam_mysql.so: undefined symbol: ERR_get_error_line_data ] Jan 19 13:34:22 [saslauthd] PAM adding faulty module: /lib/security/pam_mysql.so To confess, I don't know if it is really a pam_mysql issue, a cyrus-sasl issue or a MySQL issue. As a matter of fact, pam_mysql started working again after downgrading MySQL to 4.0.22 and re-emerging pam_mysql. So I guess, it could also be a MySQL related problem. Reproducible: Always Steps to Reproduce: 1. upgrade MySQL to MySQL-4.0.23-r1 2. re-emerge pam_mysql-0.5 Actual Results: pam_mysql-0.5 stopped working; invocation fails with: [saslauthd] PAM unable to dlopen(/lib/security/pam_mysql.so) [saslauthd] PAM [dlerror: /lib/security/pam_mysql.so: undefined symbol: ERR_get_error_line_data
Portage doesn't support reverse dependencies yet. `revdep-rebuild -p` should solve the issue.
No, it won
No, it won´t. See Bug 78678 :-/
Indeed. Even if it's bump for security reasons - this shouldn't happen. :| *** This bug has been marked as a duplicate of 78678 ***