Re: [Nix-dev] Monitoring by default

I like the idea too. It seems to me that distributions really lack metrics collection and data analysis. For example, it would be nice to have automatic gathering of the battery usage (charge/discharge/capacity) and an easy access to compiled historical data like the capacity loss over the

Re: [Nix-dev] Can a nixOps coordinator update itself?

I don't think it would be a problem but I wouldn't make promises. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Can a nixOps coordinator update itself?

Hi Nix-Ops devs, I'm currently using a separate online instance to deploy my nixos servers. This deploy instance is running nixos itself (I deployed it from a local vm with nixOps). Can the online instance update itself? Meaning it deploying updates via nixOps to itself? As I can always redeploy

[Nix-dev] break purity

Hi, I've got a bunch of artifacts being built in the /tmp/nix-build-component_name.drv-0 now I want to point the build manager, in this case cargo using the CARGO_TARGET_DIR env var to put the artifacts into a directory I make directly in the /tmp/target_${name} This way any further

Re: [Nix-dev] break purity

You can set up a build environment resembling what nix-build would use using the nix-shell command. All dependencies are provided, and each build phase gets a function. On 21 April 2016 at 17:42, stewart mackenzie wrote: > Hi, > > I've got a bunch of artifacts being built in

Re: [Nix-dev] Upgrade from 15.09 to 16.03 with NixOps

> The expressions are evaluated from the coordinator, so either you upgrade > the channel there or you check out nixpkgs somewhere and set > `NIX_PATH=nixpkgs=/path/to/your/clone` before running nixops. It is also possible to use `-I nixpkgs=` and point directly to the channel you want to use:

Re: [Nix-dev] PolicyKit timeout after upgrade to 16.03

Hi Roger, I did find a workaround by disabling polkit alltogether. security.polkit.enable = false As soon as I re-enable polkit, the issue is back again. I will still file an issue for this, for now the systems work without polkit. As the servers are never running X, I'm still unsure if I need

Re: [Nix-dev] Upgrade from 15.09 to 16.03 with NixOps

Hi Teo, Kevin and Wout, thank you all for your kind support. I do add the nixpkgs line and things seem to work correctly. I was just getting confused as this change initially didn't trigger a rebuild of the deployed system. Kind regards, Erik On Wed, Apr 20, 2016 at 11:42 PM Wout Mertens

Re: [Nix-dev] Upcoming PyPi URL Scheme Change

I also started to write some code to automate discovery of python package dependencies. Unfortunately I haven't had the chance to keep working on it. And some of the formats are quite ambiguous (does the lack of a run_requires key mean that we should look for the information somewhere else,

Re: [Nix-dev] Upcoming PyPi URL Scheme Change

Thanks for the update. There are indeed some things we can automate. Before, I experimented with using one of the API's to get out as much metadata as possible. We could also use pypi2nix, which can give for more information, but requires downloading all files. Unfortunately, the old site still