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
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/mydumper/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/agcvkgqnz979a024p7brjgrz8cgagsh0-mydumper-0.9.5/bin/mydumper --help’ got 0 exit code
- ran ‘/nix/store/agcvkgqnz979a024p7brjgrz8cgagsh0-mydumper-0.9.5/bin/myloader --help’ got 0 exit code
- found 0.9.5 with grep in /nix/store/agcvkgqnz979a024p7brjgrz8cgagsh0-mydumper-0.9.5
- directory tree listing: https://gist.github.com/593eb6f7d15a3b04c925f61d0dc068e7
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/mypy/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.dmypy-wrapped -h’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.dmypy-wrapped --help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.dmypy-wrapped help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/dmypy -h’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/dmypy --help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/dmypy help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.mypy-wrapped -h’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.mypy-wrapped --help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.mypy-wrapped -V’ and found version 0.600
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.mypy-wrapped --version’ and found version 0.600
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/mypy -h’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/mypy --help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/mypy -V’ and found version 0.600
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/mypy --version’ and found version 0.600
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.stubgen-wrapped -h’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.stubgen-wrapped --help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.stubgen-wrapped help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/stubgen -h’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/stubgen --help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/stubgen help’ got 0 exit code
- found 0.600 with grep in /nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600
- directory tree listing: https://gist.github.com/157118da991905110fee19075e61f99b
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pdfpc/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/dvwwb2myl9351rzj9gf2p3x1731d9vnc-pdfpc-4.1.1/bin/pdfpc -h’ got 0 exit code
- ran ‘/nix/store/dvwwb2myl9351rzj9gf2p3x1731d9vnc-pdfpc-4.1.1/bin/pdfpc --help’ got 0 exit code
- ran ‘/nix/store/dvwwb2myl9351rzj9gf2p3x1731d9vnc-pdfpc-4.1.1/bin/.pdfpc-wrapped -h’ got 0 exit code
- ran ‘/nix/store/dvwwb2myl9351rzj9gf2p3x1731d9vnc-pdfpc-4.1.1/bin/.pdfpc-wrapped --help’ got 0 exit code
- found 4.1.1 with grep in /nix/store/dvwwb2myl9351rzj9gf2p3x1731d9vnc-pdfpc-4.1.1
- directory tree listing: https://gist.github.com/88ef2cda6a77852e5d7541ebd43e4fec
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pspg/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/g5s0d7h461nd55hnzp5k6v74dlfcz6dh-pspg-1.1.1/bin/pspg --help’ got 0 exit code
- ran ‘/nix/store/g5s0d7h461nd55hnzp5k6v74dlfcz6dh-pspg-1.1.1/bin/pspg -V’ and found version 1.1.1
- ran ‘/nix/store/g5s0d7h461nd55hnzp5k6v74dlfcz6dh-pspg-1.1.1/bin/pspg --version’ and found version 1.1.1
- found 1.1.1 with grep in /nix/store/g5s0d7h461nd55hnzp5k6v74dlfcz6dh-pspg-1.1.1
- directory tree listing: https://gist.github.com/ba99487fab26f86a314d4a727749a490
During patch phase, the path to the fzf binary is overwritten in the vim
plugin source. The sed expression doing this wasn't working because the fzf
code changed in this commit:
02ceae15a2
making the patch useless.
I fixed it and added a check to verify that the plugin was effecively
patched to prevent this to happen in the future.
This is not only to make users aware of the changes but also to give a
heads up to developers which are using the module. Specifically if they
rely on security.dhparams.path only.
Signed-off-by: aszlig <aszlig@nix.build>
This allows to set the default bit size for all the Diffie-Hellman
parameters defined in security.dhparams.params and it's particularly
useful so that we can set it to a very low value in tests (so it doesn't
take ages to generate).
Regardless for the use in testing, this also has an impact in production
systems if the owner wants to set all of them to a different size than
2048, they don't need to set it individually for every params that are
set.
I've added a subtest to the "dhparams" NixOS test to ensure this is
working properly.
Signed-off-by: aszlig <aszlig@nix.build>
When trying to run NSD to serve the root zone, one gets the following
error message:
error: illegal name: '.'
This is because the name of the zone is used as the derivation name for
building the zone file. However, Nix doesn't allow derivation names
starting with a period.
So whenever the zone is "." now, the file name generated is "root"
instead of ".".
I also added an assertion that makes sure the user sets
services.nsd.rootServer, otherwise NSD will fail at runtime because it
prevents serving the root zone without an explicit compile-time option.
Tested this by adding a root zone to the "nsd" NixOS VM test.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @hrdinka, @qknight
Without this change
(coercedTo str toInt int).check "foo"
would evaluate to true, even though
(coercedTo str toInt int).merge {} [{ value = "foo"; }]
will throw an error because "foo" can't be coerced to an int.
We are patching GDM to respect GDM_SESSIONS_DIR environment
variable, which we are setting in the GDM module. Previously, we
only took care of a single code path, the one that handled session
start-up; missing the one obtaining the list of sessions.
This commit patches the second code path, and also whitelists the
GDM_SESSIONS_DIR so that it can be passed to the greeter.
Fixes#34101
The `haskell-gi` build fails its doctests because of a missing
library; I'm not 100% convinced that setting it to `dontCheck` is the
right thing to do, but I don't have a better idea at the moment.
The `gi-gdkx11` build fails because, surprise, Gdk-X11 isn't found; by
looking around in my store, I found that that that library seems to
live in gtk3 these days; this override is just a stop-gap, though,
I've also submitted the change to cabal2nix that I believe will fix
the automatic generation of the package in the future.
