Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/alembic/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/7w88c8acygk8igrg5s6snyzhyf13mjbj-alembic-1.7.8-bin/bin/abcls -h’ got 0 exit code
- ran ‘/nix/store/7w88c8acygk8igrg5s6snyzhyf13mjbj-alembic-1.7.8-bin/bin/abcls --help’ got 0 exit code
- ran ‘/nix/store/7w88c8acygk8igrg5s6snyzhyf13mjbj-alembic-1.7.8-bin/bin/abcls help’ got 0 exit code
- ran ‘/nix/store/7w88c8acygk8igrg5s6snyzhyf13mjbj-alembic-1.7.8-bin/bin/abctree -h’ got 0 exit code
- ran ‘/nix/store/7w88c8acygk8igrg5s6snyzhyf13mjbj-alembic-1.7.8-bin/bin/abctree --help’ got 0 exit code
- ran ‘/nix/store/7w88c8acygk8igrg5s6snyzhyf13mjbj-alembic-1.7.8-bin/bin/abcconvert --help’ got 0 exit code
- found 1.7.8 with grep in /nix/store/7w88c8acygk8igrg5s6snyzhyf13mjbj-alembic-1.7.8-bin
- directory tree listing: https://gist.github.com/0d7ea213b28bd60d9e8cfe5bfbaa4363
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/gsm/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/99q2w40pn8n5mihvg5ar9jwlzafpp9gl-gsm-1.0.18/bin/toast -h’ got 0 exit code
- ran ‘/nix/store/99q2w40pn8n5mihvg5ar9jwlzafpp9gl-gsm-1.0.18/bin/toast help’ got 0 exit code
- ran ‘/nix/store/99q2w40pn8n5mihvg5ar9jwlzafpp9gl-gsm-1.0.18/bin/tcat -h’ got 0 exit code
- ran ‘/nix/store/99q2w40pn8n5mihvg5ar9jwlzafpp9gl-gsm-1.0.18/bin/tcat help’ got 0 exit code
- ran ‘/nix/store/99q2w40pn8n5mihvg5ar9jwlzafpp9gl-gsm-1.0.18/bin/untoast -h’ got 0 exit code
- ran ‘/nix/store/99q2w40pn8n5mihvg5ar9jwlzafpp9gl-gsm-1.0.18/bin/untoast help’ got 0 exit code
- found 1.0.18 with grep in /nix/store/99q2w40pn8n5mihvg5ar9jwlzafpp9gl-gsm-1.0.18
- directory tree listing: https://gist.github.com/af6b37d2f0a0b0757d66e91dce102967
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/libofx/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/3yhk4sd6brh5z7ksmhw9sznflcc3bl8s-libofx-0.9.13/bin/ofx2qif -h’ got 0 exit code
- ran ‘/nix/store/3yhk4sd6brh5z7ksmhw9sznflcc3bl8s-libofx-0.9.13/bin/ofx2qif --help’ got 0 exit code
- ran ‘/nix/store/3yhk4sd6brh5z7ksmhw9sznflcc3bl8s-libofx-0.9.13/bin/ofx2qif help’ got 0 exit code
- ran ‘/nix/store/3yhk4sd6brh5z7ksmhw9sznflcc3bl8s-libofx-0.9.13/bin/ofxdump -h’ got 0 exit code
- ran ‘/nix/store/3yhk4sd6brh5z7ksmhw9sznflcc3bl8s-libofx-0.9.13/bin/ofxdump --help’ got 0 exit code
- ran ‘/nix/store/3yhk4sd6brh5z7ksmhw9sznflcc3bl8s-libofx-0.9.13/bin/ofxdump help’ got 0 exit code
- ran ‘/nix/store/3yhk4sd6brh5z7ksmhw9sznflcc3bl8s-libofx-0.9.13/bin/ofxdump -V’ and found version 0.9.13
- ran ‘/nix/store/3yhk4sd6brh5z7ksmhw9sznflcc3bl8s-libofx-0.9.13/bin/ofxdump --version’ and found version 0.9.13
- found 0.9.13 with grep in /nix/store/3yhk4sd6brh5z7ksmhw9sznflcc3bl8s-libofx-0.9.13
- directory tree listing: https://gist.github.com/408d21f6a77f49bceb283d4730ff7884
This adds KMyMoney, a finance manager for KDE plus a few required
dependencies.
I ran the upstream test suite as well as the following manual tests:
* Basic startup
* Completing the wizard
* Add some test transactions
* GPG encryption
* Generation of charts and reports
* Rough check whether OFX integration lists supported financial
institutions.
* Small check of AqBanking implementation, whether accounts and users
can be configured, but didn't test actual connectivity with a
financial institution.
* Check of Weboob integration with a test PayPal backend, however also
just with a dummy account and without actually connecting to PayPal.
On top of that, the application already is being used by the person
requesting me to package this, so I'd guess it works well enough.
I'm merging this without the review from @ttuegel because it only adds
packages and doesn't change anything fundamental about the KDE
ecosystem.
The only change here is to add C++ support to "mpir", where the
maintainer (@7c6f434c) has approved the change.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/opendht/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtnode -h’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtnode --help’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtnode help’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtchat -h’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtchat --help’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtchat help’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtscanner -h’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtscanner --help’ got 0 exit code
- found 1.7.1 with grep in /nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1
- directory tree listing: https://gist.github.com/a3f2bc9f76c4720e3fec78139e60c160
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/umockdev/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-run -h’ got 0 exit code
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-run --help’ got 0 exit code
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-run --version’ and found version 0.11.3
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-record -h’ got 0 exit code
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-record --help’ got 0 exit code
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-record --version’ and found version 0.11.3
- found 0.11.3 with grep in /nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3
- directory tree listing: https://gist.github.com/3dcf7f53d51ca4a9c739e567456cb16f
"platforms.gnu" has been linux-only since at least 17.03:
$ nix eval -f channel:nixos-17.03 lib.platforms.gnu
[ "i686-linux" "x86_64-linux" "armv5tel-linux" "armv6l-linux" "armv7l-linux" "aarch64-linux" "mips64el-linux" ]
Unlike platforms.linux, platforms.gnu indicates "must use glibc"
which for the most part is not intended.
Replacing platforms.gnu with platforms.linux would be the same "today"
but let's err on preserving existing behavior and be optimistic
about platforms these packages work on.
I still feel weird about doing this because it seems a little hacky
but this was requested by @Mic92 and seems understandable to not want
to mix up libressl outputs with netcat stuff.
@7c6f434c wrote in [1]:
Maybe copy-paste the upstream "Alkimia is the infrastructure for
common storage and business logic that will be used by all financial
applications in KDE. The target is to share financial related
information over application bounderies." as longDescription for
Alkimia? The current description makes me want to look up the
homepage to find out what it actually is (then I do, and despair).
[1]: https://github.com/NixOS/nixpkgs/pull/39647#issuecomment-385169261
Signed-off-by: aszlig <aszlig@nix.build>
This is used by KMyMoney and also the reason why I needed to add C++
support to MPIR in the parent commit.
The reason why I didn't add myself as a maintainer is because I'm not
personally using KMyMoney and thus Alkimia.
Signed-off-by: aszlig <aszlig@nix.build>
This is one of the requirements of KMyMoney and packaging is quite
straightforward with no unexpected traps.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @ttuegel
This is needed by Alkimia which I'm going to package soon as part of
KMyMoney.
I enabled this by default, because it doesn't increase the closure size
a whole lot (only around 150 KiB):
$ nix-store -q --size /nix/store/...old...-mpir-3.0.0
1223248
$ nix-store -q --size /nix/store/...new...-mpir-3.0.0
1377136
Introducing an option for enabling/disabling this is not worth it,
because it doesn't conflict with anything and the size increase is the
only drawback and we can still make it configurable if we want someday.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @7c6f434c
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/fastjet/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/y8mkgp5xlcfik6fb5r1dzb93n6xm1f9r-fastjet-3.3.1/bin/fastjet-config -h’ got 0 exit code
- ran ‘/nix/store/y8mkgp5xlcfik6fb5r1dzb93n6xm1f9r-fastjet-3.3.1/bin/fastjet-config --help’ got 0 exit code
- ran ‘/nix/store/y8mkgp5xlcfik6fb5r1dzb93n6xm1f9r-fastjet-3.3.1/bin/fastjet-config --version’ and found version 3.3.1
- found 3.3.1 with grep in /nix/store/y8mkgp5xlcfik6fb5r1dzb93n6xm1f9r-fastjet-3.3.1
- directory tree listing: https://gist.github.com/aa455f4d0802d2b2b76678ecccfe3eab
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
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/libwps/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wps2html -v’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wps2raw -v’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wps2raw --version’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wps2text -v’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wks2csv -v’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wks2raw -v’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wks2raw --version’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wks2text -v’ and found version 0.4.9
- found 0.4.9 with grep in /nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9
- directory tree listing: https://gist.github.com/a3fdf5973402ddf0aa6d1a0ecd058d41
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
(cherry picked from commit ba52ae5048)
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
