OpenSSL is needed for gct-tool and libgpgerror for RSA key utilities
(src/crypt3/cryptkeyrsa.c).
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @goibhniu
So far we used only the defaults, which are gtk2 and qt5. However
nowadays most applications have already switched to Qt 5 and Gtk 3, so
let's aim for that instead.
The reason Gtk 2 is still there is because GnuCash in nixpkgs is using
the Gtk 2 interface, so we can drop it as soon as a newer GnuCash has
landed in nixpkgs.
Right now the only package that depends on this is GnuCash (and
aqbanking of course), so I've tested this by not only building
gwenhywfar and aqbanking but also GnuCash. I did however not test
whether HBCI functionality works, only whether GnuCash starts up.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @goibhniu, @peti, @domenkozar
This is to make sure that we don't get a disparity between the version
in sources.nix and the version in the package expression and it's mostly
to get the package expression in par with aqbanking and gwenhywfar.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @goibhniu
Upstream changes in 5.7.8:
* Update bank information files for German banks because the format of
ZKA files has changed in the meantime.
Upstream release notes in German:
https://www.aquamaniac.de/sites/download/releasenote.php?package=03&release=217
Upstream changes in 5.7.7:
* Fix of manually adding new HBCI accounts (for example using
KMyMoney).
* Fix wrong truncation of account numbers in some turnovers of the
SWIFT parser.
* Simplified code for inserting new account data while fetching HBCI
accounts.
* Update information for German banks.
Upstream release notes in German:
https://www.aquamaniac.de/sites/download/releasenote.php?package=03&release=216
As with the gwenhywfar update, the updater script (update.sh) actually
didn't get the right file to download, so I temporarily modified it to
download file number 2 because file number 1 is the GPG signature. The
reason why I didn't fix the updater is because the upstream site will
have different URLs in the next upcoming version, so our updater is
basically end-of-life for now.
I also changed the package expression to use the version from
sources.nix instead of a hardcoded value.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @goibhniu
Upstream changes in 4.20.0:
* Update bank information files for German banks because the format of
ZKA files has changed in the meantime.
Upstream release notes in German:
https://www.aquamaniac.de/sites/download/releasenote.php?package=01&release=208
Upstream changes in 4.19.0:
* Add frontend for GTK3.
Upstream release notes in German:
https://www.aquamaniac.de/sites/download/releasenote.php?package=01&release=207
Upstream changes in 4.18.0:
* Show hashes for MD5, SHA1 and SHA512 in SSL certificates because
some bank servers display different hashing variants.
* Let GNUTLS handle the localisation of TrustStore certificates.
Upstream release notes in German:
https://www.aquamaniac.de/sites/download/releasenote.php?package=01&release=206
The updater script (update.sh) actually didn't get the right file to
download, so I temporarily modified it to download file number 2 because
file number 1 is the GPG signature. The reason why I didn't fix the
updater is because the upstream site will have different URLs in the
next upcoming version, so our updater is basically end-of-life for now.
I also changed the package expression to use the version from
sources.nix instead of a hardcoded value.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @goibhniu
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/cgal/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/7py5j9ixfljnic4dr3ij97msnj0wahv6-cgal-4.12/bin/cgal_create_CMakeLists -h’ got 0 exit code
- ran ‘/nix/store/7py5j9ixfljnic4dr3ij97msnj0wahv6-cgal-4.12/bin/cgal_create_CMakeLists help’ got 0 exit code
- ran ‘/nix/store/7py5j9ixfljnic4dr3ij97msnj0wahv6-cgal-4.12/bin/cgal_create_cmake_script -h’ got 0 exit code
- ran ‘/nix/store/7py5j9ixfljnic4dr3ij97msnj0wahv6-cgal-4.12/bin/cgal_create_cmake_script --help’ got 0 exit code
- found 4.12 with grep in /nix/store/7py5j9ixfljnic4dr3ij97msnj0wahv6-cgal-4.12
- directory tree listing: https://gist.github.com/35067880611978f76a8e3f3adac7f12a
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/jruby/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0/bin/jruby -h’ got 0 exit code
- ran ‘/nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0/bin/jruby --help’ got 0 exit code
- ran ‘/nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0/bin/jruby.bash -h’ got 0 exit code
- ran ‘/nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0/bin/jruby.bash --help’ got 0 exit code
- ran ‘/nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0/bin/ruby -h’ got 0 exit code
- ran ‘/nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0/bin/ruby --help’ got 0 exit code
- found 9.1.17.0 with grep in /nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0
- directory tree listing: https://gist.github.com/20468ca63db765e0d42a1c93191f0901
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/libmwaw/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwawFile -v’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwawZip -v’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwaw2csv -v’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwaw2html -v’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwaw2raw -v’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwaw2raw --version’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwaw2svg -v’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwaw2text -v’ and found version 0.3.14
- found 0.3.14 with grep in /nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14
- directory tree listing: https://gist.github.com/e6bf3abafc8b9634a51796eb8969b268
Yeah yeah, I want parallel glob expansion but you get what I mean.
These two packages like getting upgraded together so to minimize
incompatibilities I'm upgrading them both in the same commit.
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.
The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:
```
ISA: ARMv8 {-A, -R, -M}
/ \
Mode: Aarch32 Aarch64
| / \
Encoding: A64 A32 T32
```
At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.
The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.
[1]: https://developer.arm.com/products/architecture/a-profile
On GNU/Linux the build references these files, so let's fetch them from
the Chromium repository. I haven't checked whether they are heavily
patched or whether we can use the version from LLVM, but when looking at
the changes, they do seem to divert a bit from upstream LLVM.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @matthewbauer, @stesie
The tarball from upstream seems to be generated on the fly, so the
output is not deterministic and using fetchzip makes this more reliable
as we have a recursively hashed output path without any of the
non-determinisms in tarballs.
Unfortunately, the build still fails on NixOS systems, because we need a
few more stuff in the build tree.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @matthewbauer, @stesie
aszlig