Bug 2228002
| Summary: | sieveshell conflicts with sieveshell provided by cyrus-imapd | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Martin Osvald 🛹 <mosvald> |
| Component: | python-managesieve | Assignee: | Sandro <gui1ty> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 39 | CC: | gui1ty, ppisar |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | python-managesieve-0.7.1-23.fc42 python-managesieve-0.7.1-23.fc41 python-managesieve-0.7.1-21.fc40 python-managesieve-0.7.1-18.fc39 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-10-26 10:58:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Martin Osvald 🛹
2023-08-01 06:21:48 UTC
Thank you for the report. I wasn't aware of the conflict. I will look into possible solutions after Flock and my vacation thereafter. This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39. (In reply to Martin Osvald 🛹 from comment #0) > `python-managesieve` provides /usr/bin/sieveshell that is provided by > `cyrus-imapd` already. I think both binaries serve the same purpose and it's not unusual for different packages providing binaries with the same name. I could think of two possible solutions: 1. Use the alternative system 2. Rename `sieveshell` to something like `sieve-shell` or `sieve_shell`. My preference is option 1. With option 2 we'd be deviating from upstream and that would most likely raise questions with users installing `managesieve` expecting a `sieveshell` binary. If the tools identical, simply stop packaging that tool. Or move it to a subpackage and depend on "(cyrus-imapd or that-new-subpackage)". Nevertheless, now your package violates packaging guidelines and until you decide what to do, you need to add an explicit "Conflicts: cyrus-imapd" to python3-managesieve. (In reply to Petr Pisar from comment #4) > Nevertheless, now your package violates packaging guidelines and until you > decide what to do, you need to add an explicit "Conflicts: cyrus-imapd" to > python3-managesieve. The package has been in violation since its initial release for Fedora in 2020 when version 0.6 was packaged. Upstream's HISTORY file shows `sieveshell` was introduced in version 0.2 in 2004. Apparently the conflict was missed during package review. I adopted the package in June 2023. Anyway, I've added `Conflicts: cyrus-imapd-utils`. I believe both packages being installed alongside each other is rather rare, which probably contributed to this only being noticed now. The intended audience for cyrus-imapd is mail server administrators with Cyrus providing a sieve server. For managesieve the intended audience is mail users, who wish to manage sieve rules. FEDORA-2024-d27b841937 (python-managesieve-0.7.1-23.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2024-d27b841937 FEDORA-2024-d27b841937 (python-managesieve-0.7.1-23.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-1dffe765b7 (python-managesieve-0.7.1-18.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-1dffe765b7 FEDORA-2024-22c1b7511e (python-managesieve-0.7.1-21.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-22c1b7511e FEDORA-2024-24c67e53b2 (python-managesieve-0.7.1-23.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-24c67e53b2 FEDORA-2024-1dffe765b7 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-1dffe765b7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-1dffe765b7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-22c1b7511e has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-22c1b7511e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-22c1b7511e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-24c67e53b2 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-24c67e53b2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-24c67e53b2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Thanks for resolving this. FEDORA-2024-24c67e53b2 (python-managesieve-0.7.1-23.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-22c1b7511e (python-managesieve-0.7.1-21.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-1dffe765b7 (python-managesieve-0.7.1-18.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. |