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

Profpatsch writes: > Maybe it’s time to automate what we can? Similar to Hackage? I'm not too familiar with what is done with Hackage, but I think what we have for Python isn't a good approach. I have a meeting with dstufft to try and come up with a better solution. It might

[Nix-dev] Pull request for sssd package, RFC

Hi all, I recently submitted a pull request to nixpkgs to add the sssd package: https://github.com/NixOS/nixpkgs/pull/14697 For those not familiar, sssd is RedHat's daemon for managing LDAP authentication, automount maps, and other things. The website is here: https://fedorahosted.org/sssd/

[Nix-dev] libxml2

The file xml2-config will not report the path to xml2-config itself since that was moved to the dev output. The attached patch sets exec_prefix to match the executable files placed in the dev output. >From ddd8f1a6c52be129be73faf023f9769cede75042 Mon Sep 17 00:00:00 2001 From: Karn Kallio

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

On 16-04-20 11:41am, Graham Christensen wrote: > I recently got word that PyPi is changing their URL scheme. > > Old example: > https://pypi.python.org/packages/source/a/ansible/ansible-1.8.2.tar.gz#md5=c2ac0e5a4c092dfa84c7e9e51cd45095 > > New example: >

Re: [Nix-dev] Why not use SONAME instead of RPATH

Woah I love that! +1, I don't see why we can't do that… Wout. On Wed, Apr 20, 2016 at 1:52 PM Silvio Frischknecht wrote: > Hello, > > I recently found out that if you set the SONAME of a library to an > absolute path. > > gcc --shared -Wl,-soname="$(pwd)/libxyz.so" -o libxyz.so

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. On Wed, Apr 20, 2016 at 1:52 PM Teo Klestrup wrote: > I believe the channels are

Re: [Nix-dev] ioquake3 on nixos

Hi, On 04/19/2016 07:20 AM, Máté Kovács wrote: > (In case you're wondering: I didn't yet figure out what's wrong with my > channels, so I'm pointing to a clone of the nixpkgs github repo using > the -I option for building the game.) Try my fix, I think it might work. My theory is that points to

[Nix-dev] Upcoming PyPi URL Scheme Change

Hello Nixers, I recently got word that PyPi is changing their URL scheme. Old example: https://pypi.python.org/packages/source/a/ansible/ansible-1.8.2.tar.gz#md5=c2ac0e5a4c092dfa84c7e9e51cd45095 New example:

Re: [Nix-dev] Why not use SONAME instead of RPATH

On 17/04/16 12:02, Silvio Frischknecht wrote: > > Advantages over RPATH: > + probably faster since rpaths in nixos tend to be quite long and every > library has to be looked for in every folder (linear vs quadratic > complexity) > + only has to be setup once per library - all referrers will >

Re: [Nix-dev] few questions before migrating from Debian…

UEFI requires a separate ESP partition anyway. Unless you plan on running on FAT32. On 16/04/2016 9:35 PM, "Saša Janiška" wrote: > Roger Qiu writes: > > > Will you be using UEFI? > > Yes, on my single-disk netbook…any gotcha in regard? > > > Sincerely, >

Re: [Nix-dev] Nix-like npm replacement (NodeJS)

Yep and it (along with nixpkgs and git) is one of the few package managers that focus on content addressability. On 20/04/2016 7:50 PM, "Wout Mertens" wrote: > I thought this would be interesting for some people on this list: > > http://gugel.io/ied/ : > > Under the hood,

Re: [Nix-dev] few questions before migrating from Debian…

ZFS is the best :-) My gist ( https://gist.github.com/vizanto/7374277 ) is still relevant. With slight modifications you don’t need a separate /boot filesystem since recent Grub can read ZFS filesystems (mirrors, not sure about RAID-Z) just fine. Basically just skipping the partitioning steps

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

Hi Roger, the weird thing is that my local vm, the machine that actually deploys the servers, doesn't have this issue. This instance also runs nixos-16.03 and uses the same nixos-16.03-small channel. This issue started when trying to upgrade to 16.03 I was not really clear about how to do this

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

I believe the channels are taken from the coordinator, so when the coordinator is upgraded then the other machines should be, too. On 18 Apr 2016 19:20, "4levels" <4lev...@gmail.com> wrote: > Hi Nix'ers, > > This is an Nix Ops related question. > > How can I specify which channel to use inside

[Nix-dev] Why not use SONAME instead of RPATH

Hello, I recently found out that if you set the SONAME of a library to an absolute path. gcc --shared -Wl,-soname="$(pwd)/libxyz.so" -o libxyz.so libxyz.c and then later link to it gcc main.c -L. -lxyz the dynamic linker will only look for the library in the exact path specified when

Re: [Nix-dev] Accessing files in derivations.

On 04/20/2016 10:20 AM, Guillaume Maudoux (Layus) wrote: > If providing default outputs is just a question of symlinking attributes > to existing derivations, the following (pseudo)code would do, right ? Yes, something like that would work in most cases. It would redirect incorrectly in cases

[Nix-dev] Nix-like npm replacement (NodeJS)

I thought this would be interesting for some people on this list: http://gugel.io/ied/ : Under the hood, ied maintains an "object database", similar to git. Instead of storing packages by some arbitrary name, a SHA1-checksum is being generated to approximate their contents. The checksums can not

Re: [Nix-dev] Monitoring by default

+1 for the initiative. i don't believe personally enabling monitoring by default should be the right way to go (since we all use nixos in different contexts), but having a commented instructions in generated configurations.nix would be the way to go. it would be nice if systemd monitoring stuff

Re: [Nix-dev] Accessing files in derivations.

Le 20/04/16 08:59, Vladimír Čunát a écrit : > On 04/19/2016 10:03 PM, Layus wrote: >> But your description made me think of a viable workaround. >> We could ensure that every derivation has a fixed set of known outputs, >> like dev, lib, out and man. >> If there is no "lib" output, then the lib

Re: [Nix-dev] Accessing files in derivations.

On 04/19/2016 10:03 PM, Layus wrote: > But your description made me think of a viable workaround. > We could ensure that every derivation has a fixed set of known outputs, > like dev, lib, out and man. > If there is no "lib" output, then the lib attribute could be an alias > for out. Yes, that

Re: [Nix-dev] Monitoring by default

Seems interesting. You mention alerts for "System software too old.", but the only vaguely-universal definition of "too old" I can think of would be "missing security updates", and that's both debatable and an area where NixOS is currently fairly lacking in infrastructure and tooling. Default