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
Gstreamer: 1.14.0 -> 1.14.2 #45776
Gstreamer: 1.14.0 -> 1.14.2 #45776
Conversation
@@ -5,7 +5,7 @@ | |||
|
|||
stdenv.mkDerivation rec { | |||
name = "gst-vaapi-${version}"; | |||
version = "1.14.0"; | |||
version = "1.14.2"; |
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 hash also needs an update.
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.
Thanks for finding this mistake. Solved :)
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.
I just tried to build gst_all_1
... all the rest had succeeded.
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.
But now it works?
@GrahamcOfBorg build gst_all_1 |
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: gst_all_1 Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: gst_all_1 Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: gst_all_1 Partial log (click to expand)
|
@vcunat will you merge this? |
@matthewbauer @ttuegel someone of you wants to merge this? |
Should go in staging i think. |
@matthewbauer is |
Yep that should work |
Unless it's a security fix, changes should go to staging and not directly staging-next. |
Yes, things are merged to staging instead, at least generally. |
Is there any documentation, which pull request should end in which branch? I find it very confusing. |
There's an RFC only so far: NixOS/rfcs#26 but that part about where to merge seems to have worked well in the past few months that we're trying the workflow. EDIT: except for the important point that we might change the branch name(s) :-) |
Okay, ty :) |
Motivation for this change
I could not run
nox-review wip
, as the resultingnix-build
used more than 20GB of RAM...Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)