Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/sysstat/versions.
These checks were done:
- built on NixOS
- /nix/store/gz1jvhynz6ixwh9z33kw5fi603nq090q-sysstat-11.7.4/bin/sar passed the binary check.
- /nix/store/gz1jvhynz6ixwh9z33kw5fi603nq090q-sysstat-11.7.4/bin/sadf passed the binary check.
- /nix/store/gz1jvhynz6ixwh9z33kw5fi603nq090q-sysstat-11.7.4/bin/iostat passed the binary check.
- /nix/store/gz1jvhynz6ixwh9z33kw5fi603nq090q-sysstat-11.7.4/bin/tapestat passed the binary check.
- /nix/store/gz1jvhynz6ixwh9z33kw5fi603nq090q-sysstat-11.7.4/bin/mpstat passed the binary check.
- /nix/store/gz1jvhynz6ixwh9z33kw5fi603nq090q-sysstat-11.7.4/bin/pidstat passed the binary check.
- /nix/store/gz1jvhynz6ixwh9z33kw5fi603nq090q-sysstat-11.7.4/bin/cifsiostat passed the binary check.
- 7 of 7 passed binary check by having a zero exit code.
- 0 of 7 passed binary check by having the new version present in output.
- found 11.7.4 with grep in /nix/store/gz1jvhynz6ixwh9z33kw5fi603nq090q-sysstat-11.7.4
- directory tree listing: https://gist.github.com/099df05f7cbb5510144a7b1741ff0fda
- du listing: https://gist.github.com/21956b2e9d623a7923391b59af578f7e
Instead of explicitly depending on libelf, use
kernel.moduleBuildDependencies which was introduced in 1e77d0b975
("kernel 4.14 require libelf to compile modules.").
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/lxc/versions.
These checks were done:
- built on NixOS
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-attach passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-autostart passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-cgroup passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-checkpoint passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-copy passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-config passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-console passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-create passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-destroy passed the binary check.
- Warning: no invocation of /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-device had a zero exit code or showed the expected version
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-execute passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-freeze passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-info passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-ls passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-monitor passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-snapshot passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-start passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-stop passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-top passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-unfreeze passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-unshare passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-usernsexec passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-wait passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-checkconfig passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/lxc-update-config passed the binary check.
- /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1/bin/init.lxc passed the binary check.
- 25 of 26 passed binary check by having a zero exit code.
- 20 of 26 passed binary check by having the new version present in output.
- found 3.0.1 with grep in /nix/store/x6894sbycq6n355c9nflvf51c5wl5b4a-lxc-3.0.1
- directory tree listing: https://gist.github.com/99239516868c9c02f18f88c0399aa8f1
- du listing: https://gist.github.com/60d07821cb31145506d2cba9745bbe7d
Fixes this:
$ nix-build -A linuxPackages.lttng-modules
[...]
/nix/store/...-linux-4.14.48-dev/lib/modules/4.14.48/source/Makefile:948: \
*** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfu
(Linux 4.16+ has other issues, so mark as broken.)
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/bluez/versions.
These checks were done:
- built on NixOS
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/bluetoothctl passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/btmon passed the binary check.
- Warning: no invocation of /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/rctest had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/l2test had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/l2ping had a zero exit code or showed the expected version
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/bccmd passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/bluemoon passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/hex2hcd passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/mpris-proxy passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/btattach passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/bdaddr passed the binary check.
- Warning: no invocation of /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/avinfo had a zero exit code or showed the expected version
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/avtest passed the binary check.
- Warning: no invocation of /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/scotest had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/amptest had a zero exit code or showed the expected version
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/hwdb passed the binary check.
- Warning: no invocation of /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/hcieventmask had a zero exit code or showed the expected version
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/hcisecfilter passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/btinfo passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/btconfig passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/btsnoop passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/btproxy passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/btiotest passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/bneptest passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/mcaptest passed the binary check.
- Warning: no invocation of /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/cltest had a zero exit code or showed the expected version
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/oobtest passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/advtest passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/seq2bseq passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/nokfw passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/rtlfw passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/create-image passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/eddystone passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/ibeacon passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/btgatt-client passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/btgatt-server passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/test-runner passed the binary check.
- Warning: no invocation of /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/check-selftest had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/gatt-service had a zero exit code or showed the expected version
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/btmgmt passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/obex-client-tool passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/obex-server-tool passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/bluetooth-player passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/obexctl passed the binary check.
- Warning: no invocation of /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/hid2hci had a zero exit code or showed the expected version
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/bluetoothd passed the binary check.
- /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50/bin/obexd passed the binary check.
- 36 of 47 passed binary check by having a zero exit code.
- 19 of 47 passed binary check by having the new version present in output.
- found 5.50 with grep in /nix/store/sdf6cl55n4fp0iq5q9ky6n56inpsln2x-bluez-5.50
- directory tree listing: https://gist.github.com/d81fb1f39a7430f91d1e576b1eb599e7
- du listing: https://gist.github.com/7555f6b1dcd34da7c9731a6de05e553b
Also remove the upstream device trees beforehand so we don't
accidentally end using them if we mess up in postFixup.
Also on the topic of mess ups, make the copy unconditional since they
always seem to be built on all architectures anyway so checking for
their existence just hides typos.
In particular, now the mainline kernel can be built on the RPi 1 as well
(so kernelBaseConfig should always be a mainline defconfig from now on).
And RPi 2 users can now use linux_rpi without doing the
`nixpkgs.config.platform = lib.systems.platforms.raspberrypi2;` dance.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/criu/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/31grlhm7igrgi29fhmndki41a8f87cvs-criu-3.9/bin/crit had a zero exit code or showed the expected version
- /nix/store/31grlhm7igrgi29fhmndki41a8f87cvs-criu-3.9/bin/compel passed the binary check.
- /nix/store/31grlhm7igrgi29fhmndki41a8f87cvs-criu-3.9/bin/criu passed the binary check.
- 2 of 3 passed binary check by having a zero exit code.
- 0 of 3 passed binary check by having the new version present in output.
- found 3.9 with grep in /nix/store/31grlhm7igrgi29fhmndki41a8f87cvs-criu-3.9
- directory tree listing: https://gist.github.com/5db13cedfd351a5d1fd8ed3d70ccbac3
- du listing: https://gist.github.com/3a064c8b51705c90c1093a81ab9495ee
meson 0.46 no longer likes receiving both -Dmandir and --mandir. I removed the flags from the expression in favour of those in the meson setup hook. This also fixes manpages which were previously
installed to $man/lib for some reason.
DPDK kernel modules are optional and its libraries do not reference them.
This allows to move the packages that depend on DPDK out of linuxPackages,
since they do not depend on kernel version.
Wireguard is now split into two pretty much independent packages:
`wireguard` (Linux-specific kernel module) and `wireguard-tools`,
which is cross-platform.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/usbutils/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/wgq4wwb9dxnhkbih9jscikf2lxhdvbkl-usbutils-010/bin/lsusb.py had a zero exit code or showed the expected version
- /nix/store/wgq4wwb9dxnhkbih9jscikf2lxhdvbkl-usbutils-010/bin/usbhid-dump passed the binary check.
- /nix/store/wgq4wwb9dxnhkbih9jscikf2lxhdvbkl-usbutils-010/bin/lsusb passed the binary check.
- /nix/store/wgq4wwb9dxnhkbih9jscikf2lxhdvbkl-usbutils-010/bin/usb-devices passed the binary check.
- 3 of 4 passed binary check by having a zero exit code.
- 1 of 4 passed binary check by having the new version present in output.
- found 010 with grep in /nix/store/wgq4wwb9dxnhkbih9jscikf2lxhdvbkl-usbutils-010
- directory tree listing: https://gist.github.com/ea1dc2aa0de1416d4359481ce7edb85e
- du listing: https://gist.github.com/f46f6ac9b995df459105446dc2761e28
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/firejail/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/5zjr9idl48c08apan8gh45wh971i49i9-firejail-0.9.54/bin/firejail had a zero exit code or showed the expected version
- /nix/store/5zjr9idl48c08apan8gh45wh971i49i9-firejail-0.9.54/bin/firemon passed the binary check.
- /nix/store/5zjr9idl48c08apan8gh45wh971i49i9-firejail-0.9.54/bin/firecfg passed the binary check.
- 2 of 3 passed binary check by having a zero exit code.
- 2 of 3 passed binary check by having the new version present in output.
- found 0.9.54 with grep in /nix/store/5zjr9idl48c08apan8gh45wh971i49i9-firejail-0.9.54
- directory tree listing: https://gist.github.com/3fb76054296d9e45fea3c47ae6a9f03f
- du listing: https://gist.github.com/a732bad0be0159f527ca4e8c532400ed
When doing source routing/multihoming, it's practical to give names to routing
tables. The absence of the rt_table file in /etc make this impossible.
This patch recreates these files on rebuild so that they can be modified
by the user see NixOS#38638.
iproute2 is modified to look into config.networking.iproute2.confDir instead of
/etc/iproute2.
It turns out none of this stuff is needed. The docs aren't evenly built
properly anyways so the build trivially succeeds either way, due to what
looks like upstream misunderstanding automake. If I try to build the
docs manually in a cross shell (before and after this change), there's a
make rule error such that some HTML files aren't even attempted to be
built and then a copy fails.
Even if this was all fixed, these been a good number of cross fixes
upstream getting them to use CC_FOR_BUILD and other good stuff, so I
doubt such hacks would be needed.
Progress towards #40531 and #33302.
I’m not going to fix all of them but this is the best way to do this
in Apple things. Just add ‘EXPORT_DSTDIR’ to the installFlags & set
‘DSTDIR’ to $(out). Please do this instead of the patching!
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/alsa-utils/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/arecord -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/arecord --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsamixer -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsamixer --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsamixer help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amixer -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amixer --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amixer help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amixer -v’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amixer --version’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amidi -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amidi --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amidi -V’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amidi --version’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aplay -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aplay --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/speaker-test -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/speaker-test --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaloop -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaloop --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsabat -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsabat --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aplaymidi -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aplaymidi --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aplaymidi -V’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aplaymidi --version’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/arecordmidi -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/arecordmidi --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/arecordmidi -V’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/arecordmidi --version’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aseqdump -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aseqdump --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aseqdump -V’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aseqdump --version’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaucm -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaucm --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaucm help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsatplg -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsatplg --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsa-info.sh -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsa-info.sh --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsa-info.sh help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaconf -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaconf --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsactl -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsactl --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsactl -v’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsactl --version’ and found version 1.1.6
- found 1.1.6 with grep in /nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6
- directory tree listing: https://gist.github.com/325af09e0dbb84a155838bdb37c5f89a
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pam_u2f/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/diyxvz87ashi10zx97b0dyl2hsr6f9bh-pam_u2f-1.0.6/bin/pamu2fcfg -h’ got 0 exit code
- ran ‘/nix/store/diyxvz87ashi10zx97b0dyl2hsr6f9bh-pam_u2f-1.0.6/bin/pamu2fcfg --help’ got 0 exit code
- ran ‘/nix/store/diyxvz87ashi10zx97b0dyl2hsr6f9bh-pam_u2f-1.0.6/bin/pamu2fcfg -V’ and found version 1.0.6
- ran ‘/nix/store/diyxvz87ashi10zx97b0dyl2hsr6f9bh-pam_u2f-1.0.6/bin/pamu2fcfg --version’ and found version 1.0.6
- found 1.0.6 with grep in /nix/store/diyxvz87ashi10zx97b0dyl2hsr6f9bh-pam_u2f-1.0.6
- directory tree listing: https://gist.github.com/7d4bb96a876d359bc67f88a024a674f8
Darling has a case conflict which means that its src hash will be
different between case sensitive and case insensitive file systems.
This is not ideal and the only way around it is basically to remove
the offending files from the output. I use fetchzip here to do that
but I hope there is a better fix available eventually.
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
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/kexec-tools/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/fs7vc5d6vw26v0502smh2dhg6390d1za-kexec-tools-2.0.17/bin/kexec -h’ got 0 exit code
- ran ‘/nix/store/fs7vc5d6vw26v0502smh2dhg6390d1za-kexec-tools-2.0.17/bin/kexec --help’ got 0 exit code
- ran ‘/nix/store/fs7vc5d6vw26v0502smh2dhg6390d1za-kexec-tools-2.0.17/bin/kexec -v’ and found version 2.0.17
- ran ‘/nix/store/fs7vc5d6vw26v0502smh2dhg6390d1za-kexec-tools-2.0.17/bin/kexec --version’ and found version 2.0.17
- found 2.0.17 with grep in /nix/store/fs7vc5d6vw26v0502smh2dhg6390d1za-kexec-tools-2.0.17
- directory tree listing: https://gist.github.com/892a831f872f6ec59c936b89b0bd6aa6
Adds a couple of useful NetBSD and OpenBSD derivations. Some of these
will be integrated into Nixpkgs later.
Noncomprehensive list:
- netbsd.getent
- netbsd.getconf
- netbsd.fts
- openbsd.mg
- netbsd.compat (can replace libbsd)
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/acpid/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpi_listen -h’ got 0 exit code
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpi_listen --help’ got 0 exit code
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpi_listen -v’ and found version 2.0.29
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpi_listen --version’ and found version 2.0.29
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpid help’ got 0 exit code
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpid -v’ and found version 2.0.29
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpid --version’ and found version 2.0.29
- found 2.0.29 with grep in /nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29
- directory tree listing: https://gist.github.com/48210d03059b65f940b06df3ebb636d1
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/mcelog/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/8dyjjqwjjhzsdfzk8sk0v2qj8b72gc5l-mcelog-157/bin/mcelog --help’ got 0 exit code
- ran ‘/nix/store/8dyjjqwjjhzsdfzk8sk0v2qj8b72gc5l-mcelog-157/bin/mcelog --version’ and found version 157
- found 157 with grep in /nix/store/8dyjjqwjjhzsdfzk8sk0v2qj8b72gc5l-mcelog-157
- directory tree listing: https://gist.github.com/cc3e7a088b51c408fc98ae7bba0d57c3
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pam_u2f/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/w4zrfq02p2ssbk391n380g8bm1fy8ai7-pam_u2f-1.0.5/bin/pamu2fcfg -h’ got 0 exit code
- ran ‘/nix/store/w4zrfq02p2ssbk391n380g8bm1fy8ai7-pam_u2f-1.0.5/bin/pamu2fcfg --help’ got 0 exit code
- ran ‘/nix/store/w4zrfq02p2ssbk391n380g8bm1fy8ai7-pam_u2f-1.0.5/bin/pamu2fcfg -V’ and found version 1.0.5
- ran ‘/nix/store/w4zrfq02p2ssbk391n380g8bm1fy8ai7-pam_u2f-1.0.5/bin/pamu2fcfg --version’ and found version 1.0.5
- found 1.0.5 with grep in /nix/store/w4zrfq02p2ssbk391n380g8bm1fy8ai7-pam_u2f-1.0.5
- directory tree listing: https://gist.github.com/63aa3c566fe3d6ad7704e45ee7e969fc
See:
https://github.com/NixOS/nixpkgs/issues/39154
Not sure why we're seeing that behavior re:fetchFromGitLab,
but for now use a likely-to-be-stable URL instead.
Fixes#39154.
(although the issue warrants some additional investigation IMO)
Source master rebase of my [PR #34].
Eventually, we might consider doing something for GNU binutils too, in
order that we switch (the normal) ld-wrapper to always use this to
leverage ld to resolve libraries, rather than faking it in bash.
[PR #34]: https://github.com/tpoechtrager/cctools-port/pull/34
During the last staging merge I assume that we turned on
-Werror=format-security by default (haven't checked in-depth though),
which actually is a good thing.
This causes the rtkit build to now fail, so I took a patch from Debian
to fix these issues.
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/ipset/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/p1k7d2y5aa4haxlkkn2jadviwvl5plcc-ipset-6.38/bin/ipset -h’ got 0 exit code
- ran ‘/nix/store/p1k7d2y5aa4haxlkkn2jadviwvl5plcc-ipset-6.38/bin/ipset --help’ got 0 exit code
- ran ‘/nix/store/p1k7d2y5aa4haxlkkn2jadviwvl5plcc-ipset-6.38/bin/ipset help’ got 0 exit code
- found 6.38 with grep in /nix/store/p1k7d2y5aa4haxlkkn2jadviwvl5plcc-ipset-6.38
- directory tree listing: https://gist.github.com/0c86d4251a82d41c7e788e320f7013d0
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/sysstat/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3/bin/sar --help’ got 0 exit code
- ran ‘/nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3/bin/iostat -h’ got 0 exit code
- ran ‘/nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3/bin/iostat help’ got 0 exit code
- ran ‘/nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3/bin/pidstat -h’ got 0 exit code
- ran ‘/nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3/bin/cifsiostat -h’ got 0 exit code
- ran ‘/nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3/bin/cifsiostat help’ got 0 exit code
- found 11.7.3 with grep in /nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3
- directory tree listing: https://gist.github.com/1274e29f5a0476b26643f85767b98e40
Otherwise the build system computes incorrect references and looks for
perf-core in /libexec. DESTDIR for normal buildsystems is never the
right choice for nixpkgs.
