Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pacman/versions.
These checks were done:
- built on NixOS
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/repo-add passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/makepkg passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pacman-db-upgrade passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pacman-key passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pkgdelta passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/repo-elephant passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/repo-remove passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/vercmp passed the binary check.
- Warning: no invocation of /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/testpkg had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/cleanupdelta had a zero exit code or showed the expected version
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pacman passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pacman-conf passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/makepkg-template passed the binary check.
- 11 of 13 passed binary check by having a zero exit code.
- 0 of 13 passed binary check by having the new version present in output.
- found 5.1.0 with grep in /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0
- directory tree listing: https://gist.github.com/61f365ecd9146adf48fc68403568904d
- du listing: https://gist.github.com/391d88c911aeda73c0cd89f80ced8ce2
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/packagekit/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10/bin/pkcon -h’ got 0 exit code
- ran ‘/nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10/bin/pkcon --help’ got 0 exit code
- ran ‘/nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10/bin/pkmon -h’ got 0 exit code
- ran ‘/nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10/bin/pkmon --help’ got 0 exit code
- found 1.1.10 with grep in /nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10
- directory tree listing: https://gist.github.com/1d641323594032d2e935bd1e088bf409
The isSeccomputable flag treated Linux without seccomp as just a
normal variant, when it really should be treated as a special case
incurring complexity debt to support.
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newt -h` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newt --help` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newt help` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newt version` and found version 1.3.0
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newtmgr -h` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newtmgr --help` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newtmgr help` got 0 exit code
- found 1.3.0 with grep in /nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin
- found 1.3.0 in filename of file in /nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin
cc "@pjones @ehmry @lethalman"
This reverts commit 695027f61c.
We really can't have "nix-env -i nix" *not* upgrade nixUnstable to a
newer nixStable. For instance, it would cause "nix upgrade-nix" to
produce a user environment with collisions.
