Description of problem: With these packages installed: blueman-nemo-2.3-1.fc36.noarch blueman-nautilus-2.3-1.fc36.noarch blueman-2.3-1.fc36.x86_64 running dnf check-update gives this output: Obsoleting Packages blueman.x86_64 1:2.2.3-2.fc36 fedora blueman-nautilus.noarch 1:2.3-1.fc36 @updates-testing blueman-2.3-1 is in Fedora updates stable Version-Release number of selected component (if applicable): blueman-2.3-1 How reproducible: Always present Steps to Reproduce: 1. Update to blueman-2.3-1 2. run dnf check-update 3. See blueman-2.2.3-2 wanting to obsolete blueman-nautilus-2.3-1 Actual results: Expected results: Additional info:
This is a bit of a hard candy. blueman 2.2.3 has an unversioned "Obsoletes: blueman-nautilus", so it will always want to replace it. Since it's in the "fedora" repo (i.e. the "release" repo, not the "updates" one), there is no way to make 2.2.3 just go away. I'll need to check if there's some way to mark blueman-nautilus-2.3 as not obsoleted, without affecting the old blueman 2.2.3 package.
FEDORA-2022-39cb1ddc11 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-39cb1ddc11
FEDORA-2022-a02aa1e171 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a02aa1e171
Will blueman-nautilus reappear in Fedora 37?
FEDORA-2022-a02aa1e171 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-a02aa1e171` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a02aa1e171 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-39cb1ddc11 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-39cb1ddc11` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-39cb1ddc11 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-369d912790 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-369d912790` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-369d912790 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-a73b6f7353 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-a73b6f7353` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a73b6f7353 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-369d912790 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-a73b6f7353 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.