| Commit message (Collapse) | Author | Age |
| |
|
|\
| |
| | |
usbguard-nox: init at 0.7.4
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is just usbguard without the Qt GUI that brings in Qt dependencies.
Remove pandoc to reduce closure size. The usbguard build appears to
use it only for spell checking.
Remove asciidoctor because 0.7.1 switched to asciidoc. But don't add
a dependency on asciidoc, because that causes the build fails on
external DTDs.
|
| |
| |
| |
| |
| | |
The changelog mentions 5.2 support:
https://github.com/DisplayLink/evdi/releases/tag/v1.6.2
|
|\ \
| | |
| | | |
wpa_supplicant: 2.8 -> 2.9
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/wpa_supplicant/versions
|
|\ \ \
| | | |
| | | | |
smemstat: 0.02.04 -> 0.02.05
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/smemstat/versions
|
|\ \ \
| | | |
| | | | |
pscircle: 1.3.0 -> 1.3.1
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/pscircle/versions
|
| | | |
|
|\ \ \
| | | |
| | | | |
powerstat: 0.02.19 -> 0.02.20
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/powerstat/versions
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
boot.kernelPackages: check for conflicts
It's currently possible to set conflicting `boot.kernelPackages` several times.
Nixos now warns when this is the case instead of just picking one.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It's currently possible to set conflicting `boot.kernelPackages` several times
which can prove confusing.
This is an attempt to warn for this.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
fwupd: 1.2.8 -> 1.2.10
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/fwupd/versions
|
|\ \ \ \
| | | | |
| | | | | |
forkstat: 0.02.10 -> 0.02.11
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/forkstat/versions
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* fnotifystat: 0.02.02 -> 0.02.03
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/fnotifystat/versions
* Update default.nix
|
|\ \ \ \
| | | | |
| | | | | |
iotop: use python3
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The support of python2 will be dropped by the end of 2019, so python3
should be used by default here. In fact, this package supports both
python v2 and v3, however the installation with python3 broke because of a
bug in setup.py which is only fixed in the upstream's master[1].
Additionally, distros like debian already use iotop along with python3[2],
so this should be a sensible thing to do.
[1] https://repo.or.cz/iotop.git?a=commit;h=99c8d7cedce81f17b851954d94bfa73787300599
[2] https://packages.debian.org/de/buster/iotop
|
|\ \ \ \
| | | | |
| | | | | |
eventstat: 0.04.06 -> 0.04.07
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/eventstat/versions
|
|\ \ \ \
| | | | |
| | | | | |
nftables: 0.9.0 -> 0.9.1
|
| |/ / / |
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
conky: 1.11.3 -> 1.11.5
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/conky/versions
|
|\ \ \ \
| | | | |
| | | | | |
Staging next
|
| |\| | | |
|
| |\ \ \ \ |
|
| |\ \ \ \ \ |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Use upstream units for mdadm
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
We also correct paths in udev rules. This is cleaner and allows for less
unexpected behaviour. We still check for self-references, however we do
it manually now and only for binaries as udev rules can have them.
Rather, we patch them out during initrd generation now.
|
| | | | | | | | |
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
checksec: 2.0.1 -> 2.1.0
|
| | |_|_|_|/ / /
| |/| | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/checksec/versions
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
alfred: 2019.2 -> 2019.3
|
| |/ / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/alfred/versions
|
|/ / / / / / / |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
nixos/hardware.deviceTree: new module
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This is just as messy as it is for the kernel files. Maybe it should be
done in the uboot boot-loader?
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In response to comments, create a sub-folder for deviceTree packages
(starting with rpi), and a top-level package for helpers.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Add support for custom device-tree files, and applying overlays to them.
This is useful for supporting non-discoverable hardware, such as sensors
attached to GPIO pins on a Raspberry Pi.
|
| | | | | | | | |
|