Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/freeradius/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radcrypt help’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/smbencrypt -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/smbencrypt --help’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/smbencrypt help’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radsniff -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radlast -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radlast --help’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radzap -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radiusd -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radmin -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radmin --help’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/rc.radiusd -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/rc.radiusd --help’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/rc.radiusd help’ got 0 exit code
- found 3.0.17 with grep in /nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17
- directory tree listing: https://gist.github.com/0674f9c9bf80af589d86399e508dc604
before #ffe86fe949199ebe0e5610c74230edf60a05ae8d
perlPackages.ModuleBuildWithXSpp and perlPackages.ExtUtilsTypemapsDefault
seem to have been implicitly provided by perlPackages.MathClipper
Since the script running is a failure condition, we should fail the
build properly, not leaving it up to the missing output to determine
that the build went wrong. This should partly address #38952 — nix
build will print out the build log on non-zero exits.
