Re: [Nix-dev] The Church of Suckless NixOS is looking for followers
Hello, I didn't read the long post, but based on the title it may be of your interest what I wrote years ago: nanonixos. http://viric.name/cgi-bin/nanonixos/doc/trunk/doc/home.wiki It's very outdated. Pick nixpkgs commits from those dates to make it work. It is a cross-built nixos for the Ben Nanonote. There is very little amount of code. It worked well enough for me. That may be way more "suckless" than you may be used to use. :) Regards, Lluís. On Fri, Mar 17, 2017 at 02:00:00PM +, Jan Malakhovski wrote: > > Brothers and Sisters! > > I think I reached the point of no-return w.r.t. not being able to > tolerate systemd on my machines any longer after systemd devs dropped > utmp. I don't want to replace finely matured portable UNIX utils > produced by The Old Gods for the sake of making a bunch of crazy people > into The New Gods. And, as it turns out, I'm not alone. > > And so we (I and a couple of anonymous friends) are pleased to announce > the establishment of The Church of Suckless NixOS ("SLNOS" for short). > > * Our common goal is to have fun (see below) and to get a NixOS system > that can run using only suckless tools [1]. > > * Some of us want to drop GRUB in favor of running on top of minimal > Xen payload on Coreboot firmware and isolate everything like in > QubesOS, but we are not united on that point at this point. (Yes, we > are aware of Heads:ROM, thank you, we are discussing all of this.) > > * We like LISP, but we don't think package expressions should be written > in LISP just for the sake of LISP. Nor do we like the bloated GNU > tools. GuixSD is out of question. > > For now we have a couple of proposals for the general NixOS community. > > # The Systemd part > > In short, we propose: > > (1) to reimplement full dependency tracking in nix (should replace > `strings-with-deps.nix`) with `toposort`, > > (2) return the old `system.jobs` under another name (for backwards > compatibility), but with most of that `system.systemd` now provides, > > (3) reimplement all the services we use with "system.jobs", > > (4) implement > > > { > # use OpenRC instead of systemd > system.initd = "openrc"; > } > > > and > > > { > # toposort `system.jobs` and render static > # init script for suckless.org initd > # (a page of nix code and a page of C code > # instead of systemd, yay!) > system.initd = "static"; > } > > > The (1) can then be used to get dependency tracking in `initrd` for free > too. > > As we see it, implementing the infrastructure (1)-(2) is a couple of > days of work, but reimplementing services (3) will need lots of effort > for very systemd specific, highly cgrouped and socket-activated > services, and (4) requires writing an alternative activation script. > > SLNOS will reimplement that for the services we use whenever you like it > or not (in fact, we already implemented a part of (1) because we wanted > encryption on networking `fileSystems` (LUKS over nbd) in initrd, but > never even proposed those changes to upstream because merging simple > `toposort` for `fileSystems` took a year). > > But we want to know how many people here are like-minded and would like > to join our SLNOS effort. > > The following template answers were proposed by our current members for > your convenience: > > * Poettering is my New God! PulseAudio! Avahi! Systemd! PulseAudio! > Avahi! Systemd! DBus for the Kernel! utmp is for old people! All > computers are laptops! All initds should include Udev, DBus, and do > DHCP and DNS-resolver, this is what initds are for! Merging this > upstream would be blasphemy! Burn it! Burn it with fire! > > * I don't care, but am willing to break UNIX-like part of GNU/Linux for > posterity. [2] > > If one of these templates covers your feelings you can reply-to-only-me > not to spam the list. > > If there are enough interested people we will organize a public SLNOS > repo thing as soon as we produce something substantial that can be read > by other people. > > General thoughts and pointers to anything in current or nearly-current > NixOS that might become a general snag for this effort are very welcome. > > If you have an idea for a simpler solution to the no-systemd problem you > are very welcome too. > > Bikeshedding of "`toposort` is too slow, not gonna work" and > "toposorting should be done at runtime" kinds are not welcome. Just go > and measure first. And it should not. Works fine for us. If it's slow on > your graphs, then just implement builtin `toposort` into nix. > > # The Nix part > > Or even better: generalize closure generation by splitting it into > `toposort` and `depends-on` relation on paths, expose both via builtins, > reimplement closure generation in lib. > > Then proceed to implementing half of `nix-store` commands on top of that > infrastructure instead, which would allow to customize `nix-store` with > nix code. For instance, want to GC as usual, but
[Nix-commits] [NixOS/nixpkgs] b288f0: amule: 2.3.1 -> 2.3.2
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: b288f0529c961f137194bf5c0ec532ca4e83077a https://github.com/NixOS/nixpkgs/commit/b288f0529c961f137194bf5c0ec532ca4e83077a Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/tools/networking/p2p/amule/default.nix R pkgs/tools/networking/p2p/amule/gcc47.patch Log Message: --- amule: 2.3.1 -> 2.3.2 (cherry picked from commit f77ae4e72607a658bdfd117b7e6f32aa4504befc) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] f77ae4: amule: 2.3.1 -> 2.3.2
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: f77ae4e72607a658bdfd117b7e6f32aa4504befc https://github.com/NixOS/nixpkgs/commit/f77ae4e72607a658bdfd117b7e6f32aa4504befc Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/tools/networking/p2p/amule/default.nix R pkgs/tools/networking/p2p/amule/gcc47.patch Log Message: --- amule: 2.3.1 -> 2.3.2 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] a2737b: vlock: improve eintr patch
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: a2737b1fdfc5e31285c709c10e9696226f35 https://github.com/NixOS/nixpkgs/commit/a2737b1fdfc5e31285c709c10e9696226f35 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-03-11 (Sat, 11 Mar 2017) Changed paths: M pkgs/misc/screensavers/vlock/eintr.patch Log Message: --- vlock: improve eintr patch Commit: 8ac134321b5c525bf33d6136528fa13b8d5f2707 https://github.com/NixOS/nixpkgs/commit/8ac134321b5c525bf33d6136528fa13b8d5f2707 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-03-11 (Sat, 11 Mar 2017) Changed paths: A pkgs/tools/compression/bsc/default.nix M pkgs/top-level/all-packages.nix Log Message: --- bsc: init at 3.1.0 Compressor. Commit: 7aa5effaf64b0cb97657bca8a54d038b714baa05 https://github.com/NixOS/nixpkgs/commit/7aa5effaf64b0cb97657bca8a54d038b714baa05 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-03-11 (Sat, 11 Mar 2017) Changed paths: A pkgs/tools/compression/lzham/default.nix M pkgs/top-level/all-packages.nix Log Message: --- lzham: init at 1.0 Compressor. Compare: https://github.com/NixOS/nixpkgs/compare/a5f4e2228922...7aa5effaf64b___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 1bd3fa: vlock: fix ENOPATCH
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 1bd3fa6210743928ca6a92f1d7f14a6d28a66232 https://github.com/NixOS/nixpkgs/commit/1bd3fa6210743928ca6a92f1d7f14a6d28a66232 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-03-04 (Sat, 04 Mar 2017) Changed paths: A pkgs/misc/screensavers/vlock/eintr.patch Log Message: --- vlock: fix ENOPATCH Thanks, @dtzWill. Signed-off-by: Lluís Batlle i Rossell <vi...@viric.name> ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] c2291a: vlock: fix EINTR handling
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: c2291aae442cea320aeb88f3fcd0cf36868df770 https://github.com/NixOS/nixpkgs/commit/c2291aae442cea320aeb88f3fcd0cf36868df770 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-03-03 (Fri, 03 Mar 2017) Changed paths: M pkgs/misc/screensavers/vlock/default.nix Log Message: --- vlock: fix EINTR handling Signed-off-by: Lluís Batlle i Rossell <vi...@viric.name> ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 9e7ce9: lzbench: init at 20170208
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 9e7ce9010c572fcaa41daf2ed821a01cf4f7335a https://github.com/NixOS/nixpkgs/commit/9e7ce9010c572fcaa41daf2ed821a01cf4f7335a Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-02-27 (Mon, 27 Feb 2017) Changed paths: A pkgs/tools/compression/lzbench/default.nix M pkgs/top-level/all-packages.nix Log Message: --- lzbench: init at 20170208 In-memory benchmark of several up-to-date compressors. Signed-off-by: Lluís Batlle i Rossell <vi...@viric.name> Commit: 40b9506139d00ed0d3536518daeec6bf45084b10 https://github.com/NixOS/nixpkgs/commit/40b9506139d00ed0d3536518daeec6bf45084b10 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-02-27 (Mon, 27 Feb 2017) Changed paths: M pkgs/tools/networking/megatools/default.nix Log Message: --- megatools: 1.9.97 -> 1.9.98 Signed-off-by: Lluís Batlle i Rossell <vi...@viric.name> Compare: https://github.com/NixOS/nixpkgs/compare/7992ce65fc46...40b9506139d0___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] e1874d: Revert "neomutt: update to 20170206"
Branch: refs/heads/release-16.09 Home: https://github.com/NixOS/nixpkgs Commit: e1874d0456b6c4a1259fcf218b5c996b6161d489 https://github.com/NixOS/nixpkgs/commit/e1874d0456b6c4a1259fcf218b5c996b6161d489 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-02-25 (Sat, 25 Feb 2017) Changed paths: M pkgs/applications/networking/mailreaders/neomutt/default.nix Log Message: --- Revert "neomutt: update to 20170206" This reverts commit cb6ed5341c7d7a4d90954a34cba99308f4a71c0f. Wrong branch. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 0c42ef: SDL2: fix creation of libSDL2main.a
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 0c42efd9d70774eafb47212967caada630335731 https://github.com/NixOS/nixpkgs/commit/0c42efd9d70774eafb47212967caada630335731 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-02-16 (Thu, 16 Feb 2017) Changed paths: M pkgs/development/libraries/SDL2/default.nix Log Message: --- SDL2: fix creation of libSDL2main.a It's required by a trigger rally update I will commit next. And other games use that too. Commit: 1e7da9ec78d11f586fc74747d77b17f91969a7ed https://github.com/NixOS/nixpkgs/commit/1e7da9ec78d11f586fc74747d77b17f91969a7ed Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-02-16 (Thu, 16 Feb 2017) Changed paths: M pkgs/games/trigger/default.nix Log Message: --- trigger: update to 0.6.5 Compare: https://github.com/NixOS/nixpkgs/compare/e62fe375757f...1e7da9ec78d1___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] e62fe3: zstd: update to 1.1.3
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: e62fe375757fb3175b859bb6dc171a23e15726c8 https://github.com/NixOS/nixpkgs/commit/e62fe375757fb3175b859bb6dc171a23e15726c8 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-02-16 (Thu, 16 Feb 2017) Changed paths: M pkgs/tools/compression/zstd/default.nix Log Message: --- zstd: update to 1.1.3 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 0cee46: brotli: update to 0.5.2
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 0cee46dd217641baf09a8dee40e80ff4c32d47d6 https://github.com/NixOS/nixpkgs/commit/0cee46dd217641baf09a8dee40e80ff4c32d47d6 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-02-16 (Thu, 16 Feb 2017) Changed paths: M pkgs/tools/compression/brotli/default.nix Log Message: --- brotli: update to 0.5.2 >From 0.3.0 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 838906: Updating shotcut to 17.02.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 8389060731e758708093722bf3e5099e51b0932b https://github.com/NixOS/nixpkgs/commit/8389060731e758708093722bf3e5099e51b0932b Author: Lluís Batlle <vi...@viric.name> Date: 2017-02-02 (Thu, 02 Feb 2017) Changed paths: M pkgs/applications/video/shotcut/default.nix Log Message: --- Updating shotcut to 17.02. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 576255: Adding nuttcp.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 57625514f4da97b1682abcc9883be319cc352293 https://github.com/NixOS/nixpkgs/commit/57625514f4da97b1682abcc9883be319cc352293 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-01-28 (Sat, 28 Jan 2017) Changed paths: A pkgs/tools/networking/nuttcp/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Adding nuttcp. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] aeb1df: Update scantailor
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: aeb1dff13d648c927c49a18fe0622e8574ca982c https://github.com/NixOS/nixpkgs/commit/aeb1dff13d648c927c49a18fe0622e8574ca982c Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-01-28 (Sat, 28 Jan 2017) Changed paths: M pkgs/applications/graphics/scantailor/default.nix Log Message: --- Update scantailor Commit: 20465bedee27c5944c1cbae91f642acddaa8a4a3 https://github.com/NixOS/nixpkgs/commit/20465bedee27c5944c1cbae91f642acddaa8a4a3 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-01-28 (Sat, 28 Jan 2017) Changed paths: M pkgs/applications/video/shotcut/default.nix M pkgs/development/libraries/mlt/qt-5.nix Log Message: --- Updating shotcut and melt. Commit: 91686f2d37273940b1631c070de692dc7337e8fe https://github.com/NixOS/nixpkgs/commit/91686f2d37273940b1631c070de692dc7337e8fe Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-01-28 (Sat, 28 Jan 2017) Changed paths: M pkgs/applications/video/cinelerra/default.nix Log Message: --- Add fixed cinelerra I don't know what version to choose Commit: 8d5b2e66bde8fa6e1f146b92ccb642dfd88e0a2f https://github.com/NixOS/nixpkgs/commit/8d5b2e66bde8fa6e1f146b92ccb642dfd88e0a2f Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2017-01-28 (Sat, 28 Jan 2017) Changed paths: M pkgs/applications/video/shotcut/default.nix M pkgs/development/libraries/mlt/qt-5.nix Log Message: --- Updating shotcut to 17.01 and fixing its jobs Compare: https://github.com/NixOS/nixpkgs/compare/fc83bdc14713...8d5b2e66bde8___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] bd9cd7: nixos: compress squashfs with xz
Branch: refs/heads/release-16.09 Home: https://github.com/NixOS/nixpkgs Commit: bd9cd796bb788eb4b67632cc76415b5f8b1d23c6 https://github.com/NixOS/nixpkgs/commit/bd9cd796bb788eb4b67632cc76415b5f8b1d23c6 Author: Franz Pletz <fpl...@fnordicwalking.de> Date: 2016-12-30 (Fri, 30 Dec 2016) Changed paths: M nixos/lib/make-squashfs.nix Log Message: --- nixos: compress squashfs with xz (cherry picked from commit 6de991bd95953493447e03cb87f181e4c4a547e6) Commit: 64eaa7eb2976141403b646f9b896607f4e879ad2 https://github.com/NixOS/nixpkgs/commit/64eaa7eb2976141403b646f9b896607f4e879ad2 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-12-30 (Fri, 30 Dec 2016) Changed paths: M nixos/lib/make-squashfs.nix Log Message: --- Tune mksquashfs for smaller isos. Bigger block size, more suitable for xz. (cherry picked from commit 897b10998b5953622c475e80518f2788155c91c0) Commit: 0ae95d808eafbf817a15744dd335941885496928 https://github.com/NixOS/nixpkgs/commit/0ae95d808eafbf817a15744dd335941885496928 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-12-30 (Fri, 30 Dec 2016) Changed paths: M nixos/modules/installer/cd-dvd/installation-cd-minimal.nix Log Message: --- Make the minimal iso not use profile/minimal, +vim The profile minimal has several drawbacks: no man pages, unusual 'dbus' lib that makes many X11 pieces to rebuild, etc. With xz compression in the squashfs, despite these additions, the iso is smaller than what it was in 16.09. (cherry picked from commit e0078b2cb536c3af0f820d484f46dc9b83547678) Compare: https://github.com/NixOS/nixpkgs/compare/bada11ea49d3...0ae95d808eaf___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 741213: zfs cannot be distributed. Disabling it in the iso...
Branch: refs/heads/release-16.09 Home: https://github.com/NixOS/nixpkgs Commit: 741213d7b3756a1d33ac39b2b626c297f2290aed https://github.com/NixOS/nixpkgs/commit/741213d7b3756a1d33ac39b2b626c297f2290aed Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-12-28 (Wed, 28 Dec 2016) Changed paths: M nixos/modules/profiles/base.nix Log Message: --- zfs cannot be distributed. Disabling it in the isos. It seems that it is a GPL violation to distribute zfs in the installation ISOs. https://sfconservancy.org/blog/2016/feb/25/zfs-and-linux/ If anyone knows the issue better and has a reason to reenable it legally, feel free to reenable it. I don't know much about it. (cherry picked from commit 33d07c7ea9f0d05d47dd4b41ded3b261380acfac) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 33d07c: zfs cannot be distributed. Disabling it in the iso...
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 33d07c7ea9f0d05d47dd4b41ded3b261380acfac https://github.com/NixOS/nixpkgs/commit/33d07c7ea9f0d05d47dd4b41ded3b261380acfac Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-12-28 (Wed, 28 Dec 2016) Changed paths: M nixos/modules/profiles/base.nix Log Message: --- zfs cannot be distributed. Disabling it in the isos. It seems that it is a GPL violation to distribute zfs in the installation ISOs. https://sfconservancy.org/blog/2016/feb/25/zfs-and-linux/ If anyone knows the issue better and has a reason to reenable it legally, feel free to reenable it. I don't know much about it. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 701596: Fixing the patch for icu for ARM.
Branch: refs/heads/release-16.09 Home: https://github.com/NixOS/nixpkgs Commit: 7015964e8d9a529b28e8df49cebd03e31b41d7b9 https://github.com/NixOS/nixpkgs/commit/7015964e8d9a529b28e8df49cebd03e31b41d7b9 Author: Lluís Batlle i Rossell <vi...@vicerveza.homeunix.net> Date: 2016-12-02 (Fri, 02 Dec 2016) Changed paths: M pkgs/development/libraries/icu/0001-Disable-LDFLAGSICUDT-for-Linux.patch Log Message: --- Fixing the patch for icu for ARM. The source file changed paths. (cherry picked from commit 19fd547a7fee2665ba562933cc385a5fbe0f63a9) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 19fd54: Fixing the patch for icu for ARM.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 19fd547a7fee2665ba562933cc385a5fbe0f63a9 https://github.com/NixOS/nixpkgs/commit/19fd547a7fee2665ba562933cc385a5fbe0f63a9 Author: Lluís Batlle i Rossell <vi...@vicerveza.homeunix.net> Date: 2016-12-02 (Fri, 02 Dec 2016) Changed paths: M pkgs/development/libraries/icu/0001-Disable-LDFLAGSICUDT-for-Linux.patch Log Message: --- Fixing the patch for icu for ARM. The source file changed paths. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] fb82e5: Disabling OABI_COMPAT on ARM platforms.
Branch: refs/heads/release-16.09 Home: https://github.com/NixOS/nixpkgs Commit: fb82e597108d3d7cc4630f3fb9e316bfdf764cd0 https://github.com/NixOS/nixpkgs/commit/fb82e597108d3d7cc4630f3fb9e316bfdf764cd0 Author: Lluís Batlle i Rossell <vi...@vicerveza.homeunix.net> Date: 2016-11-06 (Sun, 06 Nov 2016) Changed paths: M pkgs/top-level/platforms.nix Log Message: --- Disabling OABI_COMPAT on ARM platforms. Otherwise, systemd-logind fails to work because SECCOMP_FILTER cannot be enabled with OABI_COMPAT set. We don't need OABI_COMPAT at all on ARM, I guess. With this change, the rpi kernel boots fine for raspberrypi2. We discussed this change with Dezgeg. (cherry picked from commit a97db109a20697a14d3ca72a112d05cc0411ae8e) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] a97db1: Disabling OABI_COMPAT on ARM platforms.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: a97db109a20697a14d3ca72a112d05cc0411ae8e https://github.com/NixOS/nixpkgs/commit/a97db109a20697a14d3ca72a112d05cc0411ae8e Author: Lluís Batlle i Rossell <vi...@vicerveza.homeunix.net> Date: 2016-11-06 (Sun, 06 Nov 2016) Changed paths: M pkgs/top-level/platforms.nix Log Message: --- Disabling OABI_COMPAT on ARM platforms. Otherwise, systemd-logind fails to work because SECCOMP_FILTER cannot be enabled with OABI_COMPAT set. We don't need OABI_COMPAT at all on ARM, I guess. With this change, the rpi kernel boots fine for raspberrypi2. We discussed this change with Dezgeg. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] a65c90: Fixing irssi-otr after change of irssi ABI.
Branch: refs/heads/release-16.09 Home: https://github.com/NixOS/nixpkgs Commit: a65c90ba4329f3e3dc878eeb2e2716eee23b3230 https://github.com/NixOS/nixpkgs/commit/a65c90ba4329f3e3dc878eeb2e2716eee23b3230 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-10-05 (Wed, 05 Oct 2016) Changed paths: M pkgs/applications/networking/irc/irssi/otr/default.nix Log Message: --- Fixing irssi-otr after change of irssi ABI. I pick the change from this pull request: https://github.com/cryptodotis/irssi-otr/pull/60/ (cherry picked from commit d96c5e1fd6df28e0e2783f0d48bd081017f23355) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] d96c5e: Fixing irssi-otr after change of irssi ABI.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: d96c5e1fd6df28e0e2783f0d48bd081017f23355 https://github.com/NixOS/nixpkgs/commit/d96c5e1fd6df28e0e2783f0d48bd081017f23355 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-10-04 (Tue, 04 Oct 2016) Changed paths: M pkgs/applications/networking/irc/irssi/otr/default.nix Log Message: --- Fixing irssi-otr after change of irssi ABI. I pick the change from this pull request: https://github.com/cryptodotis/irssi-otr/pull/60/ ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 2f182c: Updating OCE to 0.17.2
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 2f182cebcc5d406f891d9bd82789af718a551cd5 https://github.com/NixOS/nixpkgs/commit/2f182cebcc5d406f891d9bd82789af718a551cd5 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-30 (Tue, 30 Aug 2016) Changed paths: M pkgs/development/libraries/opencascade/oce.nix Log Message: --- Updating OCE to 0.17.2 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 8d4de4: Updating mumble to 1.2.16.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 8d4de4fe4f4144a9794d4a94a092507313da6678 https://github.com/NixOS/nixpkgs/commit/8d4de4fe4f4144a9794d4a94a092507313da6678 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-27 (Sat, 27 Aug 2016) Changed paths: M pkgs/applications/networking/mumble/default.nix Log Message: --- Updating mumble to 1.2.16. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 8911ef: fossil: update to 1.35
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: 8911ef51326960af941b5bb5d57cd23d80583f0c https://github.com/NixOS/nixpkgs/commit/8911ef51326960af941b5bb5d57cd23d80583f0c Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-25 (Thu, 25 Aug 2016) Changed paths: M pkgs/applications/version-management/fossil/default.nix Log Message: --- fossil: update to 1.35 (cherry picked from commit 3aa8f23aec01220773773a633b25dab1831d2def) Fixing minimal conflicts. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 3aa8f2: fossil: update to 1.35
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 3aa8f23aec01220773773a633b25dab1831d2def https://github.com/NixOS/nixpkgs/commit/3aa8f23aec01220773773a633b25dab1831d2def Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-25 (Thu, 25 Aug 2016) Changed paths: M pkgs/applications/version-management/fossil/default.nix Log Message: --- fossil: update to 1.35 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 9ef3a5: Adding vlc plugin for firefox.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 9ef3a513793e42d828b823c7ecb1488ddc2b9706 https://github.com/NixOS/nixpkgs/commit/9ef3a513793e42d828b823c7ecb1488ddc2b9706 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-23 (Tue, 23 Aug 2016) Changed paths: M pkgs/applications/networking/browsers/firefox/wrapper.nix A pkgs/applications/video/vlc/plugin.nix M pkgs/top-level/all-packages.nix Log Message: --- Adding vlc plugin for firefox. I really wanted it to substitute the html5 player, or at least the direct player for mp4/webm files in firefox, but I couldn't make it work. The formats recognized by the firefox internal player were used in all cases. The plugin worked for formats unknown by firefox. https://support.mozilla.org/ca/questions/1089501 Nevertheless, as I wrote the nix recipe, I commit it. It may be of interest to someone else. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 523776: Updating mlt to 6.2.0
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: 5237768d62a40236d24fafbd9f4f97f3227399ce https://github.com/NixOS/nixpkgs/commit/5237768d62a40236d24fafbd9f4f97f3227399ce Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-18 (Thu, 18 Aug 2016) Changed paths: M pkgs/development/libraries/mlt/qt-5.nix Log Message: --- Updating mlt to 6.2.0 (cherry picked from commit 93d8ab8007102e0e4d7f23cf25bb353d1cc5bced) I checked with kdenlive people, and they say that we should always use the latest mlt possible; that it should not be any problem, and provide only improvements. (cherry picked from commit 9f9cac34d3d0461c5ad1365bd17dcb80a58591a7) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] b8e215: Making shotcut use qt5 (5.6), not qt55.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: b8e215fb50a9cc11e8156c3913a4c4f305d2fd2b https://github.com/NixOS/nixpkgs/commit/b8e215fb50a9cc11e8156c3913a4c4f305d2fd2b Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-18 (Thu, 18 Aug 2016) Changed paths: M pkgs/applications/video/shotcut/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Making shotcut use qt5 (5.6), not qt55. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] aae489: Shotcut builds, but wants jack1 libs on start.
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: aae489527af9c4365cfbcb8a863be59b6bd96051 https://github.com/NixOS/nixpkgs/commit/aae489527af9c4365cfbcb8a863be59b6bd96051 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-18 (Thu, 18 Aug 2016) Changed paths: M pkgs/applications/video/shotcut/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Shotcut builds, but wants jack1 libs on start. (cherry picked from commit 5b3c885b35390cbd5e1d8707fb44604e5f9bf60d) Commit: f3edc3cd8c92b9ac7ac53bd3dcfc779e997ccd91 https://github.com/NixOS/nixpkgs/commit/f3edc3cd8c92b9ac7ac53bd3dcfc779e997ccd91 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-18 (Thu, 18 Aug 2016) Changed paths: M pkgs/applications/video/shotcut/default.nix Log Message: --- More dependencies to shotcut (cherry picked from commit e31951cb88c574e5fd043e74f5530329b428a600) Commit: a898588dd6a7174eaa0bf10adba98b16574b437d https://github.com/NixOS/nixpkgs/commit/a898588dd6a7174eaa0bf10adba98b16574b437d Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-18 (Thu, 18 Aug 2016) Changed paths: M pkgs/applications/video/shotcut/default.nix Log Message: --- Fixing build of shotcut, after cherrypicks from master. Compare: https://github.com/NixOS/nixpkgs/compare/4e2a6fd28816...a898588dd6a7___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 4e2a6f: Removing old traces of broken=true in shotcut
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: 4e2a6fd28816e5171aa73c2fc22bae617cf3a9da https://github.com/NixOS/nixpkgs/commit/4e2a6fd28816e5171aa73c2fc22bae617cf3a9da Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-18 (Thu, 18 Aug 2016) Changed paths: M pkgs/applications/video/shotcut/default.nix Log Message: --- Removing old traces of broken=true in shotcut ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 5b3c88: Shotcut builds, but wants jack1 libs on start.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 5b3c885b35390cbd5e1d8707fb44604e5f9bf60d https://github.com/NixOS/nixpkgs/commit/5b3c885b35390cbd5e1d8707fb44604e5f9bf60d Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-17 (Wed, 17 Aug 2016) Changed paths: M pkgs/applications/video/shotcut/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Shotcut builds, but wants jack1 libs on start. Commit: e31951cb88c574e5fd043e74f5530329b428a600 https://github.com/NixOS/nixpkgs/commit/e31951cb88c574e5fd043e74f5530329b428a600 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-18 (Thu, 18 Aug 2016) Changed paths: M pkgs/applications/video/shotcut/default.nix Log Message: --- More dependencies to shotcut Commit: 762a11a2760cf91869f6af0e58e329e7ae945a8c https://github.com/NixOS/nixpkgs/commit/762a11a2760cf91869f6af0e58e329e7ae945a8c Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-18 (Thu, 18 Aug 2016) Changed paths: M pkgs/applications/video/shotcut/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Updating and fixing shotcut. Compare: https://github.com/NixOS/nixpkgs/compare/eb6f0c06efd1...762a11a2760c___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 9f9cac: Updating mlt to 6.2.0
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 9f9cac34d3d0461c5ad1365bd17dcb80a58591a7 https://github.com/NixOS/nixpkgs/commit/9f9cac34d3d0461c5ad1365bd17dcb80a58591a7 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-17 (Wed, 17 Aug 2016) Changed paths: M pkgs/development/libraries/mlt/qt-5.nix Log Message: --- Updating mlt to 6.2.0 (cherry picked from commit 93d8ab8007102e0e4d7f23cf25bb353d1cc5bced) I checked with kdenlive people, and they say that we should always use the latest mlt possible; that it should not be any problem, and provide only improvements. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 2effe4: Adding kdenlive for kde5
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 2effe4609dfe7edf7e45474c692461688337342a https://github.com/NixOS/nixpkgs/commit/2effe4609dfe7edf7e45474c692461688337342a Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-12 (Fri, 12 Aug 2016) Changed paths: A pkgs/desktops/kde-5/applications-15.12/kdenlive.nix M pkgs/desktops/kde-5/applications/default.nix A pkgs/desktops/kde-5/applications/kdenlive.nix Log Message: --- Adding kdenlive for kde5 (cherry picked from commit e17bc0b871db241434c05d3079bd2790359cd720) Commit: ca6dedf0eeb64b80bca27c2ad5f04da1d75d5c2a https://github.com/NixOS/nixpkgs/commit/ca6dedf0eeb64b80bca27c2ad5f04da1d75d5c2a Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-12 (Fri, 12 Aug 2016) Changed paths: R pkgs/desktops/kde-5/applications-15.12/kdenlive.nix Log Message: --- Remove spurious kdenlive file Commit: 2d933d9d986b39b2752b89561b67754c37edd8d1 https://github.com/NixOS/nixpkgs/commit/2d933d9d986b39b2752b89561b67754c37edd8d1 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-12 (Fri, 12 Aug 2016) Changed paths: M pkgs/desktops/kde-5/applications/kdenlive.nix Log Message: --- Making kdenlive find kinit in PATH Commit: 17f0cce4452e7c836160a15c157a7609efd4160a https://github.com/NixOS/nixpkgs/commit/17f0cce4452e7c836160a15c157a7609efd4160a Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-12 (Fri, 12 Aug 2016) Changed paths: M pkgs/development/libraries/mlt/qt-5.nix Log Message: --- Adding the mlt version that matches kdenlive 15.12. (cherry picked from commit 008f88ae6f0aa43cf0dc4e36f059ee03e1a0b99b) Commit: 2045b40b1061f24e9a51e1f312c9d9e131b8b43b https://github.com/NixOS/nixpkgs/commit/2045b40b1061f24e9a51e1f312c9d9e131b8b43b Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-12 (Fri, 12 Aug 2016) Changed paths: M pkgs/desktops/kde-5/applications/kdenlive.nix Log Message: --- Trying to fix the latest kdenlive Compare: https://github.com/NixOS/nixpkgs/compare/b1817fa8a3e8...2045b40b1061___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 93d8ab: Updating mlt to 6.2.0
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: 93d8ab8007102e0e4d7f23cf25bb353d1cc5bced https://github.com/NixOS/nixpkgs/commit/93d8ab8007102e0e4d7f23cf25bb353d1cc5bced Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-06 (Sat, 06 Aug 2016) Changed paths: M pkgs/development/libraries/mlt/qt-5.nix Log Message: --- Updating mlt to 6.2.0 Commit: e17bc0b871db241434c05d3079bd2790359cd720 https://github.com/NixOS/nixpkgs/commit/e17bc0b871db241434c05d3079bd2790359cd720 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-06 (Sat, 06 Aug 2016) Changed paths: M pkgs/desktops/kde-5/applications-15.12/default.nix A pkgs/desktops/kde-5/applications-15.12/kdenlive.nix Log Message: --- Adding kdenlive for kde5 Commit: 06b1f2f3aa1177eea11d126c581822619c7f4984 https://github.com/NixOS/nixpkgs/commit/06b1f2f3aa1177eea11d126c581822619c7f4984 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-06 (Sat, 06 Aug 2016) Changed paths: M pkgs/desktops/kde-5/applications-15.12/kdenlive.nix Log Message: --- More pieces to kdenlive (copied from archlinux) Commit: 29ebb13afba9a89279d88bb98fbabcd99d06cf0c https://github.com/NixOS/nixpkgs/commit/29ebb13afba9a89279d88bb98fbabcd99d06cf0c Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-06 (Sat, 06 Aug 2016) Changed paths: M pkgs/development/libraries/mlt/qt-5.nix Log Message: --- Revert "Updating mlt to 6.2.0" This reverts commit 93d8ab8007102e0e4d7f23cf25bb353d1cc5bced. Commit: 008f88ae6f0aa43cf0dc4e36f059ee03e1a0b99b https://github.com/NixOS/nixpkgs/commit/008f88ae6f0aa43cf0dc4e36f059ee03e1a0b99b Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-07 (Sun, 07 Aug 2016) Changed paths: M pkgs/development/libraries/mlt/qt-5.nix Log Message: --- Adding the mlt version that matches kdenlive 15.12. Commit: da1bf5fc711c7ce179d3f64cfb9b3abc4adbc42e https://github.com/NixOS/nixpkgs/commit/da1bf5fc711c7ce179d3f64cfb9b3abc4adbc42e Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-07 (Sun, 07 Aug 2016) Changed paths: M pkgs/desktops/kde-5/applications-15.12/kdenlive.nix Log Message: --- Making kdenlive find kinit in PATH Commit: 1ec1a7c71f1394272855c91c1db6b3c76d11ab9e https://github.com/NixOS/nixpkgs/commit/1ec1a7c71f1394272855c91c1db6b3c76d11ab9e Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-08-07 (Sun, 07 Aug 2016) Changed paths: M pkgs/desktops/kde-5/applications-15.12/default.nix A pkgs/desktops/kde-5/applications-15.12/kdenlive.nix M pkgs/development/libraries/mlt/qt-5.nix Log Message: --- Adding kdenlive for kde-5 (15.12). Merging the branch where I added it, which has some steps forward/backward. The changes for master (applications-16.04) are slightly different, and although I tried to port it there, kdenlive just crashes on start. Someone should port it there. Compare: https://github.com/NixOS/nixpkgs/compare/4c09ea7e3d2f...1ec1a7c71f13___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] d7dca6: Adding psutils.
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: d7dca678a97241884bd7917895492c064dab63cc https://github.com/NixOS/nixpkgs/commit/d7dca678a97241884bd7917895492c064dab63cc Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-07-27 (Wed, 27 Jul 2016) Changed paths: A pkgs/tools/typesetting/psutils/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Adding psutils. Have we lived without psnup so many years? Incredible. (cherry picked from commit 03f368ca93b86a6b695fef5bad6f800fbee5fb6a) Commit: ccd1f37ffe583e26061641aa90e7c7dba0c6447e https://github.com/NixOS/nixpkgs/commit/ccd1f37ffe583e26061641aa90e7c7dba0c6447e Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-07-27 (Wed, 27 Jul 2016) Changed paths: M pkgs/tools/typesetting/psutils/default.nix Log Message: --- Fix psutils licence. (cherry picked from commit e412f2199a8e31d22c0ffa178c29c97c8e308983) Compare: https://github.com/NixOS/nixpkgs/compare/8541088132cf...ccd1f37ffe58___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] e412f2: Fix psutils licence.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: e412f2199a8e31d22c0ffa178c29c97c8e308983 https://github.com/NixOS/nixpkgs/commit/e412f2199a8e31d22c0ffa178c29c97c8e308983 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-07-27 (Wed, 27 Jul 2016) Changed paths: M pkgs/tools/typesetting/psutils/default.nix Log Message: --- Fix psutils licence. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 03f368: Adding psutils.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 03f368ca93b86a6b695fef5bad6f800fbee5fb6a https://github.com/NixOS/nixpkgs/commit/03f368ca93b86a6b695fef5bad6f800fbee5fb6a Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-07-27 (Wed, 27 Jul 2016) Changed paths: A pkgs/tools/typesetting/psutils/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Adding psutils. Have we lived without psnup so many years? Incredible. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 757901: perf: depend on libiberty to get c++ demangling.
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: 757901bc6dbc4fd4dadb1d31bd4e58bd688f357e https://github.com/NixOS/nixpkgs/commit/757901bc6dbc4fd4dadb1d31bd4e58bd688f357e Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-07-21 (Thu, 21 Jul 2016) Changed paths: M pkgs/os-specific/linux/kernel/perf.nix Log Message: --- perf: depend on libiberty to get c++ demangling. (cherry picked from commit dd02b6f11894eaafb309fb96652c12295f82304c) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] dd02b6: perf: depend on libiberty to get c++ demangling.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: dd02b6f11894eaafb309fb96652c12295f82304c https://github.com/NixOS/nixpkgs/commit/dd02b6f11894eaafb309fb96652c12295f82304c Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-07-21 (Thu, 21 Jul 2016) Changed paths: M pkgs/os-specific/linux/kernel/perf.nix Log Message: --- perf: depend on libiberty to get c++ demangling. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 3beaca: vm/rpm/rpm-closure.pl: make it deterministic
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: 3beaca99cbf9f185d72584b81a0733a2e1e0b693 https://github.com/NixOS/nixpkgs/commit/3beaca99cbf9f185d72584b81a0733a2e1e0b693 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-07-21 (Thu, 21 Jul 2016) Changed paths: M pkgs/build-support/vm/rpm/rpm-closure.pl Log Message: --- vm/rpm/rpm-closure.pl: make it deterministic Some recent perl version introduced "keys" to return the keys in random order. As some of the packages are solved by "provides" and based on the order, this randomness affects what packages get into the closure. This problem may be in other nix perl scripts. (cherry picked from commit 202ebf794cbd5ea293170f71999bc4e8f788779e) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 24353b: Adding intel-gpu-tools to xorg.
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: 24353b91f912c4f6ec4fe0f527b413841de15c13 https://github.com/NixOS/nixpkgs/commit/24353b91f912c4f6ec4fe0f527b413841de15c13 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-07-20 (Wed, 20 Jul 2016) Changed paths: M pkgs/servers/x11/xorg/default.nix M pkgs/servers/x11/xorg/extra.list M pkgs/servers/x11/xorg/overrides.nix M pkgs/top-level/all-packages.nix Log Message: --- Adding intel-gpu-tools to xorg. (cherry picked from commit 13fc6e56fe8012936710a0475e2fd833acc3d3fc) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 13fc6e: Adding intel-gpu-tools to xorg.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 13fc6e56fe8012936710a0475e2fd833acc3d3fc https://github.com/NixOS/nixpkgs/commit/13fc6e56fe8012936710a0475e2fd833acc3d3fc Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-07-20 (Wed, 20 Jul 2016) Changed paths: M pkgs/servers/x11/xorg/default.nix M pkgs/servers/x11/xorg/extra.list M pkgs/servers/x11/xorg/overrides.nix M pkgs/top-level/all-packages.nix Log Message: --- Adding intel-gpu-tools to xorg. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] Raspberry-Pi NixOS
On Tue, Jul 19, 2016 at 11:53:59PM +0200, Tomas Hlavaty wrote: > Lluís Batlle i Rossell <vi...@viric.name> writes: > > The device tree blob should be built by the kernel, like with pi and pi2, > > isn't it? > > This is the kernel which works for me and is taken from > raspberry-firmware/boot: > > Linux version 4.4.13-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 > (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #894 SMP Mon Jun 13 > 13:13:27 BST 2016 > > and the corresponding device tree is bcm2710-rpi-3-b.dtb. > > This looks like the same kernel version in > pkgs/os-specific/linux/kernel/linux-rpi.nix (modDirVersion = "4.4.13"; > tag = "1.20160620-1") > > Are you saying that this is not good enough? > > What works: If I copy files from raspberry-firmware/boot to /boot, rpi3 > starts fine. These are the files I have in /boot: > > $ ls -al /boot > -rwxr-xr-x 1 root root 13221 Jun 18 22:31 bcm2708-rpi-b.dtb > -rwxr-xr-x 1 root root 13484 Jun 18 22:31 bcm2708-rpi-b-plus.dtb > -rwxr-xr-x 1 root root 13257 Jun 18 22:31 bcm2708-rpi-cm.dtb > -rwxr-xr-x 1 root root 14567 Jun 18 22:31 bcm2709-rpi-2-b.dtb > -rwxr-xr-x 1 root root 15237 Jun 18 22:31 bcm2710-rpi-3-b.dtb > -rwxr-xr-x 1 root root 17932 Jun 18 22:31 bootcode.bin > -rwxr-xr-x 1 root root 165 Jul 19 22:46 cmdline.txt > -rwxr-xr-x 1 root root1369 Jan 11 2016 config.txt > -rwxr-xr-x 1 root root2504 Jun 23 20:42 fixup_cd.dat > -rwxr-xr-x 1 root root6482 Jun 23 20:42 fixup.dat > -rwxr-xr-x 1 root root9717 Jun 23 20:42 fixup_db.dat > -rwxr-xr-x 1 root root9717 Jun 23 20:42 fixup_x.dat > -rwxr-xr-x 1 root root 4224232 Jun 18 22:31 kernel7.img > drwxr-xr-x 2 root root8192 Jun 18 22:31 overlays > -rwxr-xr-x 1 root root 617432 Jun 23 20:42 start_cd.elf > -rwxr-xr-x 1 root root 4926264 Jun 23 20:42 start_db.elf > -rwxr-xr-x 1 root root 2746552 Jun 23 20:42 start.elf > -rwxr-xr-x 1 root root 3877720 Jun 23 20:42 start_x.elf > > I don't see, why raspberrypi/builder.sh creates defaultgeneration, > initrd and nixos-init files in /boot. It actually seems to me, that > initrd should not be there at all for the boot to work. > > raspberrypi/builder.sh doesn't create fixup_x.dat, which is in the list > above; but I haven't tried booting without it. > > Although pkgs/os-specific/linux/kernel/linux-rpi.nix copies DTB files, > it renames them to something that looks wrong and also it does not copy > them to /boot at all: > > # I am not sure if all of these are correct... > copyDTB bcm2708-rpi-b.dtb bcm2835-rpi-a.dtb > copyDTB bcm2708-rpi-b.dtb bcm2835-rpi-b.dtb > copyDTB bcm2708-rpi-b.dtb bcm2835-rpi-b-rev2.dtb > copyDTB bcm2708-rpi-b-plus.dtb bcm2835-rpi-a-plus.dtb > copyDTB bcm2708-rpi-b-plus.dtb bcm2835-rpi-b-plus.dtb > copyDTB bcm2708-rpi-b-plus.dtb bcm2835-rpi-zero.dtb > copyDTB bcm2708-rpi-cm.dtb bcm2835-rpi-cm.dtb > copyDTB bcm2709-rpi-2-b.dtb bcm2836-rpi-2-b.dtb > copyDTB bcm2710-rpi-3-b.dtb bcm2837-rpi-3-b.dtb > > I looks like the files in raspberry-firmware/boot should work on any rpi > version so we should probably immitate that somehow in nixos and at > least get it to work out of the box even if we just take the precompiled > files from raspberrypi-firmware/boot and improve that later. I don't remember any of the details. I'm using it in rpi2 just fine. I could forget some file, and I may have written code that is fit just for a very specific kernel version. Maybe it has all changed in 4.4. The relevant detail that I remember is that the kernel recipe is told to build the DTB, so I think that you should not need any dtb from the firmwarefiles/boot. Regards, Lluís. -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Raspberry-Pi NixOS
The device tree blob should be built by the kernel, like with pi and pi2, isn't it? Regards, Lluís. On Mon, Jul 18, 2016 at 10:40:09PM +0200, Tomas Hlavaty wrote: > > Tomas Hlavatywrites: > > - pkgs/os-specific/linux/firmware/raspberrypi/default.nix needs newer > > rev as the current one is pre-rpi3. > > > > - pkgs/os-specific/linux/kernel/linux-rpi.nix needs newer kernel, > > probably for the same reason as above. I tried 4.4.13-v7. > > Tuomas Tynkkynen has done that already and looking at the git log, he's > progressed quite far. > > commit 36f4a8a485732da98e1fcf40945ecda305677579 > Author: Tuomas Tynkkynen > Date: Sun Jun 19 22:49:36 2016 +0300 > > sd-image-armv7l-multiplatform.nix: Preliminary Raspberry Pi 2/3 support > > - RPi3 successfully gets to U-Boot, but then fails to boot the kernel > due to a missing device tree file. This should get added to the 4.8 > kernel release once this patch is merged: > https://lkml.org/lkml/2016/6/1/841 > - RPi2 is not tested, but it should successfully boot the NixOS image. > > Could not the device tree be taken from > raspberrypifw/boot/bcm2710-rpi-3-b.dtb? > > I will build nixpkgs HEAD, lets see. > > Tomas > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 19f3e0: ffmpeg-full: 2.8.5 -> 3.0
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: 19f3e09c061cc397af50efb9efabcad77ca8a447 https://github.com/NixOS/nixpkgs/commit/19f3e09c061cc397af50efb9efabcad77ca8a447 Author: Anthony Cowley <acow...@gmail.com> Date: 2016-06-18 (Sat, 18 Jun 2016) Changed paths: M pkgs/development/libraries/ffmpeg-full/default.nix Log Message: --- ffmpeg-full: 2.8.5 -> 3.0 Also changes the homepage URL to https. (cherry picked from commit 2f6f3c7b55a3aa1e07a7d936bbad28dea05925eb) Commit: f827da01368989145128c216cdb30dc1157e581c https://github.com/NixOS/nixpkgs/commit/f827da01368989145128c216cdb30dc1157e581c Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-06-18 (Sat, 18 Jun 2016) Changed paths: M pkgs/development/libraries/x264/default.nix Log Message: --- Update x264 to a recent snapshot (1,5 years update) (cherry picked from commit 3078537b6afc4256460b2ba5c38d60acb77445a2) Commit: 3d5ef21601bd5784011c7cb1f3e9aae094c45937 https://github.com/NixOS/nixpkgs/commit/3d5ef21601bd5784011c7cb1f3e9aae094c45937 Author: Anthony Cowley <acow...@gmail.com> Date: 2016-06-18 (Sat, 18 Jun 2016) Changed paths: M pkgs/development/libraries/x265/default.nix Log Message: --- x265: 1.7 -> 1.9 Unblocks #13822 (cherry picked from commit 6bc1aed8739d77c7746b863140400c3a273c50d5) Commit: 15235f5ae36ec5c8df9c2ab88d1a4e4b4fd4fcd4 https://github.com/NixOS/nixpkgs/commit/15235f5ae36ec5c8df9c2ab88d1a4e4b4fd4fcd4 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-06-18 (Sat, 18 Jun 2016) Changed paths: M pkgs/development/libraries/x265/default.nix Log Message: --- x265: enable parallel build (cherry picked from commit 726ed32bfd983203a5d50729ecb0cb15e9cd5048) Commit: 256ebc4de1bc6920b1635a56a942f012bb65cca6 https://github.com/NixOS/nixpkgs/commit/256ebc4de1bc6920b1635a56a942f012bb65cca6 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-06-18 (Sat, 18 Jun 2016) Changed paths: M pkgs/development/libraries/ffmpeg-full/default.nix Log Message: --- Update ffmpeg-full to 3.0.2 (cherry picked from commit 3a61de4e69431c667e6b900364a4229cd12f7019) Compare: https://github.com/NixOS/nixpkgs/compare/af412f29c817...256ebc4de1bc___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] Malicious installation methods
On Fri, Jun 17, 2016 at 03:17:59PM +0200, Adrien Devresse wrote: > But without even considering that, "curl-pipe-bash" will cause your > sysadmin to blow a fuse or heartbreak in most companies / environments. > And for very good reasons. That is not very different from a "make install" of a downloaded tarball, though. :) ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Raspberry-Pi NixOS
Go ahead. I use nixos in the pi2 since pre-15.09. Now with 16.03. On Wed, Jun 15, 2016 at 02:26:51PM +0200, Bas van Dijk wrote: > I'm also really interested in getting NixOS to run on Raspberry-Pi 2/3. At > LumiGuide we have many Raspberry Pi's deployed in the field running Debian. > It would be great to replace that with NixOS like all our other machines. > Op 15 jun. 2016 2:01 p.m. schreef "Matthias Beyer": > > > Hi viric, > > Hi dezgeg, > > > > I just found the wiki page on nixos on the raspberry[0], where you two are > > referenced as creators. > > > > May I ask whether this is still present? I plan on buying a Raspberry Pi > > model > > B, 3rd generation and build a small handheld linux terminal (see [1]) with > > it, > > but I really want to run nixos on it and be able to deploy software for it > > from > > my other devices (mainly because of recompilation times - or are there a > > nixpkgs > > substitutes for ARM available?). > > > > So my question is basically: Is this article still relevant to the current > > situation, as the article is almost one year old? > > > > Of course I will document my experience and share it with the NixOS > > community > > after I created the device. > > > > [0]: https://nixos.org/wiki/Raspberry_Pi_2 > > [1]: > > http://makezine.com/projects/build-raspberry-pi-powered-linux-laptop-that-fits-your-pocket/ > > > > -- > > Mit freundlichen Grüßen, > > Kind regards, > > Matthias Beyer > > > > Proudly sent with mutt. > > Happily signed with gnupg. > > > > ___ > > nix-dev mailing list > > nix-dev@lists.science.uu.nl > > http://lists.science.uu.nl/mailman/listinfo/nix-dev > > > > -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Raspberry-Pi NixOS
I don't know about the article... but I still use a pi2 as my main home server, with nixos, with 16.03. On Wed, Jun 15, 2016 at 02:01:06PM +0200, Matthias Beyer wrote: > Hi viric, > Hi dezgeg, > > I just found the wiki page on nixos on the raspberry[0], where you two are > referenced as creators. > > May I ask whether this is still present? I plan on buying a Raspberry Pi model > B, 3rd generation and build a small handheld linux terminal (see [1]) with it, > but I really want to run nixos on it and be able to deploy software for it > from > my other devices (mainly because of recompilation times - or are there a > nixpkgs > substitutes for ARM available?). > > So my question is basically: Is this article still relevant to the current > situation, as the article is almost one year old? > > Of course I will document my experience and share it with the NixOS community > after I created the device. > > [0]: https://nixos.org/wiki/Raspberry_Pi_2 > [1]: > http://makezine.com/projects/build-raspberry-pi-powered-linux-laptop-that-fits-your-pocket/ > > -- > Mit freundlichen Grüßen, > Kind regards, > Matthias Beyer > > Proudly sent with mutt. > Happily signed with gnupg. -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 93912d: Adding nvenc support to ffmpeg (default off)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 93912d99d23fa964d4dadcda9a90c8fbe7bb1faa https://github.com/NixOS/nixpkgs/commit/93912d99d23fa964d4dadcda9a90c8fbe7bb1faa Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-06-14 (Tue, 14 Jun 2016) Changed paths: M pkgs/development/libraries/ffmpeg-full/default.nix A pkgs/development/libraries/nvidia-video-sdk/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Adding nvenc support to ffmpeg (default off) I add the nvidia-video-sdk header files, required to make it work. You have to set nvenct=true to ffmpeg-full and nonfreeLicensing=true to ffmpeg-full to use this. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 268fed: Updating goPackages go-fuse/mtpfs + libmtp to late...
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 268fedbda33a0afa056eac97c6e04ccd0d21027f https://github.com/NixOS/nixpkgs/commit/268fedbda33a0afa056eac97c6e04ccd0d21027f Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-06-04 (Sat, 04 Jun 2016) Changed paths: M pkgs/development/libraries/libmtp/default.nix M pkgs/top-level/go-packages.nix Log Message: --- Updating goPackages go-fuse/mtpfs + libmtp to latest libmtp to 1.1.11, and the go packages to latest master. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] c09bee: Slight improvements to neverball package
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: c09bee391a966d19aae33c5a512a8d6d93912d3d https://github.com/NixOS/nixpkgs/commit/c09bee391a966d19aae33c5a512a8d6d93912d3d Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-05-31 (Tue, 31 May 2016) Changed paths: M pkgs/games/neverball/default.nix Log Message: --- Slight improvements to neverball package ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 0dae82: Allow not rebasing in cygwin stdenv.
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: 0dae829da76bc0144bd4bfdfe685f00a7c59b2e0 https://github.com/NixOS/nixpkgs/commit/0dae829da76bc0144bd4bfdfe685f00a7c59b2e0 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-05-20 (Fri, 20 May 2016) Changed paths: M pkgs/stdenv/cygwin/rebase-i686.sh M pkgs/stdenv/cygwin/rebase-x86_64.sh Log Message: --- Allow not rebasing in cygwin stdenv. This changes cygwin stdenv, but I don't think it will hurt much people. This allows mkDerivation to get "dontRebase=true" to skip the usual cygwin rebase. This is required, if we are using this stdenv to build DLLs for win32 inside x86_64-cygwin, because /bin/rebase crashes at finding an arch mismatch. Additionally, we don't need any rebase for libraries built by visual studio and meant for visual studio (my use case). I'm using nix in x86_64-cygwin to build libraries with visual studio, both for x86_64 and x86. (cherry picked from commit f6f5c185ca533e52b6f0e4042971e039775dd970) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] f6f5c1: Allow not rebasing in cygwin stdenv.
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: f6f5c185ca533e52b6f0e4042971e039775dd970 https://github.com/NixOS/nixpkgs/commit/f6f5c185ca533e52b6f0e4042971e039775dd970 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-05-20 (Fri, 20 May 2016) Changed paths: M pkgs/stdenv/cygwin/rebase-i686.sh M pkgs/stdenv/cygwin/rebase-x86_64.sh Log Message: --- Allow not rebasing in cygwin stdenv. This changes cygwin stdenv, but I don't think it will hurt much people. This allows mkDerivation to get "dontRebase=true" to skip the usual cygwin rebase. This is required, if we are using this stdenv to build DLLs for win32 inside x86_64-cygwin, because /bin/rebase crashes at finding an arch mismatch. Additionally, we don't need any rebase for libraries built by visual studio and meant for visual studio (my use case). I'm using nix in x86_64-cygwin to build libraries with visual studio, both for x86_64 and x86. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] b1ffcd: Adding libuuid (libblkid) to lvm2.
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: b1ffcd19d1e3b8eae782439ea4ad2fb059bfeef2 https://github.com/NixOS/nixpkgs/commit/b1ffcd19d1e3b8eae782439ea4ad2fb059bfeef2 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-05-09 (Mon, 09 May 2016) Changed paths: M pkgs/os-specific/linux/lvm2/default.nix Log Message: --- Adding libuuid (libblkid) to lvm2. It wants it to detect if there are filesystems present in block devices, in case of pvcreate. Otherwise it complaints "lvm built without blkid support" and lacks the feature of detecting/wiping. (cherry picked from commit 2f35e223b1e5dab2470c928c85e7119c7cbeb38c) I fixed an easy conflict. Commit: 8fd1ed762119601a75cda9fef79fb93c3da43e58 https://github.com/NixOS/nixpkgs/commit/8fd1ed762119601a75cda9fef79fb93c3da43e58 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-05-09 (Mon, 09 May 2016) Changed paths: M pkgs/build-support/vm/default.nix Log Message: --- vm: allow overriding QEMU_OPTS / memSize for images. It's nice to be able to create disk images with -smp 4 in qemu. (cherry picked from commit 635c99ce878d5009eaf21da80319d5426a534cee) Commit: 6e4a8bea9e1acaace67b1199bbed1b525cd6051b https://github.com/NixOS/nixpkgs/commit/6e4a8bea9e1acaace67b1199bbed1b525cd6051b Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-05-09 (Mon, 09 May 2016) Changed paths: M pkgs/build-support/vm/default.nix Log Message: --- Making vm's qemu cache=unsafe. Faster. I don't think it's unsafe, if it's meant for nix expressions. (cherry picked from commit ab93f8c137ac8d7d67f42c24aa3844f6cd233d2e) Commit: 1cfa84a52d5600e86d113209fd48ba8e3cb6dde2 https://github.com/NixOS/nixpkgs/commit/1cfa84a52d5600e86d113209fd48ba8e3cb6dde2 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-05-09 (Mon, 09 May 2016) Changed paths: M pkgs/build-support/vm/default.nix Log Message: --- Making vm's interactive shell handle the terminal well. (cherry picked from commit e21dd19168a726f749a00bc96950ce2e09f9eecd) Compare: https://github.com/NixOS/nixpkgs/compare/165781b5298a...1cfa84a52d56___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 165781: Fixing nfsd service, wait on local-fs.
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: 165781b5298a031f127b8447f829c1f5be27bc93 https://github.com/NixOS/nixpkgs/commit/165781b5298a031f127b8447f829c1f5be27bc93 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-05-09 (Mon, 09 May 2016) Changed paths: M nixos/modules/services/network-filesystems/nfsd.nix Log Message: --- Fixing nfsd service, wait on local-fs. Otherwise, mountd was started exporting directories before local-fs was ready, and it failed to start nfsd on missing fs. (cherry picked from commit 9f6afb7d78771f283b84d4dbdc5c5a08291a738c) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 74139a: Fixing stunt-rally 2.6 (adding newer bullet)
Branch: refs/heads/release-16.03 Home: https://github.com/NixOS/nixpkgs Commit: 74139a6b585d2b8bd0922ca6b0baed79f2f5cc66 https://github.com/NixOS/nixpkgs/commit/74139a6b585d2b8bd0922ca6b0baed79f2f5cc66 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-05-08 (Sun, 08 May 2016) Changed paths: A pkgs/development/libraries/bullet/bullet283.nix M pkgs/games/stuntrally/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Fixing stunt-rally 2.6 (adding newer bullet) (cherry picked from commit f0c503593fd9d968407a94e26f9ef24279bf8012) There were some weird conflicts. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] f0c503: Fixing stunt-rally 2.6 (adding newer bullet)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: f0c503593fd9d968407a94e26f9ef24279bf8012 https://github.com/NixOS/nixpkgs/commit/f0c503593fd9d968407a94e26f9ef24279bf8012 Author: Lluís Batlle i Rossell <vi...@viric.name> Date: 2016-05-08 (Sun, 08 May 2016) Changed paths: A pkgs/development/libraries/bullet/bullet283.nix M pkgs/games/stuntrally/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Fixing stunt-rally 2.6 (adding newer bullet) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] 16.03 release has been post-postponed (was: When will nixos-16.03 be ready?)
Sorry, I think that we also mentioned in the meeting that we would also have a working x32 ABI NixOS release. I'm afraid that your list is not exhaustive. On Fri, Apr 01, 2016 at 12:10:10PM +0200, Peter Simons wrote: > Christian Kauhaus writes: > > > I wonder what the timeline is for the 16.03 release. As far as I > > understand it, it was supposed to happen in March, but odds are not > > so good right now. Has anyone an idea about what it takes for the > > release to happen? > > I have the unpleasant duty of informing everyone that all plans to release > nixos-16.03 are OFF. > > We were literally minutes away from tagging the source code and switching on > the nixos-16.03 channel when Domen realized that we had flat-out forgotten > to implement several important BLOCKERS that prevent us from releasing the > new version right now. So we had an on-line meeting, discussed our options, > and concluded to POSTPONE any new NixOS releases until the following issues > are resolved: > > - Re-designed UI for Nix command-line tools > - Deterministic Reproducible Builds (#2281) > - Security Hardening (#7220) > - Fast Delivery of Security Updates (#10851) > - Recursive Nix > - Declarative User Environments a.k.a. User-space NixOS (#9250) > - Hydra NG (#12203) > - Lazier mkDerivation function (#11094) > - Consistent Support for Multiple Outputs (#7701) > > Once ALL these issues are implemented and tested, we'll start over with a > new release cycle. > > Thank you for your patience and understanding, > Peter > > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] 16.03 in gcc5.3, master in gcc 4.9?
On Tue, Mar 22, 2016 at 02:10:44PM +0100, joach...@fastmail.fm wrote: > On Tue, Mar 22, 2016, at 01:59 PM, Lluís Batlle i Rossell wrote: > > How weird. Why that was merged into 16.03 and not into master? Why isn't > > master the first step to 16.03? > > Because releases are linux only and so are unaffected by the darwin > breakage. This way we get the feature into the release while minimising > disruption for nixpkgs users. Makes sense to me. > > > So, should we push fixes for gcc5 into 16.03? Will that be merged into > > master? Should these go to staging? > > I'd expect that staging ends up being merged into master at some point, > so putting fixes into staging makes sense to me. I really expected 16.03 to be more stabilised than master, when I switched my 15.09 to 16.03 to help in stabilisation. It seems that it's the other way round, now. Is it just to be able to say 16.03 instead of 16.04? I don't see that a good enough reason to put 16.03 ahead of master in that way. I had to fix things that were working on master, and that feels strange. -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] 16.03 in gcc5.3, master in gcc 4.9?
On Tue, Mar 22, 2016 at 10:12:39AM +0100, Pascal Wittmann wrote: > On 03/22/2016 09:56 AM, Lluís Batlle i Rossell wrote: > > why is release-16.03 in gcc 5.3 (hardening+staging merged in), and master > > in gcc 4.9? > > > > I don't understand. Should we put fixes for gcc5 builds into 16.03 and not > > master? > > I noticed that too when fixing some builds on release-16.03, but haven't > got around to write a mail. I'll second that. I think that someone merged into 16.03 instead of into master unwillingly. An error. But did this pass unnoticed by the maintainers for more than 15 days? It sounds strange to me. The sooner we fix this, the better. :) -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] 16.03 in gcc5.3, master in gcc 4.9?
Hello, why is release-16.03 in gcc 5.3 (hardening+staging merged in), and master in gcc 4.9? I don't understand. Should we put fixes for gcc5 builds into 16.03 and not master? -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] download-from-binary-cache.pl: still waiting for ... is chewing time.
--option binary-caches "" Or in nix.conf. Notice tha this should be applied to nix-daemon, if you use the daemon. On Wed, Mar 16, 2016 at 11:35:39PM +0800, stewart mackenzie wrote: > This is quite annoying, I'm waiting about 30 seconds or more each time > I want to recompile the project and the network is flaky. Is there a > way to disable this cache.nixos.org/.narinfo seek? > > ``` > $ nix-build --argstr debug true --argstr subnet example_wrangle > download-from-binary-cache.pl: still waiting for > ‘https://cache.nixos.org/zh0gxqk936a7cw0kcfn96ny9cy6ccv2g.narinfo’ > after 5 seconds... > download-from-binary-cache.pl: still waiting for > ‘https://cache.nixos.org/csxcfgvjdxvbhapdyn0fmbpcfxhza0k1.narinfo’ > after 5 seconds... > download-from-binary-cache.pl: still waiting for > ‘https://cache.nixos.org/qgn83b8n256f3smy41zi1wrb8x5rjzjz.narinfo’ > after 5 seconds... > these derivations will be built: > /nix/store/6dx1w352pi3p0qc6i8rv8fmqksmlrk2y-fs_dir_list.drv > /nix/store/7l7dwfb0zmcmssp3q32yd8k5456ihkq5-example_wrangle.drv > /nix/store/97r16a6kxnlrlqj75xcqr9ffiga2vpqw-example_wrangle.drv > /nix/store/rjxgfx3a4nhcqp9fy4jill51djry8cbi-example_wrangle.drv > building path(s) ‘/nix/store/qgn83b8n256f3smy41zi1wrb8x5rjzjz-fs_dir_list’ > unpacking sources > ``` > > /sjm > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] NixCon St. Petersburg 2016
I don't know if I will be able to take part, but I recommend you the chance of going to Russia, specially in this case where you have Russian hosts. They are the best to help you enjoy the country, without you to having to fear anything. As for my experience, the Russian people have perfect control about any safety issues that foreigners may fear about, better than many EU-citizens may know about their own cities. I personally feel less safe in militarized and paranoid countries like France or Germany. Moreover, Peter is a very touristic city, and locals are very good at distinguishing tourists (welcomed people) over any migrant that they may throw crazy racist agressivenes to. :) As for the topic raised these days, I have plenty of Russian friends that have very diverse sexual preferences, and they are safe and well organized. There are enough brave people who dare to brand those flags in mass manifestations in the cities in such a police-state, and of course, that involves gratuituous repression by the police. As for assholes, there are everywhere, and they are the most broadcasted on TV. For Dutch (and Russian, which will understand most of them), I take this chance of recommending these documentaries: http://www.npo.nl/van-moskou-tot-moermansk/POMS_S_VPRO_113161 http://www.npo.nl/van-moskou-tot-magadan/POMS_S_VPRO_084195 Regards, Lluís. On Fri, Jan 29, 2016 at 10:38:20AM +, Rob Vermaas wrote: > Hi, > > > I would like to hear what NixOS foundation board have to say to host > > a conference in Sankt Petersburg. Also is there anybody else willing to > > organise conference? Then if we have more proposals who decides where the > > conference is held? I guess still being a very small community it would not > > be > > very smart to have multiple conferences (just yet). Do we need some more > > formal > > procedure for selecting main conference? > > I don't think the NixOS Foundation needs to have a bigger say in this > decision, than any other member of the Nix community. So feel free to > organize events in an open discussion with the Nix community. > > The NixOS Foundation, *currently*, does not have as goal to govern any > community process within the Nix community. This might change in the > future, if we get broader involvement of the community in the > Foundation, and if the community decides we want to organise this as > part of the NixOS Foundation. For now the NixOS Foundation has a > limited scope, as described on http://nixos.org/nixos/foundation.html, > to support the infrastructure and projects of the Nix community. > > To give a *personal* opinion, I would prefer seeing a NixCon in the > USA, if that is feasible and there is enough interest. But I also > wouldn't mind it if it would be organized in St Petersburg. > > Cheers, > -- > Rob Vermaas > > [email] rob.verm...@gmail.com > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Disabling patchelf on ARM
For what I remember, Patchelf is used in most stdenv.mkDerivation just to shorten the number of dependencies (shrink-rpath). In armv5tel, I remember that my binaries were broken if I run patchelf *ONCE*. If I run patchelf *TWICE*, they worked fine. That's clearly an jnsolved bug worked around. I think it was never fixed in patchelf, because there was this work-around and noone looked at the problem anymore. I think that for arv6 or armv7 the double-patchelf was not required anymore; I can't tell. I have not checked how does it work now with those archs. Jokia, it'd be great if you would gather details beyond "it breaks binaries", and even better if you could propose a fix. :) Regards, Lluís. On Tue, Dec 29, 2015 at 12:24:33PM +0100, Joachim Schiele wrote: > On 26.12.2015 12:55, Jookia wrote: > > Hey there, > > > > I've been working for a few months on getting a Novena port of NixOS > > running. > > The overall Nix infrastructure works, though I still have a ton of issues to > > solve before publishing any patches required on a git repository (they > > probably > > won't be merged in to nixpkgs anyway.) > > if they are good patches we will merge them! > > > A problem I've been dealing with is mysterious segmentation faults > > affecting the > > system along with bugs that aren't present in Debian on the same system. > > patchelf has been the culprit for quite a few of them and upstream doesn't > > seem > > to be working on fixing this. > > patchelf is used to deploy the initial bootstrap-tools. later one there > is only minimal use, as you already said, for binary only applications. > > please provide an exaple, where patchelf is doing something wrong with > some paste from the shell. > > thank you > > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] $3.40/month ARM server w/ 2GB RAM, 50GB disk
Thank you! Sounds like a good offer. On Fri, Nov 06, 2015 at 03:41:26AM +, Wout Mertens wrote: > http://techcrunch.com/2015/09/02/scaleway-now-provides-crazy-cheap-virtual-private-servers-starting-at-3-40-per-month/ > > It's a dedicated quad-core ARM server, and you even get 200Mb/s networking. > > Has anybody tried to get NixOS running on these? Seems like this would be > amazing for web servers… > > Having the basically the same configuration.nix for intel or arm platforms > gives NixOS a big leg up in being able to use this. > > Wout. > -- > > Wout. > (typed on mobile, excuse terseness) > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] UEFI Grub is not running, only gummiboot
If it were not a UEFI question, I would say that you only have to tag one partition as bootable. On Wed, Aug 19, 2015 at 07:36:09AM -0300, Anderson Torres wrote: Hello, Nixers! Recently I have tried to use Grub bootloader, but it shows an error message: updating GRUB 2 menu... /nix/store/a457ywa1haa0sgr9g7a1pgldrg3s798d-coreutils-8.24/bin/cp: falhou em preservar o dono para “/boot/memtest.bin”: Operation not permitted installing the GRUB 2 boot loader on /dev/sda... Installing for i386-pc platform. /nix/store/hla0k6l3zskvplyvy6f67jbl4bhf3nmx-grub-2.x-2015-07-27/sbin/grub-install: aviso: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible. /nix/store/hla0k6l3zskvplyvy6f67jbl4bhf3nmx-grub-2.x-2015-07-27/sbin/grub-install: aviso: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. /nix/store/hla0k6l3zskvplyvy6f67jbl4bhf3nmx-grub-2.x-2015-07-27/sbin/grub-install: erro: will not proceed with blocklists. /nix/store/zldbbngl0f8g5iv4rslygxwp0dbg1624-install-grub.pl: installation of GRUB on /dev/sda failed warning: error(s) occured while switching to the new configuration There is some reason I can't install Grub on my machine? ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] [nix-dev] fetchsvn fails to go via proxy
On Tue, Jul 21, 2015 at 08:45:16PM +0800, stewart mackenzie wrote: http_proxy is deliberately mangled. The Nix Way is to download dependencies into the /nix/store then patch build scripts such that the project looks to the /nix/store for the dependencies. That's not the case for fixed-output derivations. fetchsvn, like fetchurl, should properly handle http_proxy. On 21 Jul 2015 16:54, Sergey Mironov grr...@gmail.com wrote: Fetchsvn expression is not able to parse my $http_proxy var correctly. -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] crosscompiling question
On Tue, Jul 14, 2015 at 09:03:06AM +0200, Tomas Hlavaty wrote: Like this, I would like to crosscompile packages on my desktop and then copy-closure them to the board. However, they are different paths in the store. How can I actually achive this? Is there some trick I am missing? Different recipes give different store paths. The recipe of cross-building is quite different from the recipe of native building. If you expect the cross-built 'hello' to have the same hash as the natively built, I don't know any trick. They are effectively built differently, and thus, they have a different store path. I don't know of any way in nix that can relate cross-built packages with natively built. -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] crosscompiling question
On Tue, Jul 14, 2015 at 09:34:16AM +0200, Tomasz Kontusz wrote: I think the only way is to build in qemu on the host, or copy-closure whole system profiles (and then link and activate them by name). I consider the former as 'native build' too, and the latter is what I used years ago in 'nanonixos'. Regards, Lluís. -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Recovering from a failed GRUB update.
Hi, you have nixos-install --chroot. I am not running master - no idea about the grub problem. Regards, Lluís. On Wed, Jul 08, 2015 at 08:20:22AM -0700, rocon...@theorem.ca wrote: For some unknown reason my NixOS update on my laptop last night failed to properly install GRUB (even though I claim that GRUB completed sucessfully). When I rebooted I was met with a simple grub prompt grub and no boot menu. Here is what I did to recover. (1) I booted from a NixOS install media and logged in as root. (2) I mounted my hard disk at /mnt: mount /dev/sda /mnt (3) I browsed the system profiles to select the one I wanted to reactive: ls -l /mnt/nix/var/nix/profiles/system* My lastest generation is system-27-link. For safety I decided I wanted to active system-26-link. (4) Bind dev and friends: Loosely following the nixos-install script, I ran the following commands: mount --rbind /dev /mnt/dev mount --rbind /proc /mnt/proc mount --rbind /sys /mnt/sys (5) I reactivated the system-26-link generation NIXOS_INSTALL_GRUB=1 chroot /mnt /nix/var/nix/profiles/system-26-link/bin/switch-to-configuration boot After that I rebooted, and I was fine. This is all written from memory, so there may be errors. Also, I didn't actually run the command in step (5). I actually ran chroot /mnt /bin/sh and from the shell I ran the switch-to-configuration command. Currently, I'm too scared to try to reproduce the GRUB install failure. -- Russell O'Connor http://r6.ca/ ``All talk about `theft,''' the general counsel of the American Graphophone Company wrote, ``is the merest claptrap, for there exists no property in ideas musical, literary or artistic, except as defined by statute.'' ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] boostHeaders disappeared
Hello, long time ago I introduced a package boostHeaders, that only installed the boost headers without building any lib. The purpose of that package was to avoid the heavy build load of boost. For what I remember, building all boost involved bjam taking 2GB of RAM, and heavy task for g++. This is a huge task for some ARM computers. In the 14th of September William A. Kennington III removed boostHeaders because boost was a multi-output derivation. Commit: f327e9c9221d39dac55e565819054122ead64218 That helps in reducing closures, but makes any program requiring only boost headers to need the full boost completely build, isn't it? I would like boostHeaders back to avoid the heavy build time. This affects only the poor people with NixOS in slow computers that can't use hydra. Is there anyone strongly opposed to having boostHeaders back? I don't think that I can easily build boost in armv5tel with 512MB of RAM. Regards, Lluís. -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] i686 Builds?
My experience is equal with Marco, about memory and my usage of i686. i686 is important for me too. On Tue, May 12, 2015 at 11:43:47AM +0200, Marco Maggesi wrote: I use 32 bit a lot. First of all, I use it on some old machines with 32bit hardware. But, more importantly, I use it regularly on virtuabox and xen virtual machines. In my experience, for most of my use cases the 32bit require less memory (which is often not abundant on virtual instances) and it is thus generally faster for many computing tasks . I made some tests with HOL Light (the theorem prover). The bare program has memory occupation which almost the double in the 64bit version (~1.2Gb) with respect to the 32bit version (~0.7Gb). On a virtual machine with 2Gb of ram, the 32 bit it is often 10%-20% faster on typical usage and 50% faster or more when the computation requires more memory. In my experience, the version 32 bit can be more convenient than the 64bit version in a variety of situations. So, please, do not give-up with 32 bit support. Marco 2015-05-12 11:08 GMT+02:00 Luke Clifton ltclif...@gmail.com: +1 This seems like a good idea. On 12 May 2015 at 06:45, William Kennington will...@wkennington.com wrote: Maybe it would make more sense to only build the i686 builds if our tested set of x86_64 binaries build correctly. We would still release with both but it would cut down on a lot of redundant failures. On Mon, May 11, 2015 at 3:39 PM Ryan Trinkle ryan.trin...@gmail.com wrote: I encountered an i686 user just the other day! I don't use it personally, but having solid support in Nix was fantastic, especially because older, 32-bit machines tend to be slower, which makes Nix's binary caching functionality even more important. On Mon, May 11, 2015 at 6:36 PM, Shea Levy s...@shealevy.com wrote: Hi all, Do we still have users running 32-bit machines? It would reduce the load on hydra significantly if we could drop support for i686, though of course if people are still relying on it we shouldn't make the change yet. ~Shea ___ 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 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 mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] i686 Builds?
On Tue, May 12, 2015 at 01:21:59PM +0200, Eelco Dolstra wrote: On 12/05/15 12:49, Lluís Batlle i Rossell wrote: Yes. Maybe it got renamed... It used to be named 'amd32'. It's called x32: http://en.wikipedia.org/wiki/X32_ABI Thank you! So this thread could end up in an extra nixos architecture instead of one less. Years ago, I had a tweak to my nixos (never pushed upstream) that used a 64-bit kernel with 32-bit userspace. This allowed me to install specific programs 64-bit with nix-env. The purpose was to have a general memory saving, but keeping fast calculations in specific things (like melt, ffmpeg, ...). Regards, Lluís. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] i686 Builds?
Yes. Maybe it got renamed... It used to be named 'amd32'. On Tue, May 12, 2015 at 12:45:36PM +0200, Tomasz Kontusz wrote: By amd32 do you mean amd64 with 32 bit pointers? Lluís Batlle i Rossell vi...@viric.name napisał: amd32 should be ready in the kernel and gcc/glibc. We just need someone to prepare nix/nixpgks/nixos for this. :) On Tue, May 12, 2015 at 12:05:29PM +0200, Christian Theune wrote: Hi, same here. Many interpreted languages (like Python) are affected by this as they tend to be quite pointer-happy. As pointer-size doubles from 32bit to 64bit we find that in most applications we have about 70% increase when moving to 64-bit ending up with 1.7 as much memory as before. So we also currently run applications in 32-bit virtual machines and rather use many 3GiB processes than a few bigger ones. Moving from 3GiB to 64bit requires about 5GiB just to even out the pointer-size effects. Supposedly the amd64 instruction set has some benefits that make e.g. Python run faster on certain computational stuff, but I don’t have prove for that. In the long term we will include 64-bit in the mix anyway as some applications (Mongo, sigh) are quite trigger happy with allocating virtual (non residential) memory for mmapping insane numbers of insanely large files … Christian On 12 May 2015, at 11:59, Lluís Batlle i Rossell vi...@viric.name wrote: My experience is equal with Marco, about memory and my usage of i686. i686 is important for me too. On Tue, May 12, 2015 at 11:43:47AM +0200, Marco Maggesi wrote: I use 32 bit a lot. First of all, I use it on some old machines with 32bit hardware. But, more importantly, I use it regularly on virtuabox and xen virtual machines. In my experience, for most of my use cases the 32bit require less memory (which is often not abundant on virtual instances) and it is thus generally faster for many computing tasks . I made some tests with HOL Light (the theorem prover). The bare program has memory occupation which almost the double in the 64bit version (~1.2Gb) with respect to the 32bit version (~0.7Gb). On a virtual machine with 2Gb of ram, the 32 bit it is often 10%-20% faster on typical usage and 50% faster or more when the computation requires more memory. In my experience, the version 32 bit can be more convenient than the 64bit version in a variety of situations. So, please, do not give-up with 32 bit support. Marco 2015-05-12 11:08 GMT+02:00 Luke Clifton ltclif...@gmail.com: +1 This seems like a good idea. On 12 May 2015 at 06:45, William Kennington will...@wkennington.com wrote: Maybe it would make more sense to only build the i686 builds if our tested set of x86_64 binaries build correctly. We would still release with both but it would cut down on a lot of redundant failures. On Mon, May 11, 2015 at 3:39 PM Ryan Trinkle ryan.trin...@gmail.com wrote: I encountered an i686 user just the other day! I don't use it personally, but having solid support in Nix was fantastic, especially because older, 32-bit machines tend to be slower, which makes Nix's binary caching functionality even more important. On Mon, May 11, 2015 at 6:36 PM, Shea Levy s...@shealevy.com wrote: Hi all, Do we still have users running 32-bit machines? It would reduce the load on hydra significantly if we could drop support for i686, though of course if people are still relying on it we shouldn't make the change yet. ~Shea ___ 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 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 mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev — Christian Theune · c...@flyingcircus.io · +49 345 219401 0 Flying Circus Internet Operations GmbH · http://flyingcircus.io Forsterstraße 29 · 06112 Halle (Saale) · Deutschland HR Stendal HRB 21169
Re: [Nix-dev] i686 Builds?
amd32 should be ready in the kernel and gcc/glibc. We just need someone to prepare nix/nixpgks/nixos for this. :) On Tue, May 12, 2015 at 12:05:29PM +0200, Christian Theune wrote: Hi, same here. Many interpreted languages (like Python) are affected by this as they tend to be quite pointer-happy. As pointer-size doubles from 32bit to 64bit we find that in most applications we have about 70% increase when moving to 64-bit ending up with 1.7 as much memory as before. So we also currently run applications in 32-bit virtual machines and rather use many 3GiB processes than a few bigger ones. Moving from 3GiB to 64bit requires about 5GiB just to even out the pointer-size effects. Supposedly the amd64 instruction set has some benefits that make e.g. Python run faster on certain computational stuff, but I don’t have prove for that. In the long term we will include 64-bit in the mix anyway as some applications (Mongo, sigh) are quite trigger happy with allocating virtual (non residential) memory for mmapping insane numbers of insanely large files … Christian On 12 May 2015, at 11:59, Lluís Batlle i Rossell vi...@viric.name wrote: My experience is equal with Marco, about memory and my usage of i686. i686 is important for me too. On Tue, May 12, 2015 at 11:43:47AM +0200, Marco Maggesi wrote: I use 32 bit a lot. First of all, I use it on some old machines with 32bit hardware. But, more importantly, I use it regularly on virtuabox and xen virtual machines. In my experience, for most of my use cases the 32bit require less memory (which is often not abundant on virtual instances) and it is thus generally faster for many computing tasks . I made some tests with HOL Light (the theorem prover). The bare program has memory occupation which almost the double in the 64bit version (~1.2Gb) with respect to the 32bit version (~0.7Gb). On a virtual machine with 2Gb of ram, the 32 bit it is often 10%-20% faster on typical usage and 50% faster or more when the computation requires more memory. In my experience, the version 32 bit can be more convenient than the 64bit version in a variety of situations. So, please, do not give-up with 32 bit support. Marco 2015-05-12 11:08 GMT+02:00 Luke Clifton ltclif...@gmail.com: +1 This seems like a good idea. On 12 May 2015 at 06:45, William Kennington will...@wkennington.com wrote: Maybe it would make more sense to only build the i686 builds if our tested set of x86_64 binaries build correctly. We would still release with both but it would cut down on a lot of redundant failures. On Mon, May 11, 2015 at 3:39 PM Ryan Trinkle ryan.trin...@gmail.com wrote: I encountered an i686 user just the other day! I don't use it personally, but having solid support in Nix was fantastic, especially because older, 32-bit machines tend to be slower, which makes Nix's binary caching functionality even more important. On Mon, May 11, 2015 at 6:36 PM, Shea Levy s...@shealevy.com wrote: Hi all, Do we still have users running 32-bit machines? It would reduce the load on hydra significantly if we could drop support for i686, though of course if people are still relying on it we shouldn't make the change yet. ~Shea ___ 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 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 mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev — Christian Theune · c...@flyingcircus.io · +49 345 219401 0 Flying Circus Internet Operations GmbH · http://flyingcircus.io Forsterstraße 29 · 06112 Halle (Saale) · Deutschland HR Stendal HRB 21169 · Geschäftsführer: Christian. Theune, Christian. Zagrodnick -- (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
On Fri, Feb 20, 2015 at 11:45:01AM +0100, Vladimír Čunát wrote: On 02/20/2015 11:36 AM, Lluís Batlle i Rossell wrote: If that commit could be merged into master, it would be nice. I'd be able to commit to master instead. We'd better wait a few days for Hydra to catch up a bit: http://hydra.nixos.org/eval/1173079 A few days passed. I merged staging from the libsigsegv change. I didn't know next commits, so I thought better not to merge them. If anyone wants to merge more commits, go on. Regards, Lluís. -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
On Fri, Feb 20, 2015 at 11:33:40AM +0100, Vladimír Čunát wrote: On 02/20/2015 09:29 AM, Lluís Batlle i Rossell wrote: a trivial work-around for the libsigsegv issue is now in staging: This is not yet in 'master', right? What are we waiting to have it in 'master'? Hydra? Yes, ATM it's the only commit in master..staging. As I'm using staging to be able to build *anything*, I feel invited to commit to staging for non-stdenv-changing commits. :) If that commit could be merged into master, it would be nice. I'd be able to commit to master instead. I'm keeping my changes local, waiting for the merge of staging into master. Regards, Lluís. -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
On Tue, Feb 17, 2015 at 11:56:00PM +0100, Lluís Batlle i Rossell wrote: On Tue, Feb 17, 2015 at 11:45:28PM +0100, Peter Simons wrote: Hi guys, a trivial work-around for the libsigsegv issue is now in staging: https://github.com/NixOS/nixpkgs/commit/953466fcbaea0f7c4d48b5a6e3905d4e07b9a79d I'll merge it to master within a couple of days, once Hydra has built binaries for the new stdenv version. If anyone is aware of a superior way to remedy this problem, please don't hesitate to improve on the change. Perfect! Thank you! I think this change is what most people affected did, and hence they will not notice a stdenv change. This is not yet in 'master', right? What are we waiting to have it in 'master'? Hydra? Thank you, Lluís. -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
On Tue, Feb 17, 2015 at 11:45:28PM +0100, Peter Simons wrote: Hi guys, a trivial work-around for the libsigsegv issue is now in staging: https://github.com/NixOS/nixpkgs/commit/953466fcbaea0f7c4d48b5a6e3905d4e07b9a79d I'll merge it to master within a couple of days, once Hydra has built binaries for the new stdenv version. If anyone is aware of a superior way to remedy this problem, please don't hesitate to improve on the change. Perfect! Thank you! I think this change is what most people affected did, and hence they will not notice a stdenv change. -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
The repository masters are silent about it. Niksut? Dr Pepper? Peti? I guess they don't experience the problem, so they are ready to wait to new kernels arrive. That's all guessing; I haven't seen any formal position. That's why I asked at the time staging was merged. An easier way would have been to commit directly the disable of check to master, but I'm not heavily affected by the issue. As for me, please disable the check until a libsigsegv update happens. Regards, Lluís. On Tue, Feb 17, 2015 at 02:58:58PM -0200, Anderson Torres wrote: About sigsegv, what is the recommended procedure? 2015-02-14 12:45 GMT-02:00 Anderson Torres torres.anderson...@gmail.com: 2015-02-13 20:31 GMT-02:00 Lluís Batlle i Rossell vi...@viric.name: On Fri, Feb 13, 2015 at 11:29:03PM +0100, Bjørn Forsman wrote: On 13 February 2015 at 23:26, James Cook jc...@cs.berkeley.edu wrote: https://github.com/NixOS/nixpkgs/issues/6028#issuecomment-72952987 The error is caused by an impurity, so bisecting might just reveal which version you had in the store before you switched to a newer kernel. Ah, right. Thanks. (I wasn't aware of issue #6028). Some people disabled doCheck in libsigsegv, but it's a stdenv change. Should we disable doCheck there until the storm passes? Yep, it is the best thing to do now, imho. -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ 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 -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
On Fri, Feb 13, 2015 at 11:07:27PM +0100, Bjørn Forsman wrote: On 13 February 2015 at 22:20, Lluís Batlle i Rossell vi...@viric.name wrote: Thank you! Is the plan for failing libsigsegv to wait for kernel.org fixes? What's the connection between libsigsegv and kernel.org? I noticed libsigsegv test failures the other day (I was playing with armv7 bootstrap), and I bisected the error to this commit: 88fd7f452703f3280a3747e97b938c8e50ae962c (Re-Revert merge #5505: util-linux: use /run/current-system/sw/bin/*) I was planning to make a gihub issue or post on nix-dev ML, but didn't get to it before now :-) I think that linus changed the signal of stack overflow from SIGSEGV to SIGBUS. At some point, people realized it was a bad idea, and they took the change back in recent kernels. But if you bisected it... no idea. :) That change you found is quite weird. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
On Fri, Feb 13, 2015 at 11:29:03PM +0100, Bjørn Forsman wrote: On 13 February 2015 at 23:26, James Cook jc...@cs.berkeley.edu wrote: https://github.com/NixOS/nixpkgs/issues/6028#issuecomment-72952987 The error is caused by an impurity, so bisecting might just reveal which version you had in the store before you switched to a newer kernel. Ah, right. Thanks. (I wasn't aware of issue #6028). Some people disabled doCheck in libsigsegv, but it's a stdenv change. Should we disable doCheck there until the storm passes? -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
Thank you! Is the plan for failing libsigsegv to wait for kernel.org fixes? Regards, Lluís. On Fri, Feb 13, 2015 at 10:16:24PM +0100, Peter Simons wrote: 'staging' has been merged to 'master' in 54ce1a1. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Can we please have text-only on this ML?
On Fri, Feb 06, 2015 at 02:57:46PM +0100, Matthias Beyer wrote: I just notice that almost everything I read from this ML is html. You may have a problem in your mutt. Can it be? My mutt only shows the text/plain part, despite there is often also a test/html in the multipart. On 06-02-2015 14:31:03, Lluís Batlle i Rossell wrote: As long as there is a text/plain element in the multipart, all fine, isn't it? On Fri, Feb 06, 2015 at 01:41:25PM +0100, Matthias Beyer wrote: Hi, can we please have text-only on this ML? Maybe even through a mailman setting, so it rejects non-text-only-mail? -- Mit freundlichen Grüßen, Kind regards, Matthias Beyer Proudly sent with mutt. Happily signed with gnupg. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- PGP key D4831A8A - https://emailselfdefense.fsf.org/ -- Mit freundlichen Grüßen, Kind regards, Matthias Beyer Proudly sent with mutt. Happily signed with gnupg. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] A few questions about ARM support and NixOS on a Chromebook
On Mon, Feb 02, 2015 at 04:16:07PM +0100, Bjørn Forsman wrote: On 2 February 2015 at 01:17, Lluís Batlle i Rossell vi...@viric.name wrote: I have the bootstrap-tools for armv5tel, they build and the test passes. https://github.com/viric/nixpkgs/tree/make_arm_bootstraptools Now I try to go further building release-14.12 stdenv. Cool! I will have a look at your branch. So it seems all works. I see ambro has lots of work done for arm too. https://github.com/NixOS/nixpkgs/pull/6042 How can we coordinate this? Ambro, are you here? Maybe we spend some irc time and prepare a big PR? -- PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] A few questions about ARM support and NixOS on a Chromebook
I have the bootstrap-tools for armv5tel, they build and the test passes. https://github.com/viric/nixpkgs/tree/make_arm_bootstraptools Now I try to go further building release-14.12 stdenv. On Fri, Jan 30, 2015 at 04:19:49PM +0100, Lluís Batlle i Rossell wrote: I have the busybox.. but that's not enough. Eelco updated the bootstrap tools in the 29th of October, but I cannot find why. The new bootstrap tools include different binaries. Eelco updated the stdenv scripts to accomodate the new tools, but without updating arm or mips tools, hence breaking them. One approach could have been to have kept the old stdenv scripts for arm/mips. Can anyone point me to the reasons of the change, so I can try to work in that same direction? Or restore old bootstrap tools scripts. Regards, Lluís. -- PGP key D4831A8A - https://emailselfdefense.fsf.org/ -- PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] A few questions about ARM support and NixOS on a Chromebook
I have the busybox.. but that's not enough. Eelco updated the bootstrap tools in the 29th of October, but I cannot find why. The new bootstrap tools include different binaries. Eelco updated the stdenv scripts to accomodate the new tools, but without updating arm or mips tools, hence breaking them. One approach could have been to have kept the old stdenv scripts for arm/mips. Can anyone point me to the reasons of the change, so I can try to work in that same direction? Or restore old bootstrap tools scripts. Regards, Lluís. -- PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] A few questions about ARM support and NixOS on a Chromebook
Hello all, I'll try the next days whether I can update the pieces. I'm using native armv5tel, not cross builds, as usual in nixos-on-arm. 1) Build a static busybox that works for the purpose. 2) Build release-14.12 or master 3) Commit the busybox to the bootstrap svn repository (if I am correct) 4) Make stdenv reference that busybox Let's hope that'd be enough to go on. armv6 (raspberry pi) should be able to use the armv5tel binary just fine. I bet I have the slowest system of all of the present here... I'll go at my pace. If you fix it earlier, commit or submit PR. :) Regards, Lluís. On Wed, Jan 28, 2015 at 04:29:25PM +0100, Bjørn Forsman wrote: On 28 January 2015 at 08:42, Luke Clifton ltclif...@gmail.com wrote: [...] I once used to think that full system cross compilation was the only way you should do things (I was an idealist). But it is a dead end. Unless you have thousands of hours to throw at the problem, it won't work. Me too. I totally agree :-) Have you made any progress on this yourself? Nope, not really. I'm finding the nixpkgs/nixos/stdenv bootstrap process quite difficult to grap, so I've been putting it off... All I have is this branch[1] that has some cross-compilation fixes (borrowed from Buildroot[2]) for some basic packages (python, systemd, ...), as a step towards a cross-compiled bootstrap image that can be loaded in QEMU to do further native compilation. So far I've been thinking that we need to cross compile a fully working (although minimal) nixos system for QEMU, but I'm not sure this is strictly needed. Maybe we can bootstrap nix inside QEMU from a tiny set of packages (gcc, libc, make)? But I'm not sure how to do it. @nbp has some ideas: https://github.com/NixOS/nixpkgs/issues/4963#issuecomment-64956636. Best regards, Bjørn Forsman [1] https://github.com/bjornfor/nixpkgs/tree/cross-compile-fixes [2] http://buildroot.uclibc.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] kdePackages ignored silently
rename.nix says: # ++ obsolete [ environment kdePackages ] [ environment systemPackages ] # # !!! doesn't work! What should we do? If obsolete doesn't work, I'd take out kdePackages at least, for nixos-rebuild to fail if anyone uses kdePackages. Now those packages are simply ignored. I don't know much how rename.nix, so maybe someone can fix this properly. -- PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Again: Why don't these people have commit access
On Sun, Jan 18, 2015 at 07:53:35PM +0100, Moritz Ulrich wrote: Pascal Wittmann pascalwittm...@gmx.net writes: On 01/18/2015 06:19 PM, Nathan Bijnens wrote: While I don't mind that we expand the number of people with commit access, I firmly oppose doing changes directly on master, any change should first be a PR. If there're more people who can close a PR, those PRs will be open for a shorter amount of time. What is the advantage? IMO this would create an enormous overhead. E.g. I just updated abiword from 3.0.0 to 3.0.1 and only changed the version number and hash. Is this worth a pull request? I don't want to merge those pull requests, they only cover the discussion-worthy pull requests. I totally agree here: Simple version-updates, fixes, (simple) new packages, etc. should go into master/staging without a PR. We can still create pull requests for bigger changes and/or controversial ideas. Remember that we use a comfortable VCS, and it is quite easy to take back things if the changes seem not to work well. And they can be reapplied again later if they were doing the right thing, etc. As for me, let the listed contributors commit to master! ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Firefox test in 14.04
On 12/31/2014 09:23 AM, Lluís Batlle i Rossell wrote: From this link, of special attention are the Build Steps lines; one failing and the other not, of the same store path. That sounds like someone restarted a build that failed first. So the channel 14.04 is broken now. Who can fix that? We need the firefox test passing, and the firefox build too, for i686. Now the channel lacks firefox 32-bit and is outdated. Regards, Lluís. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Firefox test in 14.04
Hello all, the 14.04 channel has something strange about firefox 32-bit. It failed to build several times, but the firefox 32-bit nixos test was succeeding. Check the result and the Inputs tab. http://hydra.nixos.org/build/17689092 This resulted in having a 14.04 channel without firefox 32-bit binaries. Moreover, after the build I gave, firefox 32-bit was fixed by an update of version, but then the nixos test started to fail, therefore the channel never being updated since the failing firefox 32-bit build (the link I gave, 22nd of december). Some logs have disappared from hydra, so maybe someone knows quickly what is happening. Have happy vacations, and good luck finding the man of the noses today! :) ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Firefox test in 14.04
On Wed, Dec 31, 2014 at 09:18:39AM +0100, Lluís Batlle i Rossell wrote: Hello all, the 14.04 channel has something strange about firefox 32-bit. It failed to build several times, but the firefox 32-bit nixos test was succeeding. Check the result and the Inputs tab. http://hydra.nixos.org/build/17689092 From this link, of special attention are the Build Steps lines; one failing and the other not, of the same store path. 1 Build of /nix/store/dr791i26dli0g7dlmilk34zamgi09vy7-firefox-34.0.5 0s Failed: builder for ‘/nix/store/p1j53dk2zx2d17sh01qggkr5lvyrjvl9-firefox-34.0.5.drv’ failed with exit code 100 (log, raw, tail) 2 Build of /nix/store/dr791i26dli0g7dlmilk34zamgi09vy7-firefox-34.0.5 20m 38s wendy Succeeded (log, raw, tail) Regards, Lluís. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] deploying nix-built software to non-nix linux systems
On Tue, Nov 04, 2014 at 10:23:08AM +0100, Eelco Dolstra wrote: Hi, On 04/11/14 00:36, Anders Papitto wrote: I'm interested in using nix/nixos to build an application with its full set of dependencies, and then deploy it to non-nixos machines as a self-contained package (up to and including the system libraries), without root privileges. Ideally I would like to not require that any nix tools be available on the target system. The perfect workflow would be something like # on any linux system $ wget https://some/path/to/my-app.tar.gz $ tar -xf my-app.tar.gz $ ./my-app/bin/my-app # run the application - it should not try to access anything outside ./my-app Is this possible? No, this is not possible unless you do static linking or some deep ld-linux/patchelf magic. For instance, my-app will have references to Glibc in the Nix store, which are not relocatable. If it's only about dynamic linking, you can put all into a directory, and go with a sh script that sets the proper LD_LIBRARY_PATH and calls the proper dynamic loader to load the wanted ELF. LD_LIBRARY_PATH=`pwd` ./ld-linux.so.3 ./myprogram It may work. :) ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] nix proposal for security fixes
ahhh I never used it. I will! Thank you. On Sun, Sep 28, 2014 at 08:11:30PM -0400, Shea Levy wrote: Yes, this is exactly what replaceDependency is for. On Sun, Sep 28, 2014 at 02:58:03PM -0700, rocon...@theorem.ca wrote: We already have shlevy's replaceDependency which, IMHO, solves this problem. In functional programming when we have an immutable tree structure that we want to update, we trace a path from the root of the tree to the node that we want to update and we update all the nodes along that path to point to a newly created spine and we get a new tree that shares all unchanged subtrees with with the old tree. shlevy's replaceDependency, and his related NixOS module system.replaceRuntimeDependencies, works in the same way. Starting from the root derivation, typically your NixOS system, but could be your user-enviroment, we can traverse the entire tree of runtime dependencies and replace one package, say bash, with another package. Then we replace all the nodes between those adjusted subpackages and the root package with new nodes that are identical to the old nodes except they have their references updated to point to the new nodes. These new nodes are created by derivations that use the old node binaries as source files and run sed to replace the /nix/store/references. The result is a new NixOS sytem/user-environment that references the replacement package everywhere and this all done in a purely functional manner. While this process isn't quite as fast as our mutable cousin's procedure of updating packages in place in a matter of seconds, this replaceDependency tree update process can be done in a few minutes without any extenstions to Nix. For me, I think building bash took more time than replaceDependecy process and it is certainly faster than the hours or days it will take to rebuild the whole system. On Sun, 28 Sep 2014, Lluís Batlle i Rossell wrote: Hello! It could be nice if we had a nix derivation attribute that allowed the determination of a store path, overriding the hash mechanisms for it. Imagine that we have a bash to fix; we could add a line in the bash derivation attribute set: forceOut = whatever store path out It'd be nice if nix tools allowed to list (or mark specially on screen) derivations that have forceOut paths. It should be applied only in case of security fixes. An operation like nix-store --repair should, then, allow for a global system update. Another approach, non intrusive to nixpkgs, would be to allow nix to read such a list of hash overrides (hash → desiredHash) from nix.conf or so. It'd allow for anyone who cares to get some protection without waiting hydra. Of course this makes sense for elf programs or shared objects, and not for static libs. And hydra should not be using this trick. :) What do you think? Maybe all this even exists already. :) Regards, Lluís. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Russell O'Connor http://r6.ca/ ``All talk about `theft,''' the general counsel of the American Graphophone Company wrote, ``is the merest claptrap, for there exists no property in ideas musical, literary or artistic, except as defined by statute.'' ___ 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] nix proposal for security fixes
Hello! It could be nice if we had a nix derivation attribute that allowed the determination of a store path, overriding the hash mechanisms for it. Imagine that we have a bash to fix; we could add a line in the bash derivation attribute set: forceOut = whatever store path out It'd be nice if nix tools allowed to list (or mark specially on screen) derivations that have forceOut paths. It should be applied only in case of security fixes. An operation like nix-store --repair should, then, allow for a global system update. Another approach, non intrusive to nixpkgs, would be to allow nix to read such a list of hash overrides (hash → desiredHash) from nix.conf or so. It'd allow for anyone who cares to get some protection without waiting hydra. Of course this makes sense for elf programs or shared objects, and not for static libs. And hydra should not be using this trick. :) What do you think? Maybe all this even exists already. :) Regards, Lluís. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] nix proposal for security fixes
My 'forceOut' clearly will not work as easy as setting it in a stdenv.mkDerivation argument, because there may be multiple calls to mkDerivation for the same derivation name (with different inputs). The table of correspondences in nix.conf still looks good to me though. It'd be nice if there were an operation that could list all bash (derivation name) that have been built with a specific src hash. That'd allow to find out all affected derivations. Regards, Lluís On Sun, Sep 28, 2014 at 12:28:42PM +0200, Lluís Batlle i Rossell wrote: Hello! It could be nice if we had a nix derivation attribute that allowed the determination of a store path, overriding the hash mechanisms for it. Imagine that we have a bash to fix; we could add a line in the bash derivation attribute set: forceOut = whatever store path out It'd be nice if nix tools allowed to list (or mark specially on screen) derivations that have forceOut paths. It should be applied only in case of security fixes. An operation like nix-store --repair should, then, allow for a global system update. Another approach, non intrusive to nixpkgs, would be to allow nix to read such a list of hash overrides (hash → desiredHash) from nix.conf or so. It'd allow for anyone who cares to get some protection without waiting hydra. Of course this makes sense for elf programs or shared objects, and not for static libs. And hydra should not be using this trick. :) What do you think? Maybe all this even exists already. :) Regards, Lluís. ___ 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] skype4pidgin
I never made it install well. I always used it (long ago!) by symlinking to its shared object in the home directory for plugins (~/.purple-2/plugins? I don't remember) Regards, Lluís On Wed, Sep 24, 2014 at 01:49:17AM +0400, Alexander Zubkov wrote: Hi. Is somebody using skype4pidgin? I'm using unstable channel, installed pidgin, skype4pidgin. But pidgin do not see this plugin. If I run it with debug option: pidgin -d, I see that it only tries for plugins in its own directory. For example: (01:42:37) plugins: probing /nix/store/cvzq6cvx2p2a9jjqz45b0hivg88r5wv4-pidgin-2.10.9/lib/pidgin/pidginrc.so (01:42:37) plugins: probing /nix/store/cvzq6cvx2p2a9jjqz45b0hivg88r5wv4-pidgin-2.10.9/lib/pidgin/gtkbuddynote.so (01:42:37) plugins: probing /nix/store/cvzq6cvx2p2a9jjqz45b0hivg88r5wv4-pidgin-2.10.9/lib/pidgin/xmppdisco.so (01:42:37) plugins: probing /nix/store/cvzq6cvx2p2a9jjqz45b0hivg88r5wv4-pidgin-2.10.9/lib/purple-2/ssl-nss.so (01:42:37) plugins: probing /nix/store/cvzq6cvx2p2a9jjqz45b0hivg88r5wv4-pidgin-2.10.9/lib/purple-2/dbus-example.so (01:42:37) plugins: probing /nix/store/cvzq6cvx2p2a9jjqz45b0hivg88r5wv4-pidgin-2.10.9/lib/purple-2/libyahoojp.so What I'm doing wrong? ___ 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