| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/ncmpc/versions
|
|
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/mediainfo/versions
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Because dates are an impurity, by default buildImage will use a static
date of one second past the UNIX Epoch. This can be a bit frustrating
when listing docker images in the CLI:
$ docker image list
REPOSITORY TAG IMAGE ID CREATED SIZE
hello latest 08c791c7846e 48 years ago 25.2MB
If you want to trade the purity for a better user experience, you can
set created to now.
pkgs.dockerTools.buildImage {
name = "hello";
tag = "latest";
created = "now";
contents = pkgs.hello;
config.Cmd = [ "/bin/hello" ];
}
and now the Docker CLI will display a reasonable date and sort the
images as expected:
$ docker image list
REPOSITORY TAG IMAGE ID CREATED SIZE
hello latest de2bf4786de6 About a minute ago 25.2MB
|
|\
| |
| | |
installer: refactor
|
| | |
|
|\ \
| | |
| | | |
rdma-core: 19 -> 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/rdma-core/versions
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
pulseeffects: 4.3.4 -> 4.3.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/pulseeffects/versions
|
|\ \ \
| | | |
| | | | |
haskellPackages.sbv: fix location of z3 executable
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A lot of the functionality of the z3 library depends on it being able to
find the z3 executable on $PATH. Hard-coding it here means it will never
be unable to find it and z3 doesn't need to pollute $PATH.
|
| | | |
| | | |
| | | |
| | | | |
The test failed non-deterministically on Hydra because interfaces
sometimes weren't yet fully cleaned up when the result was checked.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The `pkgs.yabar` package is relatively old (2016-04) and contains
several issues fixed on master. `yabar-unstable` containsa recent master
build with several fixes and a lot of new features (I use
`yabar-unstable` for some time now and had no issues with it).
In the upstream bugtracker some bugs could be fixed on ArchLinux by
simply installing `yabar-git` (an AUR package which builds a recent
master).
To stabilize the module, the option `programs.yabar.package` now
defaults to `pkgs.yabar-unstable` and yields a warning with several
linked issues that are known on `pkgs.yabar`.
The test has been refactored as well to ensure that `yabar` actually
starts (and avoid non-deterministic random success) and takes a
screenshot of a very minimalistic configuration on IceWM.
Fixes #46899
|
|\ \ \ \
| | | | |
| | | | | |
gitlab: add missing meta.platforms
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
glxinfo: 8.3.0 -> 8.4.0
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
ocamlPackages.cohttp: 1.0.2 -> 1.1.1
|
| | | | | | |
|
| |_|/ / /
|/| | | |
| | | | |
| | | | |
| | | | | |
output (#46685)
Previously they both would claim to be 'git--' :).
|
| | | | |
| | | | |
| | | | |
| | | | | |
fixes #46728
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
wireguard-tools: 0.0.20180904 -> 0.0.20180918
|
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/wireguard-tools/versions
|
|\ \ \ \ \
| | | | | |
| | | | | | |
vimPlugins: vim-plug, fixes and updates
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vim-addon-nix throws weird errors on startup
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Gotools etc. update, remove goimports
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Newer version has some weird failure cases related to PATH
|
| | | | | |
| | | | | |
| | | | | | |
(roughly 2015-09-15 -> 2018-08-16)
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | | |
https://github.com/troglobit/editline/releases/tag/1.16.0
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
undervolt: 2.8 -> 2.9
|
| | | | | | | |
|