Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#25589 - [cyrus-sasl, libsasl] Replaces/conflicts/provides are nonsensical

Attached to Project: Arch Linux
Opened by Dan McGee (toofishes) - Monday, 15 August 2011, 19:42 GMT
Last edited by Jan de Groot (JGC) - Monday, 03 October 2011, 13:34 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


* cyrus-sasl (and its three split packages -gssapi, -ldap, and -sql) depend on libsasl.
* cyrus-sasl-gssapi, -ldap, and -sql replace cyrus-sasl-plugins.

Not sane:
libsasl conflicts with and provides cyrus-sasl-plugins. This happens to work with the current pacman resolving logic because don't do dependency/provision comparison with replaces, but will totally fail with 4.0 and  FS#23410 .

What were you trying to accomplish here with this setup? The conflicts belong on the -gssapi/-ldap/-sql packages, and the provision seems totally unnecessary.
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 03 October 2011, 13:34 GMT
Reason for closing:  Fixed
Additional comments about closing:  cyrus-sasl-plugins is no longer used in packages. Provides has been removed from libsasl.
Comment by Jan de Groot (JGC) - Tuesday, 16 August 2011, 05:49 GMT
We have/had still packages depending on cyrus-sasl-plugins. Part of cyrus-sasl-plugins moved to the standalone packages, but part of it moved to libsasl, that's why I added the provides to libsasl also.

We should get rid of the cyrus-sasl-plugins dependencies first before we can remove the provides. Without the provides, updating libsasl will fail completely now.