Ok, new proposal: Whenever you make a change that does any of these:
- Breaks backwards compatibility with existing user state (e.g. db
versions etc)
- Changes type of options
- Changes semantics of options
- Removes existing options
you should include a description of the change
Minor side note: I tried to update the ntp package to version 4.2.8, but
the build fails when --without-crypto is specified (like we do). Duh. :-(
Apparently, the latest vulnerability applies only to instances that
*have* crypto code enabled, it our moderately old copy of ntp isn't
vulnerable
Feel free to try enabling timesyncd by simply setting
`services.timesyncd.enable` in your nixos config. It should work as a drop
in replacement and respect the servers set in `services.ntp. servers`.
On Dec 21, 2014 11:47 PM, Kirill Elagin kirela...@gmail.com wrote:
If we are talking about
Hi,
Does anyone know what’s exactly the problem
https://github.com/NixOS/nixpkgs/blob/6d1befb7b7d27c3f54e70aec790b2eaa54700f0f/pkgs/top-level/all-packages.nix#L12864
with wine on amd64?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
Hi Kirill,
Nixpkgs only includes a package for the 32bit version of wine, which works
for 32bit applications using wine on amd64.
Wine64 has not been packaged for nixpkgs, although this should be possible.
That comment you referred to is from 2010, Eelco might be able to clarify,
but I suspect
