Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/elisa/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/x9jdlmln6ywpx5c2qh7vmfdn93djnxk3-elisa-0.2.0/bin/elisa had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/x9jdlmln6ywpx5c2qh7vmfdn93djnxk3-elisa-0.2.0/bin/.elisa-wrapped had a zero exit code or showed the expected version
- 0 of 2 passed binary check by having a zero exit code.
- 0 of 2 passed binary check by having the new version present in output.
- found 0.2.0 with grep in /nix/store/x9jdlmln6ywpx5c2qh7vmfdn93djnxk3-elisa-0.2.0
- directory tree listing: https://gist.github.com/6a824e1b1cbc4a270bb07962f2026bfb
- du listing: https://gist.github.com/ac472eaf8c7eb82ee6d9c2283ab33ca9
Since 772eef9168, Boost by default doesn't
support Python anymore, so we need to override it with Python support.
Signed-off-by: aszlig <aszlig@nix.build>
Since 772eef9168 Boost no longer has
Python support enabled by default, so depending on whether Ledger has
Python support built in we also use either Boost with Python support or
without.
Tested building with and without Python support and both builds now
succeed.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @the-kenny, @jwiegley
Removes the version pinning for arb and pynac by backporting the
upstream (sage) package upgrades. This necessitates a new patch for arb,
which was however already proposed and accepted upstream.
It's a really small fix that even could have been done via sed, but I'm
using the upstream patch instead so that once a new upstream release
comes along we don't forget to drop the patch.
The patch is from the upstream commit at:
https://cgit.kde.org/kmymoney.git/commit/?id=e5198a902996b27bf9abde0ad24af82d55ab5dc1
Signed-off-by: aszlig <aszlig@nix.build>
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/chirp-daily/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/gfgi7c2ps023ga27vx6s38y4gkgx1c54-chirp-daily-20180614/bin/.chirpw-wrapped had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/gfgi7c2ps023ga27vx6s38y4gkgx1c54-chirp-daily-20180614/bin/chirpw had a zero exit code or showed the expected version
- 0 of 2 passed binary check by having a zero exit code.
- 0 of 2 passed binary check by having the new version present in output.
- found 20180614 with grep in /nix/store/gfgi7c2ps023ga27vx6s38y4gkgx1c54-chirp-daily-20180614
- directory tree listing: https://gist.github.com/5a739e8fa0584360afb3f692d19e3771
- du listing: https://gist.github.com/e530a387cd61ae6e0b944b372041bd3d
This conflicts with -Werror=format-security and the build doesn't have
any format security problems, so -Wno-format IMHO shouldn't be there in
the first place.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @domenkozar