Latest upstream release: 1.8.0 Current version/release in rawhide: 1.7.0-2.fc36 URL: https://pypi.org/project/userpath/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/37501/
The latest version of this package depends on a new build backend created by the upstream developer for his projects userpath and hatch. I've asked about the motivation in https://github.com/ofek/hatch/issues/120 Only hatch and pipx depend on python3-userpath and I've orphaned hatch for the mentioned reason. @code you maintain pipx, do you want to take also this package?
(In reply to Lumír Balhar from comment #1) > The latest version of this package depends on a new build backend created by > the upstream developer for his projects userpath and hatch. I've asked about > the motivation in https://github.com/ofek/hatch/issues/120 > > Only hatch and pipx depend on python3-userpath and I've orphaned hatch for > the mentioned reason. @code you maintain pipx, do you > want to take also this package? Maybe! Thanks for pinging me. As soon as I have a chance, I will investigate what it would take to package and use the hatchling build system, and whether this is viable in Fedora. If it looks like a huge pain, orphaning pipx too is a possibility. I’ll report back and let you know what I want to do. I’m intentionally not clearing the NEEDINFO.
Thanks for the quick response. We also have one from the upstream maintainer in the issue mentioned before. He mentions that hatchling is something like poetry-core or flit-core and hatch is like poetry or flit itself. Unfortunately, the two projects are mixed in the one repository and have also mixed tests which might be practical from developer's perspective but not so much from our perspective.
I’m first investigating whether I can correctly build a pre-release of hatch 1.0 with hatchling[1]. If so, then I’ll move on to investigating userpath. https://bugzilla.redhat.com/show_bug.cgi?id=2035978#c36
While I’m still slowly working through hatch’s tests, userpath only requires hatchling, and I’m able to build userpath 1.8.0 with hatchling in a COPR: https://src.fedoraproject.org/rpms/python-userpath/pull-request/5 https://copr.fedorainfracloud.org/coprs/music/hatchling/builds/ I’m therefore happy to start maintaining python-userpath. It would be helpful if you could review the two new dependencies: https://bugzilla.redhat.com/show_bug.cgi?id=2050889 https://bugzilla.redhat.com/show_bug.cgi?id=2050876 I’m also happy to have you as a co-maintainer in any of these packages if you still have an interest in them.
If nobody takes those reviews first, I'll try to do them tomorrow or on Monday. I'm sorry for the delay.
(In reply to Lumír Balhar from comment #6) > If nobody takes those reviews first, I'll try to do them tomorrow or on > Monday. I'm sorry for the delay. That will be perfectly fine, and much appreciated. There is not any real hurry here.
Thank you for the reviews! With hatchling packaged, https://src.fedoraproject.org/rpms/python-userpath/pull-request/5 is ready to merge. F36 can safely be updated as well: except for dropping Python 3.6, this update is compatible with userpath-1.7, and neither of the dependent packages (hatch, pipx) has an upper bound on userpath version. Upstream indicates hatch 1.x implicitly wants pip >= 21.3 [1]. If that applies to hatchling as well (I’ve asked for clarification[2]), then F34/F35 and EPEL9 won’t see userpath 1.8 either. ---- Feel free to choose from: • Give python-userpath to me; I will merge and build, and will happily keep you on as co-maintainer if you like. • Stay primary maintainer on python-userpath. Review PR and merge once happy. Add me as co-maintainer if you like. [1] https://github.com/ofek/hatch/issues/120#issuecomment-1038185636 [2] https://github.com/ofek/hatch/issues/120#issuecomment-1048087686
Based on [1], I can backport python-hatchling to older releases. However, the only documented user-visible change from 1.7.0 to 1.8.0 is Windows-specific, so it’s probably still not worth updating F35. It opens the possibility of supporting at least EPEL9, though. [1] https://github.com/ofek/hatch/issues/120#issuecomment-1048105953
(In reply to Ben Beasley from comment #9) > Based on [1], I can backport python-hatchling to older releases. However, > the only documented user-visible change from 1.7.0 to 1.8.0 is > Windows-specific, so it’s probably still not worth updating F35. It opens > the possibility of supporting at least EPEL9, though. > > [1] https://github.com/ofek/hatch/issues/120#issuecomment-1048105953 I take it all back; other dependencies are too old in everything but F36+.
You are the main admin of the project now. I can stay as a co-maintainer and help you anytime. Thank you very much for the effort you put into this. The PR looks good to me so feel free to merge it and ship the update.
Thanks!
FEDORA-2022-6eaa343241 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6eaa343241
FEDORA-2022-6eaa343241 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-ce062a4ca3 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ce062a4ca3
FEDORA-2022-ce062a4ca3 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-ce062a4ca3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ce062a4ca3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-ce062a4ca3 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-0a85e1e3cc has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0a85e1e3cc
FEDORA-EPEL-2022-9bef2f2767 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-9bef2f2767
FEDORA-EPEL-2022-9bef2f2767 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-9bef2f2767 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-0a85e1e3cc has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-0a85e1e3cc` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0a85e1e3cc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-0a85e1e3cc has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-9bef2f2767 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.