In KMail, there should be implemented some warning mechanism when requested action (or function) is disabled because of missing library. For example: when I was trying to connect to email server using gsslib, Kmail showed: SASL(-4): no mechanism available: No worthy mechs found. After a while I figured out cyrus-sasl-gssapi is not installed. I suggest either adding this and similar libraries to dependencies or implementing some warning mechanism, which would tell user, what exactly is wrong.
Not sure how to expect kmail to have intimate knowledge of the implementation details of the platform and libraries it uses to give proper advice in situations like this. Problem being here is that gss support is optional (based on cyrus-sasl capabilities). It turns out cyrus-sasl-gssapi is a mere 31k itself... I wonder why this was split into a separate and optional non-default package anyway. cyrus-sasl folks, can you give some background/justification for the cyrus-sasl-gssapi split and/or some advice here?
It was split because of the dependencies of the plugin to allow for minimal installs. The question is whether comps is enough to solve this. Especially when comps are getting obsolete. Also the RPM Suggest support which might help is not yet in Fedora.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Rebasing to rawhide (FutureFeature) Re: comment #2 comps does support conditional dependencies, ie, install 'foo' if 'bar' is installed. which may (or may not) suffice to help here.
ping, any movement here, or should we just admit defeat and WONTFIX?
How about we just add Requires: cyrus-sasl-gssapi to kdepim.spec?
(If we disagree about the split, may as well opt out of it that way.)
That sounds like a viable option. But if you are going to go ahead with this, adding other SASL modules (if they are required) should be probably also considered.
Could a kmail try sasl_global_listmech(3) resp sasl_listmech(3) first to check if a method is available?
This is an issue for upstream discussion.