-
-
Notifications
You must be signed in to change notification settings - Fork 13k
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
sherlock: 0-unstable-2024-06-04 -> 0-unstable-2024-06-09 #313395
base: master
Are you sure you want to change the base?
Conversation
@applePrincess Upstream merged. Not sure if your build needs builds to succeed offline or not, but in case they do (as with rpms)... |
8437d4f
to
20932f6
Compare
Indeed it needs to be offline to successfully build a package. (at least on Nixpkgs' GitHub Action and on Nixpkgs' hydra CI system) |
Result of 2 packages built:
|
20932f6
to
e84a2a4
Compare
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.
Approved.
Perhaps move it to pkgs/by-name as well?
So when ryantm bot ends up bumping this, you can merge it using nixpkgs-merge-bot, as you are the maintainer.
e84a2a4
to
8f5431e
Compare
Done |
8f5431e
to
1b31351
Compare
Moving to pkgs/by-name should be done in a seperate commit like 96f6a37. |
1b31351
to
13d520c
Compare
Result of 2 packages built:
|
Description of changes
Update to 2024-06-09
sherlock-project/sherlock@ef124ac...d678908
I am notified by the upstream as sherlock-project/sherlock/issues/2111 and sherlock-project/sherlock/issues/2127 are almost ready which will use tox and poetry instead.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.