Bug 1055593
| Summary: | Installing spamassassin breaks gnome-keyring PGP integration due to dependency on old gnupg | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Catanzaro <mcatanzaro> |
| Component: | spamassassin | Assignee: | Warren Togami <wtogami> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | kevin, nb, plautrba, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | spamassassin-3.4.0-4.fc20 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-01 22:21:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Michael Catanzaro
2014-01-20 15:19:57 UTC
So, spamassassin uses gnupg for it's sa-update script (to verify that updates are correctly signed, etc). I agree it would be great to port this over to gnupg2, but as far as I know thats not yet been done. Might you be willing to file an upstream bug on this? Or would you like me to do so? I'd appreciate it if you would: I don't know anything about spamassassin beyond that it's needed to build Evolution. Thanks! gpg is often a symlink to gpg2 (e.g. in openSUSE), so unless spamassassin is broken there, supporting both should be easy. P.S. Evolution has just been changed to prefer gpg2 to gpg instead of vice-versa. A quick test seems to indicate that it can use gpg2 ok. I'll need to do some more tests, but possibly we can just patch it over to gpg2. Can you test this scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=6465137 ? It contains this switch to gnupg2 as well as a fix for amavisd ( bug 1057926 ) Feedback most welcome... Thanks! I've installed it and I'll let you know if I see anything odd, but as I mentioned I don't know anything about spamassassin (I rely on Google's spam filtering) so if everything's broken I probably won't notice.... spamassassin-3.4.0-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/spamassassin-3.4.0-3.fc20 Package spamassassin-3.4.0-3.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing spamassassin-3.4.0-3.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-4171/spamassassin-3.4.0-3.fc20 then log in and leave karma (feedback). spamassassin-3.4.0-4.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/spamassassin-3.4.0-4.fc20 Package spamassassin-3.4.0-4.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing spamassassin-3.4.0-4.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-6643/spamassassin-3.4.0-4.fc20 then log in and leave karma (feedback). spamassassin-3.4.0-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |