Description of problem: nitroshare-kservice supplements dolphin and konqueror, so it is marked as a weak dependency of these. Therefore nitroshare now lands on new live composes and users who (re-) install dolphin or konqueror will get nitroshare too. This should not happen because not all users want nitroshare. I suggest to either replace the Supplements by Enhances or use rich dependencies, so that nitroshare-kservice gets only installed when dolphin/konqueror *AND* nitroshare are (to be) installed. Version-Release number of selected component (if applicable): 0.3.4-1.fc27 How reproducible: Always Steps to Reproduce: 1. dnf reinstall dolphin (on a system with dolphin already installed, otherwise just install) Actual results: Weak dependency nitroshare-kservice is pulled in Dependencies resolved. =============================================================================================================================================================================================================== Package Arch Version Repository Size =============================================================================================================================================================================================================== Reinstalling: dolphin x86_64 17.08.1-1.fc27 fedora 3.3 M Installing dependencies: nitroshare x86_64 0.3.4-1.fc27 updates 189 k nitroshare-console x86_64 0.3.4-1.fc27 updates 9.1 k qhttpengine x86_64 1.0.0-1.fc27 updates 68 k qmdnsengine x86_64 0.1.0-1.fc27 updates 69 k Installing weak dependencies: nitroshare-kservice x86_64 0.3.4-1.fc27 updates 8.8 k Transaction Summary =============================================================================================================================================================================================================== Install 5 Packages Expected results: No nitroshare gets installed.
I'm referencing the following lines in nitroshare spec: https://src.fedoraproject.org/rpms/nitroshare/blob/master/f/nitroshare.spec#_92
Any news here? More and more KDE/Plasma users are upset about the unwanted installation of nitroshare :(
Fixed in Rawhide, Updates for 26 and 27 building.
nitroshare-0.3.4-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-babb021a3c
nitroshare-0.3.4-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f4a38854cc
nitroshare-0.3.4-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-babb021a3c
nitroshare-0.3.4-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-f4a38854cc
nitroshare-0.3.4-2.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
nitroshare-0.3.4-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
nitroshare-0.3.4-5.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-fbf964c927
nitroshare-0.3.4-5.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-fbf964c927
nitroshare-0.3.4-5.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.