Re: [Nix-dev] nix-shell cannot create directory followed by closeNest: command not found
If you are using nixos unstable, try upgrading. That's related to a gdkpixbuf package bug that has been solved recently. On Sun, Apr 27, 2014 at 7:18 AM, Mateusz Kowalczyk fuuze...@fuuzetsu.co.ukwrote: Hi, I wanted to write some code for the Yi text editor today. It is a Haskell program and I wanted to use nix to help me develop it. After all, the ability to do this is one of the main reasons why I went for NixOS. I followed instructions at [1] and using the Project Sandboxes section, I have arrived at the default.nix file you can find at [2]. When I run ‘nix-shell’, the dependencies listed get downloaded (and installed?) but the incantation fails with: [shana@lenalee:~/programming/yi/yi]$ nix-shell mkdir: cannot create directory ‘/nix/store/d5d5bmdqn9pp05yixckdbiamnhdp8hfw-haskell-yi-ghc7.6.3-0.8.1-profiling’: Read-only file system closeNest: command not found Is there something I'm missing? I thought that maybe it's a name-clash with existing package (Yi is already packaged) but changing the version string in default.nix revealed that wasn't the case. [1]: http://ocharles.org.uk/blog/posts/2014-02-04-how-i-develop-with-nixos.html [2]: http://lpaste.net/103249 -- Mateusz K. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- www.debian.org - The Universal Operating System ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] RFC: NixOS version string format
Hi all, For a long time I've felt that the NixOS version string format VERSION pre NUM_COMMITS_SINCE_THE_VERY_BEGINNING is a bit odd. It feels like a MAJOR.MINOR.PATH format, but PATCH is every increasing. I personally would prefer the number of commits number to be start over each time the version number is bumped. IMHO, that would make it easier to reason about which version you're on. I think such a version number format would also match nicely with what git describe would print if/when we have proper annotated git tags for releases (we should!). Thoughts? Best regards, Bjørn Forsman ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] RFC: NixOS version string format
We're using git, thus the only really meaningfull thing is the hash .. But its hard to compare which is more or less up to date. Thus maybe its worth thiking about adding the hash if it is not included. The hash also identifies the history. Marc Weber ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] RFC: NixOS version string format
The hash is already included in nixos-version. On Sun, Apr 27, 2014 at 12:43 PM, Marc Weber marco-owe...@gmx.de wrote: We're using git, thus the only really meaningfull thing is the hash .. But its hard to compare which is more or less up to date. Thus maybe its worth thiking about adding the hash if it is not included. The hash also identifies the history. Marc Weber ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- www.debian.org - The Universal Operating System ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] RFC: NixOS version string format
+1 for annotated tags and `git describe`. It will also include a hash. Plus some additional useful information. This way we automagically get beautiful names for releases and useful names (with last tag and commit hash) for intermediate versions. Upcoming 14.04 release might be a good point to start creating annotated tags, right? -- Кирилл Елагин On Sun, Apr 27, 2014 at 2:52 PM, Luca Bruno lethalma...@gmail.com wrote: The hash is already included in nixos-version. On Sun, Apr 27, 2014 at 12:43 PM, Marc Weber marco-owe...@gmx.de wrote: We're using git, thus the only really meaningfull thing is the hash .. But its hard to compare which is more or less up to date. Thus maybe its worth thiking about adding the hash if it is not included. The hash also identifies the history. Marc Weber ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- www.debian.org - The Universal Operating System ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Sound issues with PulseAudio (5.0) and Chromium HTML5 video lately
Reverting to PA 4 fixes the issue. 2014-04-26 19:46 GMT+02:00 Aristid Breitkreuz arist...@gmail.com: Hi, I'm having issues with sound in Chromium HTML5 videos lately, since about the time the systemd 212 and PA 5 updates hit nixpkgs. Does anybody else have these problems? Basically instead of the intended sound I get chp chp sounds. I might try later whether reverting to PA 4 helps. Cheers, Aristid ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Unable to install NixOS unstable in UEFI system
Hello.
When installation NixOS unstable on my x86_64 notebook, I am getting the
error
Failed to check file system type of /boot: No such file or directory
The log file is attached, as well as the configuration I am using.
A few months ago I had successfully installed NixOS unstalbe on this
system without any major issues.
I have followed the instructions in the manual at
http://hydra.nixos.org/job/nixos/trunk-combined/nixos.manual.x86_64-linux/latest/download-by-type/doc/manual
Any clues?
Romildo
copying Nix to /mnt
/nix/store/01msmsjrb7yik2l77fksc6cvkvds3qc1-boehm-gc-7.2d
/nix/store/0x21z9gqd3rdhxffhxdaf1ccilaay4s4-gnutar-1.27.1
/nix/store/15wj2xxnxni8ygvrg2m2lh2syhr5010b-curl-7.35.0
/nix/store/1flsshqg61dhbfrylbix8m0riaymr6si-acl-2.2.52
/nix/store/7svaxfvzl8hb7ap3fjfyrqdw3bxi8pd3-sqlite-3.8.4.3
/nix/store/9fb027n5a2lf9qwpb98v77iycqq552pf-gcc-4.8.2
/nix/store/asnkw21m4y0ihphnxi8wvw9f45f0d83k-gzip-1.6
/nix/store/cp1k5gmppz2r12mrnf5qr357r62l6l1k-openssl-1.0.1g
/nix/store/f1yaikpbxnyl9rl23p50b3rc938b6xlx-xz-5.0.5
/nix/store/gmlqaw1kp8c1nrllrs84i1pkmz34yc3b-attr-2.4.47
/nix/store/gmmx1vwm9rxryxmsf1p6sff7kvyjggcq-zlib-1.2.8
/nix/store/h6m2zymy43ms773b0m9841dc14yb4ip5-nix-1.7
/nix/store/hgmvny3ibknm6mfbj1k7p9mrviwy58a2-perl-DBI-1.631
/nix/store/hzkmjagyqhh4ab0prlr61lsrvyljrkan-libssh2-1.4.3
/nix/store/kksws74v0v0jf6dl6f5fhw24dygzairc-zlib-1.2.8
/nix/store/l4sd8xf2q3x5xk5z8ji9dk3hxpb9v8sa-perl-5.16.3
/nix/store/p0vd3ydvxplbpjffkpblwj5dahcmp9ri-bash-4.2-p45
/nix/store/pdskwizjw8ar31hql2wjnnx6g0s6xc50-glibc-2.19
/nix/store/sfhq9l2lyk599qkbiqrdd83yhhh5k97v-bzip2-1.0.6
/nix/store/wszhn3z5cjwqa81fk5i2pdmwypdym0vi-perl-DBD-SQLite-1.42
/nix/store/x76l1l04vnhw82hv6iwcvcchp3f51304-linux-headers-3.7.1
/nix/store/xdswdgz11w9lm9n9bzb6spl7dj45s2x2-coreutils-8.21
/nix/store/z2kdd4wx9nn9sr4kwvvvl8dg495yvhli-perl-WWW-Curl-4.17
building the system configuration...
copying NixOS/Nixpkgs sources...
finalising the installation...
Failed to check file system type of /boot: No such file or directory
Traceback (most recent call last):
File /nix/store/l1sspk59fpkradynsgfm4d843z8w2xai-gummiboot-builder.py, line
97, in module
subprocess.check_call([/nix/store/jn9ij02b1gm426qigymm9kyj7p9md196-gummiboot-43/bin/gummiboot,
--path=/boot, install])
File
/nix/store/qikwsrbsyx59ygcmb36p1rgmfclgg882-python-2.7.6/lib/python2.7/subprocess.py,
line 540, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command
'['/nix/store/jn9ij02b1gm426qigymm9kyj7p9md196-gummiboot-43/bin/gummiboot',
'--path=/boot', 'install']' returned non-zero exit status 1
# Edit this configuration file to define what should be installed on
# your system. Help is available in the configuration.nix(5) man page
# and in the NixOS manual (accessible by running ‘nixos-help’).
{ config, pkgs, ... }:
{
imports =
[ # Include the results of the hardware scan.
./hardware-configuration.nix
];
# Use the gummiboot efi boot loader.
boot.loader.grub.enable = false;
boot.loader.gummiboot.enable = true;
boot.loader.efi.canTouchEfiVariables = true;
# networking.hostName = nixos; # Define your hostname.
# networking.wireless.enable = true; # Enables wireless.
# Select internationalisation properties.
# i18n = {
# consoleFont = lat9w-16;
# consoleKeyMap = us;
# defaultLocale = en_US.UTF-8;
# };
# List services that you want to enable:
# Enable the OpenSSH daemon.
# services.openssh.enable = true;
# Enable CUPS to print documents.
# services.printing.enable = true;
# Enable the X11 windowing system.
# services.xserver.enable = true;
# services.xserver.layout = us;
# services.xserver.xkbOptions = eurosign:e;
# Enable the KDE Desktop Environment.
# services.xserver.displayManager.kdm.enable = true;
# services.xserver.desktopManager.kde4.enable = true;
}
# Do not modify this file! It was generated by ‘nixos-generate-config’
# and may be overwritten by future invocations. Please make changes
# to /etc/nixos/configuration.nix instead.
{ config, pkgs, ... }:
{
imports =
[ nixpkgs/nixos/modules/installer/scan/not-detected.nix
];
boot.initrd.availableKernelModules = [ ehci_pci ahci xhci_hcd usbhid
];
boot.kernelModules = [ kvm-intel ];
boot.extraModulePackages = [ ];
fileSystems./ =
{ device = /dev/sda8;
fsType = ext4;
};
swapDevices =
[ { device = /dev/sda4; }
];
nix.maxJobs = 8;
#hardware.opengl.videoDrivers = [ nvidia ];
hardware.opengl.videoDrivers = [ ];
}
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] RFC: NixOS version string format
On 04/27/2014 12:00 PM, Bjørn Forsman wrote: For a long time I've felt that the NixOS version string format VERSION pre NUM_COMMITS_SINCE_THE_VERY_BEGINNING Perhaps I don't understand what you mean. nixos-version for me prints 14.04pre- + git-hash BTW, the number of commits since 14.04 does give a better intuition than hash by itself, but IMO the actual commit date seems even better (and it's supposed to be monotonous, too). 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] RFC: NixOS version string format
On 27 April 2014 16:54, Vladimír Čunát vcu...@gmail.com wrote: On 04/27/2014 12:00 PM, Bjørn Forsman wrote: For a long time I've felt that the NixOS version string format VERSION pre NUM_COMMITS_SINCE_THE_VERY_BEGINNING Perhaps I don't understand what you mean. nixos-version for me prints 14.04pre- + git-hash Yes, sorry, I didn't mention the hash for some reason. I guess I thought it was a good idea to leave it out of the discussion because it's not something I want to change. Like Marc Weber says above, when using git/distributed system, the hash is the only true identifier. I agree with that. To clear things up: * nixos-version currently adds the git-hash at the very end and I don't want to change that * git describe also adds a hash at the end to provide unique identifier (iff the commit isn't exactly on a tag) Best regards, Bjørn Forsman ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] builder is root, not nixbldn [was: cannot build coreutils]
Ben Franksen wrote: tl;dr I can verify with a very simple nix expression that the builder indeed is root, and not one of the nixbld users. I think this is not as it should be. I finally solved this after looking into the source tree. It turned out that after I re-compiled and installed Nix from source, the configuration directory (sysconfdir) is /usr/local/etc (a somewhat unconventional choice, if you ask me). It was /etc when I had installed Nix from the ubuntu package, but I recently upgraded my system to ubuntu trusty and there is no binary package for trusty yet, so I re-installed from source. Thus my existing entry for build-users-group in /etc/nix.conf was ignored. BTW, I see that there are rpm specs in the sources. How can I create package for my system from the sources? Cheers Ben -- Make it so they have to reboot after every typo. -- Scott Adams ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] nix-shell cannot create directory followed by closeNest: command not found
On 04/27/2014 11:16 AM, Luca Bruno wrote: If you are using nixos unstable, try upgrading. That's related to a gdkpixbuf package bug that has been solved recently. On Sun, Apr 27, 2014 at 7:18 AM, Mateusz Kowalczyk fuuze...@fuuzetsu.co.ukwrote: Hi, I wanted to write some code for the Yi text editor today. It is a Haskell program and I wanted to use nix to help me develop it. After all, the ability to do this is one of the main reasons why I went for NixOS. I followed instructions at [1] and using the Project Sandboxes section, I have arrived at the default.nix file you can find at [2]. When I run ‘nix-shell’, the dependencies listed get downloaded (and installed?) but the incantation fails with: [shana@lenalee:~/programming/yi/yi]$ nix-shell mkdir: cannot create directory ‘/nix/store/d5d5bmdqn9pp05yixckdbiamnhdp8hfw-haskell-yi-ghc7.6.3-0.8.1-profiling’: Read-only file system closeNest: command not found Is there something I'm missing? I thought that maybe it's a name-clash with existing package (Yi is already packaged) but changing the version string in default.nix revealed that wasn't the case. [1]: http://ocharles.org.uk/blog/posts/2014-02-04-how-i-develop-with-nixos.html [2]: http://lpaste.net/103249 -- Mateusz K. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev Upgrading and playing with it for a second did the trick. -- Mateusz K. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Exposing Haskell library + binary when using nix-shell and cabal build
Hello, I'm trying to work on Yi, the text editor written in Haskell. Following [1] and with some help on this list, I managed to get nix-shell working. As I understand it, I should be able to use it instead of cabal sandboxes. There is a problem with this approach that I don't know how to get around. Yi produces a binary and a library: the binary then loads the library at run-time. With cabal sandboxes, I had a cabal package database per-sandbox and was able to run Yi from within a sandbox while pointing it at that library. My wrapper script from my previous setup is something like this: export GHC_PACKAGE_PATH=$HOME/programming/yi/yi/.cabal-sandbox/i386-linux-ghc-7.6.3-packages.conf.d:$GHC_PACKAGE_PATH $HOME/programming/yi/yi/.cabal-sandbox/bin/yi $@ This worked fine and I could point other things there if I needed to and they would see the libraries. With nix-shell followed by ‘cabal build’, we do not get such a database. Running Yi, we quickly find out that it can't find its own libraries. OK, I think, I will try ‘cabal install’, it should get registered and be able to see its own library. This approach doesn't work, ‘cabal install’ fails with: yi-0.8.1: dependency dlist-0.7.0.1-097643e4e208c620450bdd15d82b0b72 doesn't exist (use --force to override) yi-0.8.1: dependency dyre-0.8.12-ec18729a01bb7f4f276d764f16f59f88 doesn't exist (use --force to override) yi-0.8.1: dependency fingertree-0.1.0.0-7b004cd58ca38ab98a8debc0170a04be doesn't exist (use --force to override) yi-0.8.1: dependency glib-0.12.5.4-407a95c1ac58268bb8de695128c633b1 doesn't exist (use --force to override) … and many more of these. As far as I can tell there's one for each dependency. ‘cabal haddock’ fails as well: Running Haddock for yi-0.8.1... Preprocessing library yi-0.8.1... command line: cannot satisfy -package-id Diff-0.3.0-56d6d899a3d3165124001f1cd6bed1a7 (use -v for more information) but I will attempt to resolve that afterwards. My questions are: * How can I point Yi (and other programs) at the package database set up by nix-shell? * Am I ever meant to be running ‘cabal install’ from within nix-shell? * If I am meant to use ‘cabal install’, will nix do The Right Thing™ or will the binary escape to the global cabal bin store? You can find the default.nix I'm using for Yi at [2]. As usual, thank you for any help. [1]: http://ocharles.org.uk/blog/posts/2014-02-04-how-i-develop-with-nixos.html [2]: http://lpaste.net/103284 -- Mateusz K. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Unable to install NixOS unstable in UEFI system
It looks like you are trying to do a UEFI boot but not providing the correct partition mounted in /boot. https://wiki.archlinux.org/index.php/Gummiboot#Updating On Apr 27, 2014 2:15 PM, José Romildo Malaquias j.romi...@gmail.com wrote: Hello. When installation NixOS unstable on my x86_64 notebook, I am getting the error Failed to check file system type of /boot: No such file or directory The log file is attached, as well as the configuration I am using. A few months ago I had successfully installed NixOS unstalbe on this system without any major issues. I have followed the instructions in the manual at http://hydra.nixos.org/job/nixos/trunk-combined/nixos.manual.x86_64-linux/latest/download-by-type/doc/manual Any clues? Romildo ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Wireless carl9170 usb driver - missing firmware
Hi, I've downloaded the firmware for my Tplink TL-WN821N. Where do I place it and how I tell nixos this is where the firmware is? wget ' http://wireless.kernel.org/en/users/Drivers/carl9170?action=AttachFiledo=gettarget=carl9170-1.fw-1.9.9' -O carl9170-1.fw Dmesg has the message missing firmware, lsusb has the correct driver(carl9170) loaded, just missing the firmware. Aloha, RK. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
