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
gjs: 1.66.2 -> 1.68.0 #117323
gjs: 1.66.2 -> 1.68.0 #117323
Conversation
Result of 5 packages marked as broken and skipped:
3 packages failed to build:5 packages skipped due to time constraints:
55 packages built successfully:
1 suggestion:
Note that build failures may predate this PR, and could be nondeterministic or hardware dependent. Result of 5 packages marked as broken and skipped:
1 package failed to build:8 packages skipped due to time constraints:
60 packages built successfully:
1 suggestion:
Note that build failures may predate this PR, and could be nondeterministic or hardware dependent. |
Part of #117081 |
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for gjs is: "JavaScript bindings for GNOME"
meta.homepage for gjs is: "https://gitlab.gnome.org/GNOME/gjs/blob/master/doc/Home.md"
meta.changelog for gjs is: ""
Updates performed
To inspect upstream changes
Impact
Checks done (click to expand)
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-users
list or you can usesudo
since root is effectively trusted.Or, build yourself:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out
Maintainer pings
cc @hedning @jtojnar @worldofpeace @dasj19 @maxeaubrey for testing.