Latest upstream release: 2020.11.4 Current version/release in rawhide: 2020.8.13-1.fc34 URL: https://docs.pipenv.org/ 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/16437/
Latest upstream release: 2020.11.15 Current version/release in rawhide: 2020.8.13-1.fc34 URL: https://docs.pipenv.org/ 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/16437/
All blockers are solved.
PR: https://src.fedoraproject.org/rpms/pipenv/pull-request/31
I'd like to get the latest pipenv available on F33 & F34. I am willing to package it, but am not sure on where to start. It seems a lot of the work has been done already, without being familiar with the Fedora tools & processes I'm finding it hard to figure out where to focus! I believe I've my account(s) setup as required, so am eager to contribute something!
The latest version is available in rawhide. We can probably create an update for F34 which will become available after the release but I'm not sure how good the idea is to create an update for the already released version? Are there any backward incompatibilities between 2020.8.13 and 2020.11.15? Could you please check it?
I've a bit to read up on regarding the policy for packaging in Fedora Linux - there aren't enough hours in the day to get to everything I want to! There's no guarantee that none of these will break certain projects, but anecdotally; I've used all released versions of pipenv, along with some unreleased versions (Using pip to install, and not on Fedora Linux). I've experienced no issues both in either personal or work projects. Previously the project was feared to have been abandoned, so stability has been the biggest focus of the project. It's mainly been bug fixes, but I've listed out the features & Improvements since 2020.8.13. v2020.11.15 - Support expanding environment variables in requirement URLs. _ - Show warning message when a dependency is skipped in locking due to the mismatch of its markers. _ 2020.11.4 - Add a new command pipenv scripts to display shortcuts from Pipfile. _ - Retrieve package file hash from URL to accelerate the locking process. _ - Add the missing --system option to pipenv sync. _ - Add a new option pair --header/--no-header to pipenv lock command, which adds a header to the generated requirements.txt _ Taken from https://github.com/pypa/pipenv/releases Would adding these updates to COPR be a good option as a first step to getting the latest pipenv onto F33 or F34? I'm happy to take direction on what to do here. And with some help would be able to update in whatever approach is deemed best. I've done a decent bit of packaging for CentOS at work, but this would be my first effort packaging something for Fedora.
It's not that much about the work it needs to update the package in F33 and F34 because it means merge the rawhide branch to the versioned branches, build the package and do some testing. But the final decision is up to the maintainers whether they consider it as a good idea and not a threat to stability. If they decide to not update the package, you can still install it from pip (to a virtual environment) or you can do your own rebuild in COPR.
I've run the following commands: $ copr create @python/pipenv-rawhide --repo='http://kojipkgs.fedoraproject.org/repos/f$releasever-build/latest/$basearch/' --chroot fedora-32-x86_64 --chroot fedora-33-x86_64 --chroot fedora-34-x86_64 New project was successfully created. $ copr add-package-distgit @python/pipenv-rawhide --name pipenv --webhook-rebuild on Create or edit operation was successful. $ copr build-package @python/pipenv-rawhide --nowait --name pipenv Build was added to pipenv-rawhide. Created builds: 2074470 This copr will (auto)rebuild the rawhide version of pipenv for older Fedoras: https://copr.fedorainfracloud.org/coprs/g/python/pipenv-rawhide/ I don't know yet if it succeeds, if it will be installable and if it will function properly, but it is a start. If it works, I'll add some description to the Copr.
It doesn't work: No matching package to install: 'python3dist(attrs) >= 20.3' No matching package to install: 'python3dist(colorama) >= 0.4.4' No matching package to install: 'python3dist(first) >= 2.0.2' No matching package to install: 'python3dist(iso8601) >= 0.1.13' No matching package to install: 'python3dist(parse) >= 1.18' No matching package to install: 'python3dist(python-dotenv) >= 0.15' No matching package to install: 'python3dist(requests) >= 2.25' No matching package to install: 'python3dist(semver) >= 2.13'
That's reflecting my concerns :(
So the next step would be to adapt the spec file for Fedora 33 by lowering some of the bounds (if it works with the older versions) or re-bundling (if it doesn't work with the older versions). The spec file is: https://src.fedoraproject.org/rpms/pipenv/blob/rawhide/f/pipenv.spec
I can take a look at this. Is there a policy on how to first attempt this? Lowering the versions of these dependencies seems like an easier first step, though may introduce issues.
No policy, except "make it work". I'd try lowering first and see if the tests pass and if pipenv functions properly.
FEDORA-2021-93f928dc0d has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-93f928dc0d
The build for Fedora 34 is ready. Since it's a leaf package, it should be OK to go in even during beta. I've smoke-tested it and I'll use it myself from now on :) For Fedora 33, a Copr repo would be better. It would be better to move the discussion to the mailing list, python-devel.org, as I'd like to close this bug after the update.
FEDORA-2021-93f928dc0d has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-93f928dc0d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-93f928dc0d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-93f928dc0d has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.