-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
exiv2: 0.26.x -> 0.27.x #50496
exiv2: 0.26.x -> 0.27.x #50496
Conversation
@GrahamcOfBorg build exiv2 |
Success on aarch64-linux (full log) Attempted: exiv2 Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: exiv2 Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: exiv2 Partial log (click to expand)
|
@GrahamcOfBorg build python36Packages.py3exiv2 gegl_0_4 |
Failure on x86_64-darwin (full log) Attempted: python36Packages.py3exiv2, gegl_0_4 Partial log (click to expand)
|
Failure on x86_64-linux (full log) Attempted: python36Packages.py3exiv2, gegl_0_4 Partial log (click to expand)
|
Failure on aarch64-linux (full log) Attempted: python36Packages.py3exiv2, gegl_0_4 Partial log (click to expand)
|
They've released RC2 already. There are some new Coverity fixes in the log, so that's possibly also relevant for security. |
The new build system also installs very many new executables. Maybe there were some other caveats; I've forgotten since the last time I've tried pre-0.27. |
@periklis I'd rather put this update on hold until 0.27 has been released. |
Expected dates have been announced:
But I guess RC3 should be 07 December, given that the announcement was on 16 November :-) |
Mainly run test and remove additionally installed stuff.
Well, the real problem with 0.27 is that a large fraction of direct dependents won't build with it (yet). EDIT: too many for me to fix anytime soon and way too intrusive for 18.09 anyway. |
The bump includes all the patches we had and adds some more, e.g. for CVE-2017-1000127. I don't think all CVEs get fixed by that, but 0.27 would currently break too many packages; /cc NixOS#50496.
The bump includes all the patches we had and adds some more, e.g. for CVE-2017-1000127. I don't think all CVEs get fixed by that, but 0.27 would currently break too many packages; /cc #50496. (cherry picked from commit bf7d1b5)
gexiv2 0.10.10 supporting exiv2 0.27 was released https://gitlab.gnome.org/GNOME/gexiv2/blob/gexiv2-0.10.10/NEWS |
Let me link ghtumb patch, too. ATM it still seems early to update, but feel free to try finding/producing patches for most of our packages. |
@@ -12,6 +14,14 @@ stdenv.mkDerivation rec { | |||
sha256 = "1vf0zv92p9hybdhn7zx53h3ia53ph97a21xz8rfk877xlr5261l8"; | |||
}; | |||
|
|||
patches = [ | |||
(fetchpatch { # should be included in the following release |
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.
gexiv2 0.10.10 is in master now.
I happened to notice 0.27.1 was release recently: https://www.exiv2.org/whatsnew.html |
Motivation for this change
fix for #50369
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)