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
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
|
Details
Sane:
* 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 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.
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.
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.