Noticed this since it stops python-missingo from installing too: https://koschei.fedoraproject.org/package/python-missingno?collection=f33 I tested it locally too: $ sudo dnf --releasever=33 install python3-geoplot Error: Problem: conflicting requests - nothing provides python3.8dist(contextily) >= 1.0rc2 needed by python3-geoplot-0.4.0-1.fc33.noarch (try to add '--skip-broken' to skip uninstallable packages)
Uh, also applies to F32 for the latest build according to koschei: https://koschei.fedoraproject.org/package/python-missingno?collection=f32 2020-04-25 00:12:32 Package resolution failed Problem: conflicting requests - nothing provides python3.8dist(contextily) >= 1.0rc2 needed by python3-geoplot-0.4.0-1.fc32.noarch
This is a bug in the dependency generator. contextily is 1.0.0, which it normalizes to 1. geoplot requires 1.0rc2, but it does _not_ strip the .0 and it should probably change rc2 to ~rc2... I can patch this in the meantime though.
FEDORA-2020-0ada2824d2 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-0ada2824d2
If my information is up to date, you should get: python3.8dist(contextily) >= 1~rc2 On rawhide. Is that correct?
Least build from Koschei before patching the dependency has: $ rpm -qp --requires python3-geoplot-0.4.0-1.fc33.noarch.rpm ... python3.8dist(contextily) >= 1~rc2 So this is indeed fixed in rawhide. We are seriously way behind with backports to stable Fedoras :(
s/Least/Latest/
FEDORA-2020-0ada2824d2 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-0ada2824d2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-0ada2824d2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Since this bugzilla was repurposed, could you please edit the update not to close it?
It won't.
Thanks.
FEDORA-2020-0ada2824d2 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
There were a lot of changes in the generator, and they can usually be worked around pretty easily, so backporting is not a very high priority for us. Please comment if we should do it soon, otherwise this is on the backburner.
I've since updated to a version that requires >=1.0.0, which has always worked correctly, so there's no rush here.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 EOL if it remains open with a Fedora 'version' of '32'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.