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-nipy) Fails To Install in Fedora 39: can't install python3-nipy: - nothing provides python3.11dist(transforms3d) needed by python3-nipy-0.5.0^9512cd9git20230206-7.fc38.x86_64 - nothing provides python(abi) = 3.11 needed by python3-nipy-0.5.0^9512cd9git20230206-7.fc38.x86_64 - nothing provides python3.11dist(six) >= 1.9 needed by python3-nipy-0.5.0^9512cd9git20230206-7.fc38.x86_64 - nothing provides python3.11dist(numpy) >= 1.14 needed by python3-nipy-0.5.0^9512cd9git20230206-7.fc38.x86_64 - nothing provides python3.11dist(scipy) >= 1 needed by python3-nipy-0.5.0^9512cd9git20230206-7.fc38.x86_64 - nothing provides python3.11dist(sympy) >= 1 needed by python3-nipy-0.5.0^9512cd9git20230206-7.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-nipy 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.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
Ankur, I see you assigned this bugzilla 2 months ago. Have you made any progress? The package fails to install and fails to build. Fedora 39 Beta was just released. Is it probable that this will be fixed (or worked around) in time for the Fedora 39 Final Freeze (2023-10-03)? If not, could you please consider retiring the package, so we can obsolete it and unblock clean upgrades to Fedora 39? A retired package can be reintroduced later during the lifetime of Fedora 39.
Well, there are PRs, but upstream hasn't merged them. We're still getting errors in the build. Ben, what do you think we should do here?
I’m poking at it in https://src.fedoraproject.org/rpms/python-nipy/pull-request/6 now. I filed a significant number of new PR’s which upstream merged promptly, along with a couple of fixes of their own, and there is now only one remaining error.
Thanks so much for working on this Ben :)
I can’t seem to find a way to skip or work around the remaining error[1]. However, the actual tests do pass, so if I did disable the tests (or ignore their failure) we would have a working nipy package with less protection against regressions. While investigating this, I found that nipy relies heavily on numpy.distutils[2], which will disappear[3] as soon as Fedora’s numpy is updated to 1.26[4] (the first version that official supports Python 3.12). I’m tempted to disable the tests for long enough to get a good build in F39 final (building in F40 too, of course), with the understanding that if upstream isn’t able to port away from numpy.distutils in time for F40 we probably won’t be able to save the package. Advice welcome. [1] https://github.com/nipy/nipy/issues/495#issuecomment-1730122793 [2] https://github.com/nipy/nipy/issues/526 [3] https://numpy.org/doc/stable/reference/distutils.html#numpy.distutils.misc_util.Configuration [4] https://github.com/numpy/numpy/releases/tag/v1.26.0
(In reply to Ben Beasley from comment #7) > I’m tempted to disable the tests for long enough to get a good build in F39 > final (building in F40 too, of course), with the understanding that if > upstream isn’t able to port away from numpy.distutils in time for F40 we > probably won’t be able to save the package. That sounds reasonable. But, if I understand things correctly, it also means a maintenance burden on our part, dragging that package along and nursing it. On the upside: upstream appears active. SO, there's good hope of the package being ported away from `numpy-distutils`. With python-nipy being a leaf package, the alternative would be to drop it and re-introduce it when it's fixed.
(In reply to Sandro from comment #8) > (In reply to Ben Beasley from comment #7) > > I’m tempted to disable the tests for long enough to get a good build in F39 > > final (building in F40 too, of course), with the understanding that if > > upstream isn’t able to port away from numpy.distutils in time for F40 we > > probably won’t be able to save the package. > > That sounds reasonable. But, if I understand things correctly, it also means > a maintenance burden on our part, dragging that package along and nursing > it. On the upside: upstream appears active. SO, there's good hope of the > package being ported away from `numpy-distutils`. Well… basically, we now have a fully working and fairly clean package now, with all of the necessary patches merged upstream. The only problem is that we can’t rely on the exit status of the test suite. I think there probably won’t be much to do to the package in the lifecycle of F39. The only problem is that it’s possible that an update to numpy 1.26 will come through and cause the package to FTBFS. This certainly won’t be ready in time for the F39 final release, and it won’t cause the package to FTI or break at runtime. With the benefit of a night’s sleep, I still think I want to let the package coast through F39 and prepare ourselves to possibly retire it for F40 if upstream isn’t able to keep up with porting to meson and pytest.
(In reply to Ben Beasley from comment #9) > With the benefit of a night’s sleep, I still think I want to let the package > coast through F39 and prepare ourselves to possibly retire it for F40 if > upstream isn’t able to keep up with porting to meson and pytest. Let's do that then. F40 release should be plenty of time for upstream to get things sorted.
FEDORA-2023-5bd1c01110 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5bd1c01110
FEDORA-2023-5bd1c01110 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
Reopening for Fedora 39.
(In reply to Miro Hrončok from comment #13) > Reopening for Fedora 39. The F39 build is in progress, and a Bodhi update will be ready shortly.
FEDORA-2023-ed0adf8107 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-ed0adf8107
FEDORA-2023-ed0adf8107 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-ed0adf8107` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-ed0adf8107 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-ed0adf8107 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.