New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pythonPackages.pelican: Add patch from upstream for failing tests with… #87600
Conversation
… updated pygments version
A slight improvement would be to get the patch via
But already a big thanks for tracking this down. ;) |
Patch also contains fixes for some other files, e.g. in custom_locale, which we are removing from tarball. But I'll use it for future, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commit message has a spelling mistake 'pythonPackaes.pelican' instead of 'pythonPackages.pelican'. Besides that everything looks good. :) Tested with nix-review.
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
you can also pass |
@@ -48,6 +48,11 @@ buildPythonPackage rec { | |||
nose | |||
]; | |||
|
|||
patches = [ | |||
# fix for updated pygments version. Remove when updating to new version. | |||
./pygments-tests.patch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this taken from a pull request? If so it would be nice to use fetchpatch
on the commit url instead of adding the patch to nixpkgs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just saw the other comments above.
A new pelican version has been released recently, but for nixos-20.03 this PR is still relevant. @dashmoho would it be ok if I created a backport PR for your patches? |
as long as the new version doesn't introduce any regressions. It's fine to backport package updates (generally patch and minor versions, if the package follows semver) |
How do we handle this if upstream has regressions but the package was broken for the whole the release was current? In this case the latest Pelican releases drops support for Python 2.7, but never worked for nixos-20.03. Should we still backport the patch or upgrade to the latest Pelican release? |
I would say just make the changes to master, if someone opens an issue that backporting the change would be worthwhile, then we can look into it. |
Patch does not cleanly apply anymore when doing nixpkgs-review. |
Result of 2 packages failed to build:
|
Result of 2 packages failed to build:
|
superseded by #112137 |
… updated pygments version
Motivation for this change
This fixes issue with failing tests (#83513).
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)