Description of problem: Problem: conflicting requests - nothing provides python3.7dist(fslpy) >= 1.13.2 needed by python3-fsleyes-0.27.3-1.fc30.noarch - nothing provides python3.7dist(matplotlib) < 3.0 needed by python3-fsleyes-0.27.3-1.fc30.noarch Version-Release number of selected component (if applicable): python3-fsleyes-0.27.3-1.fc30.noarch It seems we have python3-fslpy-1.12.0-4.fc30 and python-matplotlib-3.0.2-1.fc30 right now.
Hrm, but how were these installed in the first place if the deps aren't present? I'll look into these. Must be something silly.
https://fedoraproject.org/wiki/Changes/EnablingPythonGeneratorsByDefault
python-fslpy-2.2.0-2.fc29 python-fsleyes-0.29.0-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-af54a76d11
python-fslpy-2.2.0-2.fc30 python-fsleyes-0.29.0-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f8a52fa6c2
python-fsleyes-0.29.0-1.fc30, python-fslpy-2.2.0-2.fc30 has been pushed to the Fedora 30 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-2019-f8a52fa6c2
python-fsleyes-0.29.0-1.fc29, python-fslpy-2.2.0-2.fc29 has been pushed to the Fedora 29 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-2019-af54a76d11
python-fsleyes-0.29.0-1.fc30, python-fslpy-2.2.0-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
python-fsleyes-0.29.0-1.fc29, python-fslpy-2.2.0-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.