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
cpuset: 1.5.8 -> 1.6 #107512
cpuset: 1.5.8 -> 1.6 #107512
Conversation
/marvin opt-in |
Hi! I'm an experimental bot. My goal is to guide this PR through its stages, hopefully ending with a merge. You can read up on the usage here. |
@glittershark please review. |
Result of 1 package built:
|
|
||
propagatedBuildInputs = [ ]; | ||
propagatedBuildInputs = with pythonPackages; [ | ||
configparser |
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.
Not necessary for Python 3, but if we want this package to continue to work with Python 2 this needs to be included.
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.
This package is usually used as a CLI tool so I don't think it's hugely important to keep the Python 2 support (especially that we're not testing it?), although I don't see much harm in it either.
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.
Yeah, me too, I am ok either way.
|
||
propagatedBuildInputs = [ ]; | ||
propagatedBuildInputs = with pythonPackages; [ | ||
configparser |
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.
This package is usually used as a CLI tool so I don't think it's hugely important to keep the Python 2 support (especially that we're not testing it?), although I don't see much harm in it either.
Result of 1 package built:
|
Result of 1 package built:
|
]; | ||
|
||
# https://github.com/lpechacek/cpuset/pull/36 | ||
patches = fetchpatch { |
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.
isn't patches
usually a list?
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.
If I put fetchpatch
inside a list it returns an error.
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.
ah, ok then.
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.
Please use this style:
patches = [ |
Switch from wykurz to lpechacek fork, so we can use Python 3 instead of Python 2. However, Python 2 should still works. Also, fix this issue since it is easy: SUSE/cpuset#38
Result of 1 package built:
|
tested the result, appears to work |
/status needs_merger |
Result of 1 package built:
|
Motivation for this change
Switch from wykurz to lpechacek fork, so we can use Python 3 instead of Python 2. However, Python 2 should still works.
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)