Re: [Nix-dev] Merging stdenv-updates soon?
Hi. On 08/24/2013 02:40 PM, Peter Simons wrote: are there any issues left that would prevent us from merging the stdenv-updates branch? As far as I can tell, the branch is in pretty good shape. The whole darwin is broken because of failing perl. However, I can see no error in the log (except that the build failed). Could it be a random transient problem? I have no machine to try it. We need to enable building everything on Hydra first. I suspect there may be some packages that need minor patches to compile with newer gcc. Thanks for starting Hydra. Vlada smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Merging stdenv-updates soon?
On 08/27/2013 09:24 AM, Vladimír Čunát wrote: The whole darwin is broken because of failing perl. However, I can see no error in the log (except that the build failed). Could it be a random transient problem? I have no machine to try it. I forgot a link http://hydra.nixos.org/job/nixpkgs/stdenv/perl.x86_64-darwin smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Set locale during nix build?
Hi Rickard, have you tried adding export LANG=en_US.UTF-8 to the build environment, i.e. in a preConfigure hook? Take care, Peter ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Merging stdenv-updates soon?
Hi, On 27/08/13 09:28, Vladimír Čunát wrote: On 08/27/2013 09:24 AM, Vladimír Čunát wrote: The whole darwin is broken because of failing perl. However, I can see no error in the log (except that the build failed). Could it be a random transient problem? I have no machine to try it. I forgot a link http://hydra.nixos.org/job/nixpkgs/stdenv/perl.x86_64-darwin Near the top: sed: -i: No such file or directory -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Set locale during nix build?
Hi,
On 27/08/13 10:29, Peter Simons wrote:
have you tried adding
export LANG=en_US.UTF-8
to the build environment, i.e. in a preConfigure hook?
If you do that, you probably also need to set:
export LOCALE_ARCHIVE=${glibcLocales}/lib/locale/locale-archive
Otherwise the locale won't be found.
--
Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Set locale during nix build?
On 08/27/2013 02:37 PM, Eelco Dolstra wrote:
Hi,
On 27/08/13 10:29, Peter Simons wrote:
have you tried adding
export LANG=en_US.UTF-8
to the build environment, i.e. in a preConfigure hook?
If you do that, you probably also need to set:
export LOCALE_ARCHIVE=${glibcLocales}/lib/locale/locale-archive
Otherwise the locale won't be found.
Ah, the combination of LANG and LOCALE_ARCHIVE works, thank you!
/ Rickard
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] disk setup for nixos installation
aszlig writes: So you could use it, but it's not yet ready for being part of the nixos installation procedure. Here is the repository: https://github.com/aszlig/nixpart And it is in nixpkgs as well. Thank you very much. I have had a play, and it looks very helpful. There is one small problem though: I want to use the nilfs2 filesystem, and kickstart does not support it out of the box. Is there any way to pass some option to tell nixpart and kickstart that nilfs2 is a valid filesystem type ? When I specify a filesystem of type nilfs2 in the kickstart file, nixpart just ignores it (it does not even complain about it). If I change the filesystem type (e.g. to ext3), then nixpart will create it. Tim ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Merging stdenv-updates soon?
On 08/27/2013 05:02 PM, James Cook wrote: On 27 August 2013 05:55, Vladimír Čunát vcu...@gmail.com wrote: Ah, thanks. So it's the postPatch phase, but I don't see what's the problem, nor why it should be different than on Linux platforms. I have seen this before on FreeBSD. The issue was that BSD sed expects a suffix after -i, but Linux sed is happy with -i on its own. Probably Darwin's stdenv uses the Darwin's sed. I believe the failing command is sed /^$pat/d -i MANIFEST What do you mean by suffix? Vlada smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Merging stdenv-updates soon?
On 27 August 2013 08:08, Vladimír Čunát vcu...@gmail.com wrote: On 08/27/2013 05:02 PM, James Cook wrote: On 27 August 2013 05:55, Vladimír Čunát vcu...@gmail.com wrote: Ah, thanks. So it's the postPatch phase, but I don't see what's the problem, nor why it should be different than on Linux platforms. I have seen this before on FreeBSD. The issue was that BSD sed expects a suffix after -i, but Linux sed is happy with -i on its own. Probably Darwin's stdenv uses the Darwin's sed. I believe the failing command is sed /^$pat/d -i MANIFEST What do you mean by suffix? In BSD sed, use -i .bak MANIFEST, and then the original file will be saved as MANIFEST.bak. With GNU sed the backup file is optional. The two obvious solutions are: - Make sure everything uses GNU sed on Darwin and FreeBSD. - Make sure every use of sed -i has a backup file suffix after the -i. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Objections to switching to Bluez5?
Hi! I'm currently updating packages, so Bluez5 works again. I believe it was not made the default way back when because it did not support Kernel 3.2, right? Well, now 3.4 is default so how about switching NixOS over to Bluez5 (assuming I get it all to work...)? Cheers, Aristid ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Objections to switching to Bluez5?
It appears that KDE does not support Bluez 5 at this point, so this appears to be out of the question for now. 2013/8/27 Aristid Breitkreuz arist...@gmail.com Hi! I'm currently updating packages, so Bluez5 works again. I believe it was not made the default way back when because it did not support Kernel 3.2, right? Well, now 3.4 is default so how about switching NixOS over to Bluez5 (assuming I get it all to work...)? Cheers, Aristid ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Plone Development on Nix is getting quite nice!
Hi, Thanks to the work Rok Garbas has been doing on generating python packages I noticed it is now possible to use a combination of Nix and a standard buildout.cfg for Plone development with a small patch to buildout. I've added instructions to the wiki for anyone who's interested: https://nixos.org/wiki/Plone_development#How_to_use_myEnvFun_and_buildout-nix_to_create_a_plone_development_environment Although this wouldn't be a suitable way to deploy Plone, as a development environment it already provides many advantages over a plain old buildout setup. You can re-use python modules which have already been packaged in nix, which speeds up initial installation greatly (e.g. Python c modules such as ZODB3 are already compiled). These can also effectively be shared between multiple development environments, but, unlike a typical egg cache they can be garbage collected when no longer needed. Since they are in the store, you also know that they haven't been modified, however, if you do want to modify an egg, you can replace the symlink in ./eggs with a copy of the egg and add debugging statements there etc. There is also no need to bootstrap buildout or set up a virtualenv, since buildout-nix is packaged in nix and myEnvFun provides isolation. Required eggs which aren't available in the environment will be downloaded and installed, and other typical buildout development scripts should all work as normal. I've only used this to install and run a vanilla Plone 4.3.1 instance so far, so there may well be complications with more advanced configurations. It would be interesting to hear if anyone else tries it out, or has any feedback about it. You'll notice some addition version pinnings in the buildout.cfg, I'm not sure why they're required, but without them buildout failed with version conflict errors. Cheers, Cillian ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
