-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
wayshot 1.3.0 -> 1.3.1 #302017
wayshot 1.3.0 -> 1.3.1 #302017
Conversation
pkgs/tools/misc/wayshot/default.nix
Outdated
cargoHash = "sha256-Hfgr+wWC5zUdHhFMwOBt57h2r94OpdJ1MQpckhYgKQQ="; | ||
cargoHash = "sha256-K7E4od+YGb9PgmIzWSQh+sIU8kaJviftNhFpUD9vOIc="; | ||
|
||
# added due to faulty tests in latest version |
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 there an upstream bug report?
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.
Did not find any report in source related to this issue.
In developers makefile they do not run cargo test
, just cargo build
. So ignoring checks should not be an issue as they passed it to thier release version.
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.
The upstream developers may appreciate a bug report about this, then.
It would also give us something to link to, so that we know what to do about disabling tests in the future. (E.g. if upstream fixes it, we can remove it; if upstream decides they don't care about tests, we will now know that.)
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.
Opened issue. What about pull request to nixpkgs? Should just wait for the upstream developers' response to the issue or do something else?
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.
What about pull request to nixpkgs? Should just wait for the upstream developers' response to the issue or do something else?
No need to wait, just add a link to the issue in a comment, that explains why tests are disabled.
We can fetchpatch the fix |
If you mean fetchpatch from commit. That won't be an option as commit has more fixes than version 1.3.1 needs. |
Result of 1 package failed to build:
|
Result of 1 package built:
|
Just ran |
@ofborg build wayshot |
Looks like now it shows different cargoHash from what was before. Please try again, I've changed to the one from ofborg logs. |
@ofborg build wayshot |
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.
Package looks good functionality-wise.
Please squash your commits together into the following two chunks:
maintainers: add id3v1669
wayshot: 1.3.0 -> 1.3.1
Also, you can pass arguments to cargo test
via checkFlags = [ ... ];
. Maybe that can be used to skip only the tests that are actually broken?
Done. |
Description of changes
https://github.com/waycrate/wayshot/releases/tag/1.3.1
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/
)Notes
Release version of package has faulty tests with
cargo test
but runs as intended, sodoCheck = false;
was added.Add a 👍 reaction to pull requests you find important.