Dear package maintainer, this bugzilla is automated becasue the number of impacted packages it too high to go trough manually. It appears that your package failed to build with setuptools 74.1.3 and wheel 0.44 in https://copr.fedorainfracloud.org/coprs/churchyard/setuptools-74/package/python-moksha-hub/ While it succeeded with setuptools 69.2.0 and wheel 0.43 in https://copr.fedorainfracloud.org/coprs/churchyard/setuptools-control/package/python-moksha-hub/ This usually means this package fails to build with setuptools 74+ We plan to update setuptools to version 74 or newer in Fedora 42. This is an approved Fedora 42 Change: https://fedoraproject.org/wiki/Changes/Setuptools_74+ Please analyze the failure and fix it in rawhide. Thanks. You can use the builds from the churchyard/setuptools-74 copr for local testing. mock -r fedora-rawhide-x86_64 --addrepo 'https://download.copr.fedorainfracloud.org/results/churchyard/setuptools-74/fedora-rawhide-$basearch/' One of the most common problems is that the setup.py test command cannot be used. If that is the case here, run the tests in %check differently, e.g. via %pytest, %tox, %{python3} -m unittest, etc. If you need help, reach out to me in this bugzilla.
I was babysitting this package solely for two dependents: `fedmsg` and `module-build-service`. Both have been retired now. Though I actually missed that happening. Is it too late to have this package retired for F41 in addition to rawhide? It probably would require an FE. But it would put it nicely in line with its companions.
FWIW retirements are not actually blocked by the final freeze. I don't think that's by design, but that's my experience. It is possible or retire this in rawhide and than merge the retirement commit to the f41 branch. That said, only do that if you know it won't actually break anything else. The setuptools update this is about is targetted to Fedora 42, not Fedora 41.
Apparently, retirement on f41 is no longer possible: https://pagure.io/releng/issue/12394#comment-939162
Oh well. I guess it could still be manually retired. But it's not a big deal if it stays around for a little longer. I'll talk to QA / releng. For starters let's retire this in rawhide.
(In reply to Miro Hrončok from comment #3) > Apparently, retirement on f41 is no longer possible: > https://pagure.io/releng/issue/12394#comment-939162 Actually, retirements aren't being processed at all, atm, since the toddler is on vacation. Anyway, I retired the package in rawhide. I'll keep this bug open for now as a canary for the retirement process. But it looks like moksha-hub may see another release yet.
> I'll keep this bug open for now as a canary for the retirement process. The package was retired. There is no process that would close this bugzilla, hence closing it.
I plan to update setuptools to 74.x in rawhide this week. At that point, this package will fail to build from source if not fixed.
(In reply to Sandro from comment #5) > Anyway, I retired the package in rawhide. I'll keep this bug open for now as > a canary for the retirement process. But it looks like moksha-hub may see > another release yet. I just realized above might be confusing. I meant it will see another Fedora release (F41). With "canary of the retirement process" I was expressing some expectation of assignee change. But maybe that is only happening when orphaning. (In reply to Miro Hrončok from comment #7) > I plan to update setuptools to 74.x in rawhide this week. > > At that point, this package will fail to build from source if not fixed. How so? The package is retired in rawhide and `setuptools` won't be updated to 74.x in other branches.
> At that point, this package will fail to build from source if not fixed. I've sent this to all the bugzillas before I realized this one is retired. Ignore it here. Sorry about that.