Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ Your package (python-pyunicorn) Fails To Install in Fedora 39: can't install python3-pyunicorn: - nothing provides python(abi) = 3.11 needed by python3-pyunicorn-0.6.1-12.fc38.x86_64 - nothing provides python3.11dist(numpy) >= 1.14 needed by python3-pyunicorn-0.6.1-12.fc38.x86_64 - nothing provides python3.11dist(scipy) >= 1 needed by python3-pyunicorn-0.6.1-12.fc38.x86_64 - nothing provides python3.11dist(igraph) >= 0.7 needed by python3-pyunicorn-0.6.1-12.fc38.x86_64 If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock: $ mock -r fedora-39-x86_64 --config-opts mirrored=False install python3-pyunicorn P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages Thanks!
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 7+ weeks. This is the first reminder (step 3) from the policy. Don't hesitate to ask for help on devel.org if you are unsure how to fix this bug.
Removed dependency on python3-pytest-flake8 and tried a scratch build for f38, due to python3-basemap not yet being fixed in rawhide. Package python-pytest-flake8 is going to be retired. But it appears it wasn't used by pyunicorn anyway, since only the 'units' environment is being selected, which doesn't require pytest-flake8: %tox -e units It looks like pyunicorn is not compatible with the updated numpy package and requires some refactoring. Issue has been reported upstream.
For all the gory details: https://kojipkgs.fedoraproject.org//work/tasks/6650/104026650/build.log
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
FEDORA-2023-012e3c64d6 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-012e3c64d6
FEDORA-2023-012e3c64d6 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
Please also create an update for Fedora 39. Note that 0.7.0a1 will sort higher than 0.7.0. Use 0.7.0~a1 to solve this problem.
(In reply to Miro Hrončok from comment #7) > Please also create an update for Fedora 39. It's pending: https://bodhi.fedoraproject.org/updates/FEDORA-2023-cadd8181fb > Note that 0.7.0a1 will sort higher than 0.7.0. Use 0.7.0~a1 to solve this > problem. Should I pull the update for f39? Since `0.7.0a1` already landed in rawhide, would changing Version: even work?
(In reply to Sandro from comment #8) > (In reply to Miro Hrončok from comment #7) > > Please also create an update for Fedora 39. > > It's pending: https://bodhi.fedoraproject.org/updates/FEDORA-2023-cadd8181fb Coudl you amkr the update as fixing this bugzilla? That way, if the freeze exception request gets approved, the update can be pushed. > > Note that 0.7.0a1 will sort higher than 0.7.0. Use 0.7.0~a1 to solve this > > problem. > > Should I pull the update for f39? You can replace the build in that update once ready. > Since `0.7.0a1` already landed in rawhide, > would changing Version: even work? Considering it is a development release, I'd say yes, do it.
s/amkr/mark/
(In reply to Miro Hrončok from comment #9) > Coudl you amkr the update as fixing this bugzilla? That way, if the freeze > exception request gets approved, the update can be pushed. Hmm. Apparently Bodhi didn't parse the commit message correctly. Anyway, update with the version fix is on its way. I make sure this bug is tagged when pushing it. > Considering it is a development release, I'd say yes, do it. Done!
Builds failed. I know why. Upstream is using `version = 0.7.0a1` https://github.com/pik-copan/pyunicorn/blob/aa56ad1db9b53c0cd33d41e06303293817640047/setup.cfg#L10C1-L10C18 Now %{version} and internal version no longer match. So, is that sorting issue you mentioned @mhroncok RPM specific? Or would that also fail to sort semantically? Reason: Do I work around it downstream? Or do I ask upstream for a fix, making them aware of the issue?
I decided to work around it for now. But Koji is being slow atm. Both builds are pending. I've gotta go. Will check the status in a few hours. Feel free to intervene.
No, the tilde is RPM-only thing and hence downstream-only thing. What you need is: - keep upstream version as 0.7.0a1 - set RPM Version to 0.7.0~a1 - wherever you use %{version} in the specfile, use something else (e.g. %{upstream_version} as you did in https://src.fedoraproject.org/rpms/python-pyunicorn/c/229e99d58aa148c3f96b359cfb55810ac3d7c5ce?branch=rawhide)
FEDORA-2023-881b2f61b1 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-881b2f61b1
FEDORA-2023-881b2f61b1 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-7c49082cdd has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7c49082cdd
(In reply to Miro Hrončok from comment #14) > No, the tilde is RPM-only thing and hence downstream-only thing. Thanks for the clarification. It should be all good now. I pulled the 0.7.0a1 update from fc39 now the 0.7.0~a1 is pending in Bodhi.
FEDORA-2023-7c49082cdd 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-2023-7c49082cdd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-7c49082cdd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Discussed in ticket: https://pagure.io/fedora-qa/blocker-review/issue/1273 The decision to classify this bug as an AcceptedFreezeException was made: "We usually pull in FTI fixes."
The updated `pyunicorn` depends on `h5netcdf`, which is not yet in Fedora. But a review has been requested in bug 2213518.
FEDORA-2023-180cc0af8c has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-180cc0af8c
FEDORA-2023-180cc0af8c has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
*** Bug 2239679 has been marked as a duplicate of this bug. ***
FEDORA-2023-7c49082cdd has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.