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
goffice: 0.10.47 -> 0.10.48 #96332
goffice: 0.10.47 -> 0.10.48 #96332
Conversation
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.
Changes look okay: http://ftp.gnome.org/pub/GNOME/sources/goffice/0.10/goffice-0.10.48.news
breaks gnumeric
|
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.
Changes to gnumeric look fine too https://ftp.gnome.org/pub/GNOME/sources/gnumeric/1.12/gnumeric-1.12.48.news |
@jtojnar since they shared the same patch version, I assumed they were developed in tandom |
Yeah, that seems to be the case, would not expect it to break if they do not match, though. I just recently started tagging PRs with |
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for goffice is: "A Glib/GTK set of document centric objects and utilities"
meta.homepage for goffice is: ""
meta.changelog for goffice is: ""
Updates performed
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
The tests defined in
passthru.tests
, if any, passed0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 0.10.48 with grep in /nix/store/3wcjbnz2al4x6x6pzrff3dl0h323i077-goffice-0.10.48
directory tree listing: https://gist.github.com/23d86646c9c71d86f47c2410d3814e7d
du listing: https://gist.github.com/00a9ad1e9be0245c8fae6ecc85262101
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.
Result of
nixpkgs-review
11 package failed to build:
3 packages built:
Maintainer pings