[Nix-commits] [NixOS/nixpkgs] ee20e8: virtmanager-qt: 0.39.60 -> 0.42.67
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: ee20e8964429288df5f8186c4d6b0771633be86d https://github.com/NixOS/nixpkgs/commit/ee20e8964429288df5f8186c4d6b0771633be86d Author: Peter Hoeg Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/applications/virtualization/virt-manager/qt.nix Log Message: --- virtmanager-qt: 0.39.60 -> 0.42.67 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] How do you work on big packages?
A while ago I wrote a wrapper around nix-shell that helps with running the build steps in correct manner and order (among with other niceties like automatically creating a temporary build directory and making $out point to a path in /tmp/): https://github.com/dezgeg/nix-debug-shell I mainly wrote it for debugging build steps for existing packages, but I guess the same ideas/code could be used for local development as well. It is rigorously undocumented, so here's a short primer: in a nixpkgs tree, run /path/to/nix-debug-shell -A hello. That places you under /tmp/nds-build-hello/hello-2.10 with the sources unpacked. Run 'nd-step' as many times you want to step through the build phases (it's named after the 'step' command in GDB). When installPhase is done, it installs to /tmp/, e.g. /tmp/nds-install-hello/bin/hello. Hope anyone finds this useful. 2017-03-17 21:26 GMT+02:00 Profpatsch : > On 17-03-17 06:04pm, Volth wrote: >> "nix-shell" would be a super option here if it could handle >> "installPhase" (this seems easy to fix) and .nix files less trivial >> than "hello.nix" (this seems not easy to fix; for example "nix-shell >> '' -A linux_4_4" has no "configurePhase", and there are >> similar problems with almost every of the big projects; nix-shell >> launches "make" when "nix-build" launches "cmake" or vice-versa, etc) > > That’s a pretty common stumbling block. > > If someone defines his own `installPhase` for example, > the `installPhase` shell function is just the standard > stdenv `installPhase`. What you want to call is rather > the contents of `$installPhase` (the variable), since > that contains the phase you defined in `mkDerivation`. > > nix-shell > $ unpackPhase > unpacking … > $ configurePhase > configuring … > $ buildPhase > … > $ $installPhase > running your installPhase > > > There is not much abstraction. Every nix attribute within > `derivation` (and by extension `mkDerivation`) will end up > as a bash shell variable in your shell (and your build env). > > -- > Proudly written in Mutt with Vim on NixOS. > Q: Why is this email five sentences or less? > A: http://five.sentenc.es > May take up to five days to read your message. If it’s urgent, call me. > ___ > 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-commits] [NixOS/nixpkgs] f9458b: citrix-receiver: add link to webpage with all vers...
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: f9458bae63d324ba4b80ab3deac9ca205d203c43 https://github.com/NixOS/nixpkgs/commit/f9458bae63d324ba4b80ab3deac9ca205d203c43 Author: obadz Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/applications/networking/remote/citrix-receiver/default.nix Log Message: --- citrix-receiver: add link to webpage with all versions and adjust to change in nix-prefetch-url Helps with #23975 (cherry picked from commit 17bfb6a08a0f77124bbe96e2908076c821bdeb46) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 17bfb6: citrix-receiver: add link to webpage with all vers...
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 17bfb6a08a0f77124bbe96e2908076c821bdeb46 https://github.com/NixOS/nixpkgs/commit/17bfb6a08a0f77124bbe96e2908076c821bdeb46 Author: obadz Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/applications/networking/remote/citrix-receiver/default.nix Log Message: --- citrix-receiver: add link to webpage with all versions and adjust to change in nix-prefetch-url Helps with #23975 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 3fac05: libsodium: 1.0.11 -> 1.0.12
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 3fac05b9515dbee23d8d33dad42d947204192483 https://github.com/NixOS/nixpkgs/commit/3fac05b9515dbee23d8d33dad42d947204192483 Author: Joachim Fasting Date: 2017-03-16 (Thu, 16 Mar 2017) Changed paths: M pkgs/development/libraries/libsodium/default.nix Log Message: --- libsodium: 1.0.11 -> 1.0.12 Commit: aa5777df7701c019df77bad151faf2c2bfc3efc5 https://github.com/NixOS/nixpkgs/commit/aa5777df7701c019df77bad151faf2c2bfc3efc5 Author: Joachim F Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/development/libraries/libsodium/default.nix Log Message: --- Merge pull request #23952 from joachifm/libsodium-bump libsodium: 1.0.11 -> 1.0.12 Compare: https://github.com/NixOS/nixpkgs/compare/5d51f1d7b172...aa5777df7701___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 4b1406: firefox, firefox-bin: 51.0.1 -> 52.0, firefox-esr:...
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 4b140619b4d40e0a03d00c13c02c3ddaf7617ff9 https://github.com/NixOS/nixpkgs/commit/4b140619b4d40e0a03d00c13c02c3ddaf7617ff9 Author: taku0 Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/applications/networking/browsers/firefox-bin/sources.nix M pkgs/applications/networking/browsers/firefox/default.nix Log Message: --- firefox, firefox-bin: 51.0.1 -> 52.0, firefox-esr: 45.7esr -> 52.0esr (cherry picked from commit a24aaae60252b8c383bdf480858c724c4b38c3b6) Commit: a30906fd9cc6e0c3b0d2ef7af39f8619c1ec3584 https://github.com/NixOS/nixpkgs/commit/a30906fd9cc6e0c3b0d2ef7af39f8619c1ec3584 Author: taku0 Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/applications/networking/browsers/firefox-bin/sources.nix M pkgs/applications/networking/browsers/firefox/default.nix Log Message: --- firefox, firefox-bin: 52.0 -> 52.0.1 (cherry picked from commit 3f175876e8f470b0860e37b926aa0e9776231556) Commit: 1f984c0e05d4854e9668bd0c15f0947beb1f6ecc https://github.com/NixOS/nixpkgs/commit/1f984c0e05d4854e9668bd0c15f0947beb1f6ecc Author: taku0 Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/applications/networking/browsers/firefox/default.nix Log Message: --- firefox-esr: 52.0esr -> 52.0.1esr (cherry picked from commit a038f918714efbb67b27574dff93b632f50c916e) Compare: https://github.com/NixOS/nixpkgs/compare/b944312eb536...1f984c0e05d4___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 3f1758: firefox, firefox-bin: 52.0 -> 52.0.1
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 3f175876e8f470b0860e37b926aa0e9776231556 https://github.com/NixOS/nixpkgs/commit/3f175876e8f470b0860e37b926aa0e9776231556 Author: taku0 Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/applications/networking/browsers/firefox-bin/sources.nix M pkgs/applications/networking/browsers/firefox/default.nix Log Message: --- firefox, firefox-bin: 52.0 -> 52.0.1 Commit: a038f918714efbb67b27574dff93b632f50c916e https://github.com/NixOS/nixpkgs/commit/a038f918714efbb67b27574dff93b632f50c916e Author: taku0 Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/applications/networking/browsers/firefox/default.nix Log Message: --- firefox-esr: 52.0esr -> 52.0.1esr Commit: 5d51f1d7b172ace9411ab953a866243b76fb0ae0 https://github.com/NixOS/nixpkgs/commit/5d51f1d7b172ace9411ab953a866243b76fb0ae0 Author: Joachim F Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/applications/networking/browsers/firefox-bin/sources.nix M pkgs/applications/networking/browsers/firefox/default.nix Log Message: --- Merge pull request #24000 from taku0/firefox-bin-52.0.1 firefox, firefox-bin: 52.0 -> 52.0.1, firefox-esr: 52.0esr -> 52.0.1esr [Critical security fix] Compare: https://github.com/NixOS/nixpkgs/compare/a4d6e2cf1632...5d51f1d7b172___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] a4d6e2: atom: avoid using LD_PRELOAD. Fixes glibc compat i...
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: a4d6e2cf163202b438b2b1af732fa47ea5db5cce https://github.com/NixOS/nixpkgs/commit/a4d6e2cf163202b438b2b1af732fa47ea5db5cce Author: Benno Fünfstück Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/applications/editors/atom/default.nix M pkgs/applications/editors/atom/env.nix Log Message: --- atom: avoid using LD_PRELOAD. Fixes glibc compat issues The wrapper for Atom was loading libraries via LD_PRELOAD, for example libxkbfile. Now, if you installed atom via nix-env and happened to use a newer nixpkgs for that than what your system environment is build against, you could end up with an error like this: ``` uname: relocation error: /nix/store/68sa3m89shpfaqq1b9xp5p1360vqhwx6-glibc-2.25/lib/libdl.so.2: symbol _dl_catch_error, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference ``` This happens because atom calls the `uname` executable from the system to determine the platform. Because that inherits the `LD_PRELOAD` environment variable, so the libxkbfile library that the `atom` wrapper was build against is loaded into `uname`. But since `atom` comes from `nix-env`, the `libxkbfile` it was built with might be compiled against a newer version of `glibc` than `uname`, which comes from the system, was! Having two versions of glibc loaded into the same processes results in chaos. To fix this, we avoid setting `LD_PRELOAD` and instead use patchelf to set the correct RPATH. RPATH is not inherited by child processes, so the above issue can no longer occur. The only small complication here is that the library that actually loads libxkbfile is not the atom binary itself, but a node extension that atom uses. So instead of setting the RPATH on `atom` only, we also set the `rpath` on all node extensions (`*.node`) the output. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] The Church of Suckless NixOS is looking for followers
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. > > ... This probably won't be of practical use to me since I have other issues with NixOS, but I'd like to show my support for this: Having enough interest to get forked is certainly a good thing. Who knows, maybe NixOS will join the ranks of other distros with spin-offs. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] How do you work on big packages?
nix-shell on its installPhase has no rights to write to /nix/store, installPhase always fails. I am thinking about something like converting a derivation (a .drv file) into two files: 1. a .sh file, which would do unpackPhase, patchPhase, configurePhase, buildPhase using the current directory, not something in /tmp. nix-shell fits very well here. Ideally, this script just launches nix-shell to perform these phases. 2. a .nix file with src= pointing to the build directory made by the previous script and performs buildPhase, checkPhase, installPhase, fixupPhase. this .nix file could be used substitute a .nix file in all-packages.nix during troubleshooting. So buildPhase is performed twice (we assume it is to be idempotent, isn't it?), second time quickly because all .o files are already compiled. And it would automatically recompile only changed sources. In practice, it is not so beautiful. For example, kernel derivation sets environment variables in preUnpack then uses in buildPhase so it would be a trouble to simply skip all the phases before buildPhase. On 3/17/17, Profpatsch wrote: > On 17-03-17 06:04pm, Volth wrote: >> "nix-shell" would be a super option here if it could handle >> "installPhase" (this seems easy to fix) and .nix files less trivial >> than "hello.nix" (this seems not easy to fix; for example "nix-shell >> '' -A linux_4_4" has no "configurePhase", and there are >> similar problems with almost every of the big projects; nix-shell >> launches "make" when "nix-build" launches "cmake" or vice-versa, etc) > > That’s a pretty common stumbling block. > > If someone defines his own `installPhase` for example, > the `installPhase` shell function is just the standard > stdenv `installPhase`. What you want to call is rather > the contents of `$installPhase` (the variable), since > that contains the phase you defined in `mkDerivation`. > > nix-shell > $ unpackPhase > unpacking … > $ configurePhase > configuring … > $ buildPhase > … > $ $installPhase > running your installPhase > > > There is not much abstraction. Every nix attribute within > `derivation` (and by extension `mkDerivation`) will end up > as a bash shell variable in your shell (and your build env). > > -- > Proudly written in Mutt with Vim on NixOS. > Q: Why is this email five sentences or less? > A: http://five.sentenc.es > May take up to five days to read your message. If it’s urgent, call me. > ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 63f1a1: neo4j service: increase file limit, per warning em...
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 63f1a14ae551f650584ac7502b5ee159221d1f92 https://github.com/NixOS/nixpkgs/commit/63f1a14ae551f650584ac7502b5ee159221d1f92 Author: Will Dietz Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M nixos/modules/services/databases/neo4j.nix Log Message: --- neo4j service: increase file limit, per warning emitted at startup (#23961) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] f9f15f: irker: init at 2017-02-12
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: f9f15fff56c669282b3e19eb4f471765e0ca6e7e https://github.com/NixOS/nixpkgs/commit/f9f15fff56c669282b3e19eb4f471765e0ca6e7e Author: Will Dietz Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: A pkgs/servers/irker/default.nix M pkgs/top-level/all-packages.nix Log Message: --- irker: init at 2017-02-12 Commit: 2807d75dca3121992a7857254727ce91228bc80e https://github.com/NixOS/nixpkgs/commit/2807d75dca3121992a7857254727ce91228bc80e Author: Will Dietz Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M nixos/modules/module-list.nix A nixos/modules/services/misc/irkerd.nix Log Message: --- irkerd service: init Commit: 9a976c09ba9b810a8ef0cd0ce9a6e60b26eaad87 https://github.com/NixOS/nixpkgs/commit/9a976c09ba9b810a8ef0cd0ce9a6e60b26eaad87 Author: Joachim F Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M nixos/modules/module-list.nix A nixos/modules/services/misc/irkerd.nix A pkgs/servers/irker/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Merge pull request #23963 from dtzWill/feature/irkerd irker: init at 2017-02-12 Compare: https://github.com/NixOS/nixpkgs/compare/953616907493...9a976c09ba9b___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] How do you work on big packages?
On 17-03-17 05:34pm, Dmitry Kalinkin wrote: > Also it is funny how your statement is followed by some good advice on how to > turn nix into even better dev platform. I will only add that one could also > use ccache to speedup builds: > > my_cool_package.override { stdenv = pkgs.ccacheStdenv; } Caches will burn you. You should never mix non-deterministic caching with deployment. There’s just no way it will work out in all cases. -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A: http://five.sentenc.es May take up to five days to read your message. If it’s urgent, call me. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 953616: nixos/treewide: remove boolean examples for option...
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 953616907493c5b81ba3ec9dd86f1422f4d1fcd3 https://github.com/NixOS/nixpkgs/commit/953616907493c5b81ba3ec9dd86f1422f4d1fcd3 Author: Franz Pletz Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M nixos/modules/installer/cd-dvd/iso-image.nix M nixos/modules/programs/adb.nix M nixos/modules/programs/gphoto2.nix M nixos/modules/programs/mosh.nix M nixos/modules/programs/ssmtp.nix M nixos/modules/programs/tmux.nix M nixos/modules/programs/vim.nix M nixos/modules/security/grsecurity.nix M nixos/modules/services/backup/rsnapshot.nix M nixos/modules/services/computing/boinc/client.nix M nixos/modules/services/databases/cassandra.nix M nixos/modules/services/databases/openldap.nix M nixos/modules/services/editors/emacs.nix M nixos/modules/services/mail/offlineimap.nix M nixos/modules/services/misc/ihaskell.nix M nixos/modules/services/misc/taskserver/default.nix M nixos/modules/services/monitoring/arbtt.nix M nixos/modules/services/networking/aiccu.nix M nixos/modules/services/networking/ferm.nix M nixos/modules/services/networking/firefox/sync-server.nix M nixos/modules/services/networking/mosquitto.nix M nixos/modules/services/networking/quagga.nix M nixos/modules/services/networking/znc.nix M nixos/modules/services/scheduling/cron.nix M nixos/modules/services/security/haka.nix M nixos/modules/services/torrent/deluge.nix M nixos/modules/services/web-apps/atlassian/crowd.nix M nixos/modules/services/web-apps/atlassian/jira.nix M nixos/modules/services/web-servers/caddy.nix M nixos/modules/services/x11/compton.nix M nixos/modules/services/x11/desktop-managers/enlightenment.nix M nixos/modules/services/x11/desktop-managers/gnome3.nix M nixos/modules/services/x11/desktop-managers/kodi.nix M nixos/modules/services/x11/desktop-managers/xterm.nix M nixos/modules/services/x11/hardware/libinput.nix M nixos/modules/services/x11/hardware/multitouch.nix M nixos/modules/services/x11/hardware/synaptics.nix M nixos/modules/services/x11/redshift.nix M nixos/modules/services/x11/unclutter-xfixes.nix M nixos/modules/services/x11/unclutter.nix M nixos/modules/services/x11/urxvtd.nix M nixos/modules/services/x11/window-managers/exwm.nix M nixos/modules/services/x11/window-managers/xmonad.nix M nixos/modules/system/boot/loader/grub/grub.nix M nixos/modules/tasks/filesystems/zfs.nix M nixos/modules/tasks/network-interfaces.nix M nixos/modules/virtualisation/containers.nix Log Message: --- nixos/treewide: remove boolean examples for options They contain no useful information and increase the length of the autogenerated options documentation. See discussion in #18816. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] b94431: emacs: fix runtime GTK3 dependencies
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: b944312eb536b9b6d7722d334fa470c0bb46e54a https://github.com/NixOS/nixpkgs/commit/b944312eb536b9b6d7722d334fa470c0bb46e54a Author: Nikolay Amiantov Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/applications/editors/emacs/default.nix Log Message: --- emacs: fix runtime GTK3 dependencies Fixes #23845. (cherry picked from commit a8785daf0ea794f1791c598c6cac9db3858b45bb) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] a8785d: emacs: fix runtime GTK3 dependencies
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: a8785daf0ea794f1791c598c6cac9db3858b45bb https://github.com/NixOS/nixpkgs/commit/a8785daf0ea794f1791c598c6cac9db3858b45bb Author: Nikolay Amiantov Date: 2017-03-18 (Sat, 18 Mar 2017) Changed paths: M pkgs/applications/editors/emacs/default.nix Log Message: --- emacs: fix runtime GTK3 dependencies Fixes #23845. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 6cc120: marathonctl: init at 2017-03-06
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 6cc1200bd586dc8eeb930bbc3a25299ea27e5409 https://github.com/NixOS/nixpkgs/commit/6cc1200bd586dc8eeb930bbc3a25299ea27e5409 Author: Michael Fellinger Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: A pkgs/tools/virtualization/marathonctl/default.nix A pkgs/tools/virtualization/marathonctl/deps.nix M pkgs/top-level/all-packages.nix Log Message: --- marathonctl: init at 2017-03-06 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] How do you work on big packages?
What I meant in the original question is more about troubleshooting than development. That development is incorporated in the deployment chain all other steps are already powered by nix: build a (patched) kernel, then build system closures with it, then test-driver scripts, then deploy/run them... On 3/17/17, Vladimír Čunát wrote: > On 03/17/2017 10:34 PM, Dmitry Kalinkin wrote: >> Also it is funny how your statement is followed by some good advice >> on how to turn nix into even better dev platform. I will only add >> that one could also use ccache to speedup builds: > > I do believe the intention was for "SW distribution" etc, at least > primarily, and the suitability for development is a by-product due to > some properties, e.g. easy (non-)mixing of development and stable > versions/configs. Marc can surely remember the earlier days of NixOS. > > It's even possible to use nix-build instead of make to compile > individual files, but there it just doesn't seem to be very suitable... > > ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 25d450: KDE Applications: 16.12.2 -> 16.12.3
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 25d450c0674e388bad60f25ceca4817deb601c50 https://github.com/NixOS/nixpkgs/commit/25d450c0674e388bad60f25ceca4817deb601c50 Author: Thomas Tuegel Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/applications/kde/fetch.sh M pkgs/applications/kde/srcs.nix Log Message: --- KDE Applications: 16.12.2 -> 16.12.3 (cherry picked from commit 06ece41778ff3c06dbb4fad0f87e888ca6c9889d) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] How do you work on big packages?
On 03/17/2017 10:34 PM, Dmitry Kalinkin wrote: > Also it is funny how your statement is followed by some good advice > on how to turn nix into even better dev platform. I will only add > that one could also use ccache to speedup builds: I do believe the intention was for "SW distribution" etc, at least primarily, and the suitability for development is a by-product due to some properties, e.g. easy (non-)mixing of development and stable versions/configs. Marc can surely remember the earlier days of NixOS. It's even possible to use nix-build instead of make to compile individual files, but there it just doesn't seem to be very suitable... smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Questions about the all-packages fixpoint
On Fri, Mar 17, 2017 at 9:38 PM, Benno Fünfstück wrote: > One thing that is nicer about `self.callPackage` though is that you can > follow the rule "whenever taking something from self does not lead infinite > recursion, take it from self" when writing overrides. And we should not advertise that, because this would lead to packages which are not patched, under the rules of the future security-update work. So whatever you think this is simpler or not, this is incorrect, I guess we could nullify these functions in the latest layer, preventing callPackage to ever be used through `self`. -- Nicolas Pierron http://www.linkedin.com/in/nicolasbpierron - http://nbp.name/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] How do you work on big packages?
> On 17 Mar 2017, at 12:48, Marc Weber wrote: > > Nix is 'software distribution platform', not a dev platform. I never could understand this. Some people are also saying that nix-shell is sometimes not being used in the "intended way". However, nix developers seem to not be aware: https://github.com/NixOS/nix/blob/1.11-maintenance/dev-shell Also it is funny how your statement is followed by some good advice on how to turn nix into even better dev platform. I will only add that one could also use ccache to speedup builds: my_cool_package.override { stdenv = pkgs.ccacheStdenv; } > > Depending on the task other solutions might be better. > > For instance restarting nginx/ apache the nixos way is also slower than > edit/restart cycle on 'debian'. So use the right tool / env for your > job. > > There was a hack to impurely rewrite some dependencies for security > reasons - forgot about it - so maybe you can force impurity to speed up > your workflow. > > In the kernel case hat takes most time will be 'building it', thus you > can try 'get compiled data' from your directory (binary distribution) > like, then use something like nixos build-vm or such (disk caching > reasons - no restart required). > > You can also try creating links to your 'dev' directory and switch off > sandoxing and add a 'dummy env vars' which you increment to force > rebuilding. > > Marc Weber > ___ > 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-commits] [NixOS/nixpkgs] ae1c27: linux: 4.4.53 -> 4.4.54
Branch: refs/heads/release-16.09 Home: https://github.com/NixOS/nixpkgs Commit: ae1c270479c09c957f2d35dabcec05951e8ee3fb https://github.com/NixOS/nixpkgs/commit/ae1c270479c09c957f2d35dabcec05951e8ee3fb Author: Tim Steinbach Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/os-specific/linux/kernel/linux-4.4.nix Log Message: --- linux: 4.4.53 -> 4.4.54 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] ca750a: linux: 4.4.53 -> 4.4.54
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: ca750a5320998ef83c8a6e24dfae989ca903ed0d https://github.com/NixOS/nixpkgs/commit/ca750a5320998ef83c8a6e24dfae989ca903ed0d Author: Tim Steinbach Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/os-specific/linux/kernel/linux-4.4.nix Log Message: --- linux: 4.4.53 -> 4.4.54 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] ca3fb4: linux: 4.4.53 -> 4.4.54
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: ca3fb4d1d406ab20f7fc3ade0fb92ec0a9d077d1 https://github.com/NixOS/nixpkgs/commit/ca3fb4d1d406ab20f7fc3ade0fb92ec0a9d077d1 Author: Tim Steinbach Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/os-specific/linux/kernel/linux-4.4.nix Log Message: --- linux: 4.4.53 -> 4.4.54 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 5579e8: linux: 4.10.2 -> 4.10.3
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 5579e817830d1da30e388758176f6ce5976e3bea https://github.com/NixOS/nixpkgs/commit/5579e817830d1da30e388758176f6ce5976e3bea Author: Tim Steinbach Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/os-specific/linux/kernel/linux-4.10.nix Log Message: --- linux: 4.10.2 -> 4.10.3 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 81ad24: linux: 4.10.2 -> 4.10.3
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 81ad24d4d7ff93d0382f25ff8d963f4627c557fc https://github.com/NixOS/nixpkgs/commit/81ad24d4d7ff93d0382f25ff8d963f4627c557fc Author: Tim Steinbach Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/os-specific/linux/kernel/linux-4.10.nix Log Message: --- linux: 4.10.2 -> 4.10.3 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] How do you work on big packages?
On 03/17/2017 07:04 PM, Volth wrote: > "nix-shell" would be a super option here if it could handle > "installPhase" For my paid work (upstream) I'm perfectly comfortable with nix-shell on an expression that is slightly modified from the nixpkgs version. I solve the installing just by specifying prefix to ./install, so `make install` does what I need. Almost all of the modifications are boring - just for easy switching of various options, such as compiler flag sets, gcc/clang, CI tests, etc. Maybe I'm just lucky with the packages I worked with, and they're no big beasts like kernel or chromium, too :-) --Vladimir smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 06ece4: KDE Applications: 16.12.2 -> 16.12.3
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 06ece41778ff3c06dbb4fad0f87e888ca6c9889d https://github.com/NixOS/nixpkgs/commit/06ece41778ff3c06dbb4fad0f87e888ca6c9889d Author: Thomas Tuegel Date: 2017-03-12 (Sun, 12 Mar 2017) Changed paths: M pkgs/applications/kde/fetch.sh M pkgs/applications/kde/srcs.nix Log Message: --- KDE Applications: 16.12.2 -> 16.12.3 Commit: 73ccc49448447174a198dd6feeb339eb6740844c https://github.com/NixOS/nixpkgs/commit/73ccc49448447174a198dd6feeb339eb6740844c Author: Thomas Tuegel Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/applications/kde/fetch.sh M pkgs/applications/kde/srcs.nix Log Message: --- Merge pull request #23992 from ttuegel/kde-applications-16.12.3 KDE Applications: 16.12.2 -> 16.12.3 Compare: https://github.com/NixOS/nixpkgs/compare/1129f92f6548...73ccc4944844___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] Questions about the all-packages fixpoint
Hi Nicolas, thank you for the answer, that clears up must of my questions. I do think that `self` is pretty standard throughout nixpkgs (at least the parts that I have worked with) for exactly this fixpoint construction, thus the name conflict is a little unfortuntate, but seems we cannot do much about that right now. However, I am still unsure what you mean with If `super.callPackage` were taking all its arguments from `super`, then this would imply that you could not easily override the argument of packages which are inside the dependencies of another one. By taking the packages from `self`, we can easily replace it for all its uses. Well, that's why you should almost never use `super.callPackage`. I would imagine that inside of `all-packages.nix`, at the top, we would have something like: `let callPackage = self.callPackage in ... ` so that all occurences of `callPackage` refer to `self.callPackage`, yet `pkgs.callPackage` only looks inside the scope of `pkgs`. There's only one problem I see with this, when packages take what is called `self` in all-packages.nix directly as an argument, but I think they should take `pkgs` instead anyway. For me, it feels like `super.callPackage` calls something in the scope of `super`, but perhaps that only makes more sense to me because I'm used to it. Now that I think of it, there's an argument for `super.callPackage` to take the deps from `self` as well: that way, `foo = super.callPackage path/to/foo {}; ` is equavilent to `super.foo` if foo is defined like that in `super`. One thing that is nicer about `self.callPackage` though is that you can follow the rule "whenever taking something from self does not lead infinite recursion, take it from self" when writing overrides. -- Benno ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Questions about the all-packages fixpoint
Hi Benno, Before answering, let me give you a brief intro to the fix-extend function combo. The extend function is similar to the update operator of Nix `//`, the main difference is that it give its left-hand side (`super`) as argument to its right hand side. But this extend function give an extra argument (`self`) to all its arguments. When chaining these extend function, the `self` argument is the same for the all layers. When a fix point is applied to this chain of extend function, `self` corresponds to the last set produced by the extend function chain. Note that using `self` can easily cause infinite recursion, for example if the addition of an attribute to the set depends on the presence of an attribute in `self`. On Fri, Mar 17, 2017 at 5:04 PM, Benno Fünfstück wrote: > 2. In `stage.nix`, why do we construct a *local* fixpoint just for > all-packages? The current code is: > > allPackages = self: super: > let res = import ./all-packages.nix > { inherit lib nixpkgsFun noSysDirs config; } > res self; > in res; > > Even more confusingly, if we look at `all-packages.nix`, it is a function > defined like this: > > { lib, nixpkgsFun, noSysDirs, config}: > self: pkgs: > > So the variable that is called `self` in `stage.nix` is bound to what is > called `pkgs` in `all-packages.nix`, and `self` in `all-packages.nix` > actually refers to what is called `res` in `stage.nix` This is because this code is still legacy before the introduction of the extend function. We should not use this `self` argument under all-packages.nix, but last time I tried to avoid changing any hashes. Another reason why I did not address this, such as renaming it because `self` is quite an overloaded name, and a naive search and replace would not work as expected. Note, there is also a package named `self`, for interpreting the Self language. So `pkgs` of all-packages.nix is literaly the result of the fix-point, given to all overlays under the name `self`. > 1. An override is given the arguments `self` and `super`, as expected. But > why does `super.callPackage` resolve dependencies from `self`? `callPackage` take a function as argument, or a path to a function, and list the arguments of it. It then create a set with the requested argument and a set given as argument. In `top-level/splice.nix`, the callPackage function is given an argument which is constructed from the result of the fix-point. Thus `super.callPackage` will fill the arguments of the functions with the value taken within the result of the fix-point. > I would have > expected it to not know about `self`, and resolve dependencies in the scope > of `super`. If I wanted this behaviour, I would have used > `self.callPackage`, but the current behaviour makes that unnecessary. Why is > this implemented like that? The history of all-packages.nix used to be that we had a "rec" keyword on top of the attribute set. Then we added the `self` reference that you complained about in (2) in order to be able to override packages. If `super.callPackage` were taking all its arguments from `super`, then this would imply that you could not easily override the argument of packages which are inside the dependencies of another one. By taking the packages from `self`, we can easily replace it for all its uses. > This is confusing to me. Also, why do we need `self` and `pkgs`? Wouldn't > one of them be enough? Yes, but again, renaming these variables is hard without the proper tooling to guarantee that we are not making any mistake. -- Nicolas Pierron http://www.linkedin.com/in/nicolasbpierron - http://nbp.name/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] NixOps: distributed builds, arm7vl
Hi Théophane, thank you for the reply. > On Mar 17, 2017, at 9:13 AM, Théophane Hufschmitt wrote: > > 2. Yes, it works without problem. In fact NixOps isn't concerned about > the architecture of your machine, it just forwards the config to nix > which builds it. But you have to specify the architecture in the > configuration of your machine for nix to know about it. In my case it > was just setting `nixpkgs.system = "armv7l-linux"` in my bananaPi's > configuration. I missed this step after looking around in the NixOS and NixOps documentation for something like that to no avail, and broke my armv7l box! (NixOps pushed some x86-64 binaries to it, whoops.) Thanks for the pointer. > 3. Yes again, by using nix's distributed builds feature (see the > `nix.buildMachines` and `nix.distributedBuilds` nixos options and > https://nixos.org/nix/manual/#chap-distributed-builds if you don't know > how to set it up), you got what you want (and if you don't explicitly > specify you boards as build machines, nothing will be built on them). That is great to hear. Thanks again for the reply! I’ll try all of this out this weekend and post an update on my progress next week. d ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] How do you work on big packages?
On 17-03-17 06:04pm, Volth wrote: > "nix-shell" would be a super option here if it could handle > "installPhase" (this seems easy to fix) and .nix files less trivial > than "hello.nix" (this seems not easy to fix; for example "nix-shell > '' -A linux_4_4" has no "configurePhase", and there are > similar problems with almost every of the big projects; nix-shell > launches "make" when "nix-build" launches "cmake" or vice-versa, etc) That’s a pretty common stumbling block. If someone defines his own `installPhase` for example, the `installPhase` shell function is just the standard stdenv `installPhase`. What you want to call is rather the contents of `$installPhase` (the variable), since that contains the phase you defined in `mkDerivation`. nix-shell $ unpackPhase unpacking … $ configurePhase configuring … $ buildPhase … $ $installPhase running your installPhase There is not much abstraction. Every nix attribute within `derivation` (and by extension `mkDerivation`) will end up as a bash shell variable in your shell (and your build env). -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A: http://five.sentenc.es May take up to five days to read your message. If it’s urgent, call me. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] The Church of Suckless NixOS is looking for followers
Profpatsch writes: > On 17-03-17 02:00pm, Jan Malakhovski wrote: >> >> Brothers and Sisters! >> >> * Our common goal is to have fun (see below) and to get a NixOS system >> that can run using only suckless tools [1]. > > I, for one, applaud our new anonymous suckless leaders! > On an offhand note, be advised that suckleast.org is already taken. We don't plan to register any domains, AFAIK. >> * 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. > > rolf > >> We want suckless tools instead of GNU. Sh instead of Bash. Coreboot >> instead of GRUB and BIOS and so on. > > gl hf thx > T. systemd fanboi :( Cheers, Jan ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] The Church of Suckless NixOS is looking for followers
Stefan Huchler writes: >> * Our common goal is to have fun (see below) and to get a NixOS system >> that can run using only suckless tools [1]. > > which is a subject oppinion, which tools does suck and which not. > Correct. >> * 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, > >> * 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. > > And why is it for the sake of lisp? Have you proof that guixsd chose > lisp just because of lisp despite some disadvantages? What are the > disadvantages of lisp package expressions? We won't argue. You are free to like and use whatever you want. We collectively hate systemd, pulseaudio and dbus and want du -csh $(nix-store -qR /run/current-system) for a usable (for our definition of usable) system to be megabytes, not gigabytes. Putting LISP on top of Nix goes against that goal. > Blooted GNU tools? So you like the horrible inferior tools that come > with android? its always good if software has less features? Yes. No, Android uses Toolbox, not even Busybox, and certainly not Suckless. No, but Suckless provide 90% of the features with 1-10% of the code. See for yourself: http://git.suckless.org/sbase/tree/ http://git.suckless.org/ubase/tree/ and then compare that to the single GNU grep http://git.savannah.gnu.org/cgit/grep.git/tree > So you want to have a distro not only for the 2% linux users but only > for the 1% pc that run with coreboot, I am very optimistic that you will > get much contribution and feedback :) That is a valid point, but you'd be surprised how many people (e.g. most of us) use old Thinkpads. Used ones are super cheap too, so no problem experimenting. Flashing coreboot (after you managed to build it with the correct config and blobs, nix helps here, as always) takes $5 of hardware (+$35 if you or someone you know doesn't have RPi or BB, the RPi and BB, both are then reusable for other cool stuff) and minutes of time. Also, its not like we require you to abolish everything you like to even consider helping the cause. I'm not gonna abolish my XMonad any time soon, regardless of GHC closure size. > But thanks for the post, made me laugh. You are welcome. Cheers, Jan ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 1129f9: file: 5.28 -> 5.30
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 1129f92f6548b9436e16e9f0a776fdbf84c43752 https://github.com/NixOS/nixpkgs/commit/1129f92f6548b9436e16e9f0a776fdbf84c43752 Author: Renaud Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/tools/misc/file/default.nix Log Message: --- file: 5.28 -> 5.30 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] How do you work on big packages?
"nix-shell" would be a super option here if it could handle "installPhase" (this seems easy to fix) and .nix files less trivial than "hello.nix" (this seems not easy to fix; for example "nix-shell '' -A linux_4_4" has no "configurePhase", and there are similar problems with almost every of the big projects; nix-shell launches "make" when "nix-build" launches "cmake" or vice-versa, etc) On 3/17/17, Linus Heckemann wrote: > On 17/03/17 16:00, Volth wrote: >> What could be done here? > nix-shell, and the upstream recommended build procedure. > ___ > 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-commits] [NixOS/nixpkgs] 7196d1: shapelib: init at 1.4.0
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 7196d16e3fc4c214c94f8d5ff4ed515d27c17152 https://github.com/NixOS/nixpkgs/commit/7196d16e3fc4c214c94f8d5ff4ed515d27c17152 Author: Emery Hemingway Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: A pkgs/development/libraries/shapelib/default.nix M pkgs/top-level/all-packages.nix Log Message: --- shapelib: init at 1.4.0 Commit: fa65cc067b3bbdf4d4cdfb21f24009c297334b28 https://github.com/NixOS/nixpkgs/commit/fa65cc067b3bbdf4d4cdfb21f24009c297334b28 Author: Emery Hemingway Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: A pkgs/applications/misc/xastir/default.nix M pkgs/top-level/all-packages.nix Log Message: --- xaster: init at release 208 Compare: https://github.com/NixOS/nixpkgs/compare/427edf1e5d67...fa65cc067b3b___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] The Church of Suckless NixOS is looking for followers
Jan Malakhovski (The ephemeral self-proclaimed Pope of SLNOS) writes: > * Our common goal is to have fun (see below) and to get a NixOS system > that can run using only suckless tools [1]. which is a subject oppinion, which tools does suck and which not. > * 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, So you want to have a distro not only for the 2% linux users but only for the 1% pc that run with coreboot, I am very optimistic that you will get much contribution and feedback :) > * 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. And why is it for the sake of lisp? Have you proof that guixsd chose lisp just because of lisp despite some disadvantages? What are the disadvantages of lisp package expressions? Blooted GNU tools? So you like the horrible inferior tools that come with android? its always good if software has less features? But thanks for the post, made me laugh. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] How do you work on big packages?
Nix is 'software distribution platform', not a dev platform. Depending on the task other solutions might be better. For instance restarting nginx/ apache the nixos way is also slower than edit/restart cycle on 'debian'. So use the right tool / env for your job. There was a hack to impurely rewrite some dependencies for security reasons - forgot about it - so maybe you can force impurity to speed up your workflow. In the kernel case hat takes most time will be 'building it', thus you can try 'get compiled data' from your directory (binary distribution) like, then use something like nixos build-vm or such (disk caching reasons - no restart required). You can also try creating links to your 'dev' directory and switch off sandoxing and add a 'dummy env vars' which you increment to force rebuilding. Marc Weber ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] How do you work on big packages?
On 17/03/17 16:00, Volth wrote: > What could be done here? nix-shell, and the upstream recommended build procedure. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 427edf: robomongo: mark as broken
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 427edf1e5d677795d20ebd8c8729a5f1bee20c96 https://github.com/NixOS/nixpkgs/commit/427edf1e5d677795d20ebd8c8729a5f1bee20c96 Author: Robin Gloster Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/applications/misc/robomongo/default.nix Log Message: --- robomongo: mark as broken ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 9bfa7c: robomongo: mark as broken
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 9bfa7c9c3b81aadbd970be06266febd1aa7c3867 https://github.com/NixOS/nixpkgs/commit/9bfa7c9c3b81aadbd970be06266febd1aa7c3867 Author: Robin Gloster Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/applications/misc/robomongo/default.nix Log Message: --- robomongo: mark as broken (cherry picked from commit 427edf1e5d677795d20ebd8c8729a5f1bee20c96) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] NixOps: distributed builds, arm7vl
Hi Drew, I got a setup quite similar to the one you describe : I got a network managed by nixops consisting of a few x86 machines and an armv7l board (a bananaPi R1, which has exactly the same chipset as the BBB iirc), and forwards builds to an arm machine in the cloud. Short answer : it works fine. More in detail : 1. Not that I know of. The machine that I use as a CnC is itself managed by nixops, and it never raised any problem. 2. Yes, it works without problem. In fact NixOps isn't concerned about the architecture of your machine, it just forwards the config to nix which builds it. But you have to specify the architecture in the configuration of your machine for nix to know about it. In my case it was just setting `nixpkgs.system = "armv7l-linux"` in my bananaPi's configuration. 3. Yes again, by using nix's distributed builds feature (see the `nix.buildMachines` and `nix.distributedBuilds` nixos options and https://nixos.org/nix/manual/#chap-distributed-builds if you don't know how to set it up), you got what you want (and if you don't explicitly specify you boards as build machines, nothing will be built on them). -- Théophane Hufschmitt Wed 15 Mar 17 − 15:01, Drew Hess(ml-nix-...@drewhess.com) a écrit: > Hi all, > > I just wrapped up my first NixOps deployment. It’s lovely! Now I’m > ready to proceed to the next stage, and I could use a little guidance. > Here's where I am currently: > > - I use a dedicated NixOS host, which I manage by hand (i.e., not with > NixOps), as a “command-and-control” (CnC) host for my NixOps > deployments. > > - The current deployment is just 2 x86_64-linux physical hosts. These > machines are fully managed by NixOps from the CnC host. > > Here is where I'd like to get to next: > > - Add multiple BeagleBone Black (armv7l architecture) hosts to the > existing NixOps deployment. These will run various services and > sensors. > > - Use a dedicated armv7l build slave for the armv7l package builds. > The BeagleBone Blacks (BBBs) are seriously underpowered and should > never do their own builds. > > I just installed NixOS on a Jetson TK1. I would like to use it as the > armv7l build slave since it has pretty decent specs for an armv7l > machine. Currently, it is managed by hand, i.e., not in NixOps. > > Here are my questions: > > 1. Are there any potential problems that arise from managing build >slaves that are intended for use in NixOps deployments in the >NixOps deployment itself? Should build slaves be managed by hand, >like the CnC host? I’m not sure how NixOS’s support for >distributed builds interacts and/or interferes with NixOps’s >deployments. > > 2. Does NixOps support both x86_64-linux and armv7l physical host >targets in the same deployment? Do I need to specify that a >particular target is armv7l, or will NixOps figure that out when it >adds the host to the database? > > 3. Is there a way to ensure that NixOps only uses the dedicated armv7l >build slave for armv7l builds, and never performs builds on the >other armv7l targets that it has deployed? I would prefer that >deployments fail — say, because the dedicated build slave is down — >than builds ever happen on the BeagleBones. > > Thanks! > > d > > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev signature.asc Description: PGP signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Questions about the all-packages fixpoint
Hello all, I am (again) wrapping my head around the current construction of the package set. I think I understand how it works, but there's a few subtle details that I feel like they are confusing, bur probably necessary. I would like to understand why: 1. An override is given the arguments `self` and `super`, as expected. But why does `super.callPackage` resolve dependencies from `self`? I would have expected it to not know about `self`, and resolve dependencies in the scope of `super`. If I wanted this behaviour, I would have used `self.callPackage`, but the current behaviour makes that unnecessary. Why is this implemented like that? 2. In `stage.nix`, why do we construct a *local* fixpoint just for all-packages? The current code is: allPackages = self: super: let res = import ./all-packages.nix { inherit lib nixpkgsFun noSysDirs config; } res self; in res; Even more confusingly, if we look at `all-packages.nix`, it is a function defined like this: { lib, nixpkgsFun, noSysDirs, config}: self: pkgs: So the variable that is called `self` in `stage.nix` is bound to what is called `pkgs` in `all-packages.nix`, and `self` in `all-packages.nix` actually refers to what is called `res` in `stage.nix` This is confusing to me. Also, why do we need `self` and `pkgs`? Wouldn't one of them be enough? Greetings, Benno ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] How do you work on big packages?
For example, you are working on patch for kernel or chromium or something huge like this. src= in your x.nix points to a local working directory, so every change would result in rebuilding of the deviation and its dependants. Nice so far. The problem is any change implies full rebuild, because .o files are not preserved between the builds, and in case of big projects it takes hours instead of seconds. What could be done here? An nix-build option to forcible preserve tmp directories (--just-keep-and-reuse-tmp-i-know-what-i-am-doing) ? ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Teamviewer will not connect to remote machine
Hi. I am trying to use the TeamViewer client on NixOS. I added `teamviewer` to my `environment.systemPackages` in `configuration.nix`, and set services.teamviewer.enable = true; Mostly, after boot, the client complains about no network connection being available, but after restarting teamviewerd, I can log in to my account. However, after when I select my remote machine, and try to connect to it, the teamviewer main window minimizes, but no remote connection window shows, as it would do normally. My first guess is that, since everything is in wine, there is some problem with spawning another windows process. However, I have now idea how to confirm that. It works inside my Win10 VM and it works inside my Debian VM, so it cannot be a problem with my account or remote machine. I would appreciate any help. I don't even know how to further investigate on this problem. Journalctl does not say anything, and the stdout of teamviewer also has no info. The gui.log sais, when trying to connect, fixme:nls:GetGeoInfoW -1 4 0x1dee2ec 3 0 fixme:nls:GetGeoInfoW -1 4 0x1dee2ec 3 0 fixme:nls:GetGeoInfoW -1 4 0x1dee2ec 3 0 fixme:nls:GetGeoInfoW -1 4 0x1dee2ec 3 0 fixme:nls:GetGeoInfoW -1 8 (nil) 0 0 The file TeamViewer12_Logfile.log contains lots of entries like 2017/03/17 16:41:35.393 8 9 GX0! TeamViewer.exe: unable to send command 7 2017/03/17 16:41:36.393 8 9 GX0! TeamViewer.exe: unable to send command 7 2017/03/17 16:41:37.393 8 9 GX0! TeamViewer.exe: unable to send command 7 Best Regards, Christoph-Simon Senjak ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 6d25f7: nixos: tor: add enableGeoIP
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 6d25f77a643762d718c49ab3fc86e0262d2d38fd https://github.com/NixOS/nixpkgs/commit/6d25f77a643762d718c49ab3fc86e0262d2d38fd Author: Jan Malakhovski Date: 2017-03-16 (Thu, 16 Mar 2017) Changed paths: M nixos/modules/services/security/tor.nix Log Message: --- nixos: tor: add enableGeoIP Commit: a04782581a96d5ee8b4001701432599959ac2dc2 https://github.com/NixOS/nixpkgs/commit/a04782581a96d5ee8b4001701432599959ac2dc2 Author: Jan Malakhovski Date: 2017-03-16 (Thu, 16 Mar 2017) Changed paths: M nixos/modules/services/security/torify.nix Log Message: --- nixos: torify: disable by default, add some documentation as of why This `tsocks` wrapper leaks DNS requests to clearnet, meanwhile Tor comes with `torsocks` which doesn't. Previous commits to this file state that all of this still useful somehow. Assuming that it's true, at least let's not confuse users with two different tools and don't clash with the `tsocks` binary from nixpkgs by disabling this by default. Commit: 01f8e2161c5a89cba6e3efba128fa0b963c8aaea https://github.com/NixOS/nixpkgs/commit/01f8e2161c5a89cba6e3efba128fa0b963c8aaea Author: Joachim F Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M nixos/modules/services/security/tor.nix M nixos/modules/services/security/torify.nix Log Message: --- Merge pull request #23962 from oxij/nixos/tor-sec nixos: tor: usability and security fixes Compare: https://github.com/NixOS/nixpkgs/compare/3728143cbcea...01f8e2161c5a___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] ca4ae4: prometheus-unifi-exporter: init at 0.4.0
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: ca4ae433dbc9b20f82534c0e4cdd2816e3dd43d9 https://github.com/NixOS/nixpkgs/commit/ca4ae433dbc9b20f82534c0e4cdd2816e3dd43d9 Author: Pascal Bach Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M nixos/modules/module-list.nix A nixos/modules/services/monitoring/prometheus/unifi-exporter.nix A pkgs/servers/monitoring/prometheus/unifi-exporter/default.nix A pkgs/servers/monitoring/prometheus/unifi-exporter/deps.nix M pkgs/top-level/all-packages.nix Log Message: --- prometheus-unifi-exporter: init at 0.4.0 (cherry picked from commit 3728143cbcead48f387dd7297f76138a82ed04de) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 372814: prometheus-unifi-exporter: init at 0.4.0
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 3728143cbcead48f387dd7297f76138a82ed04de https://github.com/NixOS/nixpkgs/commit/3728143cbcead48f387dd7297f76138a82ed04de Author: Pascal Bach Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M nixos/modules/module-list.nix A nixos/modules/services/monitoring/prometheus/unifi-exporter.nix A pkgs/servers/monitoring/prometheus/unifi-exporter/default.nix A pkgs/servers/monitoring/prometheus/unifi-exporter/deps.nix M pkgs/top-level/all-packages.nix Log Message: --- prometheus-unifi-exporter: init at 0.4.0 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] The Church of Suckless NixOS is looking for followers
On 17-03-17 02:00pm, Jan Malakhovski wrote: > > Brothers and Sisters! > > * Our common goal is to have fun (see below) and to get a NixOS system > that can run using only suckless tools [1]. I, for one, applaud our new anonymous suckless leaders! On an offhand note, be advised that suckleast.org is already taken. > * 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. rolf > We want suckless tools instead of GNU. Sh instead of Bash. Coreboot > instead of GRUB and BIOS and so on. gl hf T. systemd fanboi -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A: http://five.sentenc.es May take up to five days to read your message. If it’s urgent, call me. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 15cc79: icewm: fix CFGDIR
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 15cc79581724a745ecaf1f3a6a4add5bfd899510 https://github.com/NixOS/nixpkgs/commit/15cc79581724a745ecaf1f3a6a4add5bfd899510 Author: Volth Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/applications/window-managers/icewm/default.nix Log Message: --- icewm: fix CFGDIR (cherry picked from commit fd61a33d2b42d86215c1697c8da11218279ac802) Commit: 0786d9f4ad09b1b52ab3800240749889a83c6fb5 https://github.com/NixOS/nixpkgs/commit/0786d9f4ad09b1b52ab3800240749889a83c6fb5 Author: Profpatsch Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M nixos/modules/services/mail/mlmmj.nix Log Message: --- modules/mlmmj: fix a typo in listaddress folder (cherry picked from commit 6da60bb10142ba2e63309da048044026f7158d0a) Commit: 05fcddf977485848c5d3b40141bd23823003df5c https://github.com/NixOS/nixpkgs/commit/05fcddf977485848c5d3b40141bd23823003df5c Author: Léo Gaspard Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M nixos/modules/security/dhparams.nix Log Message: --- dhparams module: condition on enable option (#23661) Hence, the init/cleanup service only runs when the dhparams module is enabled. (cherry picked from commit 66e54f25a160ed1cd9d0a008c2c61f9c30a84eb1) Commit: 8cff9b9ccfe2b877ba2880d93b6b4eefada72926 https://github.com/NixOS/nixpkgs/commit/8cff9b9ccfe2b877ba2880d93b6b4eefada72926 Author: Linus Heckemann Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/interpreters/renpy/default.nix Log Message: --- renpy: mark as broken (cherry picked from commit 9b62e41c1e13c363b679f07f4f677cfa2e6c2acd) Commit: 7b401c71ce644bc131139037829decc4f31ac83d https://github.com/NixOS/nixpkgs/commit/7b401c71ce644bc131139037829decc4f31ac83d Author: Michael Raskin <7c6f4...@mail.ru> Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M nixos/tests/firefox.nix Log Message: --- nixos: tests: firefox: make more comprehensive Run Firefox inside an XTerm, it doesn't crash mysteriously this way. Also try opening developer tools and checking that Firefox doesn't crash in the process. (cherry picked from commit 14a3412048473e022e4bc2c687c66bb5f30c0e42) Commit: fadb858e880326bb1f6ec95598b369e9f76c3caf https://github.com/NixOS/nixpkgs/commit/fadb858e880326bb1f6ec95598b369e9f76c3caf Author: Kamil Chmielewski Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/compilers/ponyc/default.nix M pkgs/development/compilers/ponyc/pony-stable.nix Log Message: --- ponyc: 0.11.0 -> 0.11.3 (cherry picked from commit 017fddb4be7d5c074a0b3e2dfb26b88d5e90ceaf) Compare: https://github.com/NixOS/nixpkgs/compare/3879491de261...fadb858e8803___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 017fdd: ponyc: 0.11.0 -> 0.11.3
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 017fddb4be7d5c074a0b3e2dfb26b88d5e90ceaf https://github.com/NixOS/nixpkgs/commit/017fddb4be7d5c074a0b3e2dfb26b88d5e90ceaf Author: Kamil Chmielewski Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/compilers/ponyc/default.nix M pkgs/development/compilers/ponyc/pony-stable.nix Log Message: --- ponyc: 0.11.0 -> 0.11.3 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] aed491: docker: 1.13.1 -> 17.03.0-ce
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: aed491879588bb92bc6e5c264dd336a631d83903 https://github.com/NixOS/nixpkgs/commit/aed491879588bb92bc6e5c264dd336a631d83903 Author: Tim Steinbach Date: 2017-03-14 (Tue, 14 Mar 2017) Changed paths: M pkgs/applications/virtualization/docker/default.nix Log Message: --- docker: 1.13.1 -> 17.03.0-ce Commit: f1c2d047ed1290e731ba53d36203ae9f770cfa8b https://github.com/NixOS/nixpkgs/commit/f1c2d047ed1290e731ba53d36203ae9f770cfa8b Author: Tim Steinbach Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/applications/virtualization/docker/default.nix Log Message: --- Merge pull request #23872 from NeQuissimus/docker_17_03_0 docker: 1.13.1 -> 17.03.0-ce Compare: https://github.com/NixOS/nixpkgs/compare/273e480379b2...f1c2d047ed12___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-dev] The Church of Suckless NixOS is looking for followers
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 always leave source tarballs intact (some of us do exactly that with hacks)? Easy. Want custom queries? Trivial. Just imagine: * `nix-store --gc -A gc-no-src` (`--gc` gives gc roots to `gc-no-src` and checks `gc-no-src` doesn't leave any orphans with its returned list of to-be-removed paths, then cleans them up as usual), * `nix-store --gc -A gc-no-src $derivations` (as before, but start collecting from `$derivations`) * `nix-store --realize -A list-all-sources $derivation` (run `list-all-sources` on `$derivation` and realize all those paths. yes, this can be done with a crazy shell command already, but this is much more generic) * now the blasphemous idea trivially follows from above: `nix-store --realize -A list-all-sources`
[Nix-commits] [NixOS/nixpkgs] 273e48: rustNightlyBin: 2017-01-26 -> 2017-03-16 (#23988)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 273e480379b233b91c327e9e63746f387d764851 https://github.com/NixOS/nixpkgs/commit/273e480379b233b91c327e9e63746f387d764851 Author: Jörg Thalheim Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/compilers/rust/nightlyBin.nix Log Message: --- rustNightlyBin: 2017-01-26 -> 2017-03-16 (#23988) thanks! ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] b4fd04: pygame_sdl2: init at 6.99.10.1227
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: b4fd04c395e868af9cc70cbc3729ff6cb230ad00 https://github.com/NixOS/nixpkgs/commit/b4fd04c395e868af9cc70cbc3729ff6cb230ad00 Author: Michael Raskin <7c6f4...@mail.ru> Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/top-level/python-packages.nix Log Message: --- pygame_sdl2: init at 6.99.10.1227 Commit: 8388cb8bff25f2e0689e7fed239d84c1da5ad5e6 https://github.com/NixOS/nixpkgs/commit/8388cb8bff25f2e0689e7fed239d84c1da5ad5e6 Author: Michael Raskin <7c6f4...@mail.ru> Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/interpreters/renpy/default.nix Log Message: --- renpy: 6.17.6 -> 6.99.12.4; still a strange mistake on launch Compare: https://github.com/NixOS/nixpkgs/compare/8c00f3432aee...8388cb8bff25___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 934c8c: callCabal2nix: Fixed indentation
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 934c8c7a93126090f786f9d061190cf84e7d4473 https://github.com/NixOS/nixpkgs/commit/934c8c7a93126090f786f9d061190cf84e7d4473 Author: Will Fancher Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/haskell-modules/default.nix Log Message: --- callCabal2nix: Fixed indentation Commit: 8c00f3432aee8cb9404f9f499148ae9158916664 https://github.com/NixOS/nixpkgs/commit/8c00f3432aee8cb9404f9f499148ae9158916664 Author: Peter Simons Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/haskell-modules/default.nix Log Message: --- Merge pull request #23982 from ElvishJerricco/callCabal2nix-dont-rebuild-cabalfile callCabal2nix: Fixed indentation Compare: https://github.com/NixOS/nixpkgs/compare/f9fb38fcae76...8c00f3432aee___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] df5a47: Merge pull request #23924 from 7c6f434c/improve-fi...
Branch: refs/heads/staging-17.03 Home: https://github.com/NixOS/nixpkgs Commit: df5a4710ff512ac062e948b54bf265ce13241fff https://github.com/NixOS/nixpkgs/commit/df5a4710ff512ac062e948b54bf265ce13241fff Author: Michael Raskin <7c6f4...@mail.ru> Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M nixos/tests/firefox.nix Log Message: --- Merge pull request #23924 from 7c6f434c/improve-firefox-test nixos: tests: firefox: make more comprehensive (cherry picked from commit f9fb38fcae7631903d23523cb987266592e35b0a) The test will block the channel without the xterm change. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 14a341: nixos: tests: firefox: make more comprehensive
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 14a3412048473e022e4bc2c687c66bb5f30c0e42 https://github.com/NixOS/nixpkgs/commit/14a3412048473e022e4bc2c687c66bb5f30c0e42 Author: Michael Raskin <7c6f4...@mail.ru> Date: 2017-03-15 (Wed, 15 Mar 2017) Changed paths: M nixos/tests/firefox.nix Log Message: --- nixos: tests: firefox: make more comprehensive Run Firefox inside an XTerm, it doesn't crash mysteriously this way. Also try opening developer tools and checking that Firefox doesn't crash in the process. Commit: f9fb38fcae7631903d23523cb987266592e35b0a https://github.com/NixOS/nixpkgs/commit/f9fb38fcae7631903d23523cb987266592e35b0a Author: Michael Raskin <7c6f4...@mail.ru> Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M nixos/tests/firefox.nix Log Message: --- Merge pull request #23924 from 7c6f434c/improve-firefox-test nixos: tests: firefox: make more comprehensive Compare: https://github.com/NixOS/nixpkgs/compare/17eaa5fe25a3...f9fb38fcae76___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 64f3d0: purePackages.octave: 0.7 -> 0.9
Branch: refs/heads/staging-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 64f3d0c1beb5f423d6636eaca47946986cebdd34 https://github.com/NixOS/nixpkgs/commit/64f3d0c1beb5f423d6636eaca47946986cebdd34 Author: Robin Gloster Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M pkgs/development/pure-modules/octave/default.nix Log Message: --- purePackages.octave: 0.7 -> 0.9 (cherry picked from commit c83665108492437527554e39963a733471c75023) Commit: 82b389fcfcd798be6fc7a7785bc584022707e59a https://github.com/NixOS/nixpkgs/commit/82b389fcfcd798be6fc7a7785bc584022707e59a Author: Robin Gloster Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M pkgs/development/compilers/ponyc/default.nix Log Message: --- ponyc: 0.10.0 -> 0.11.0 (cherry picked from commit 80bd50a6e4cbb875d936a951420abda5167cfc16) Commit: fec49efc980b4b234962685e50cf09f4c9e34c18 https://github.com/NixOS/nixpkgs/commit/fec49efc980b4b234962685e50cf09f4c9e34c18 Author: Robin Gloster Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M pkgs/development/compilers/ispc/default.nix Log Message: --- ispc: fix build (cherry picked from commit dbbdccdd658169a9f001eff01a7629a2404780ba) Commit: 2d817a37e0e1e515b911c5b4c8c8d484f609efa8 https://github.com/NixOS/nixpkgs/commit/2d817a37e0e1e515b911c5b4c8c8d484f609efa8 Author: Robin Gloster Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M pkgs/applications/science/biology/emboss/default.nix Log Message: --- emboss: fix build (cherry picked from commit e2a13af49c0a05fef1dafc0bb75ec99b8c7da6b7) Commit: b095c9998949def9d45c5b5f1d924342415d7e67 https://github.com/NixOS/nixpkgs/commit/b095c9998949def9d45c5b5f1d924342415d7e67 Author: Frederik Rietdijk Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M pkgs/development/python-modules/hypothesis.nix Log Message: --- pythonPackages.hypothesis: fix for python 3.3 (cherry picked from commit 6f90badeac9c6453033665bdeb78e28d02c8250c) Commit: 019350ac01d5ea2acf00c6552eae7425ea633280 https://github.com/NixOS/nixpkgs/commit/019350ac01d5ea2acf00c6552eae7425ea633280 Author: Frederik Rietdijk Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M pkgs/top-level/python-packages.nix Log Message: --- ipython_genutils: fix for python 3.3 and 3.4 (cherry picked from commit 891a051df18c029845415718773d3bdf16d1c7e6) Commit: eca54d99c692128e4091633a3b39ec4435e0d0b7 https://github.com/NixOS/nixpkgs/commit/eca54d99c692128e4091633a3b39ec4435e0d0b7 Author: Frederik Rietdijk Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M pkgs/top-level/python-packages.nix Log Message: --- pythonPackages.traitlets: 4.3.1 -> 4.3.2 (cherry picked from commit 8aee2b5c4fd0dfe79b801d261d440a0107e789d9) Commit: 197b247e6b13b21b3c77c3f9973003037c9dc35f https://github.com/NixOS/nixpkgs/commit/197b247e6b13b21b3c77c3f9973003037c9dc35f Author: Frederik Rietdijk Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M pkgs/development/python-modules/hypothesis.nix Log Message: --- hypothesis: 3.6.0 -> 3.6.1 (cherry picked from commit 57e768f58e7d2019ea19520226d5fb6e05e98c96) Commit: d4465f80a886b90bfaf1e0dd8560d85f92d1a90d https://github.com/NixOS/nixpkgs/commit/d4465f80a886b90bfaf1e0dd8560d85f92d1a90d Author: Tim Steinbach Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M pkgs/development/tools/continuous-integration/jenkins/default.nix Log Message: --- Merge pull request #23846 from mayflower/jenkins_2.49 jenkins: 2.44 -> 2.49(cherry picked from commit bc1f692e4956773ef13e345ebe87b5216ccbe574) Commit: 1c6cb9cb0530e4381b69fff21cdc9a6f417cf4f7 https://github.com/NixOS/nixpkgs/commit/1c6cb9cb0530e4381b69fff21cdc9a6f417cf4f7 Author: Vladimír Čunát Date: 2017-03-14 (Tue, 14 Mar 2017) Changed paths: M pkgs/development/compilers/llvm/4/clang/default.nix M pkgs/development/compilers/llvm/4/default.nix M pkgs/development/compilers/llvm/4/libc++/default.nix M pkgs/development/compilers/llvm/4/libc++abi.nix M pkgs/development/compilers/llvm/4/lld.nix M pkgs/development/compilers/llvm/4/lldb.nix M pkgs/development/compilers/llvm/4/llvm.nix M pkgs/top-level/all-packages.nix Log Message: --- Merge #23860: llvmPackages_4: rc3 -> release (cherry picked from commit bfed19cfaa4f174ee44383307d6908e50bf055bb) Commit: 591d91b3583014f3efd4a2d5796d708db7ecedac https://github.com/NixOS/nixpkgs/commit/591d91b3583014f3efd4a2d5796d708db7ecedac Author: Tim Steinbach Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M pkgs/os-specific/linux/kernel/linux-4.4.nix Log Message: --- linux: 4.4.52 -> 4.4.53 (cherry picked from commit 9ac82a773c9b4369bad77dc2dc24454c1afe
[Nix-commits] [NixOS/nixpkgs] 9b62e4: renpy: mark as broken
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 9b62e41c1e13c363b679f07f4f677cfa2e6c2acd https://github.com/NixOS/nixpkgs/commit/9b62e41c1e13c363b679f07f4f677cfa2e6c2acd Author: Linus Heckemann Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/interpreters/renpy/default.nix Log Message: --- renpy: mark as broken Commit: 17eaa5fe25a3b3020b8c3d257e26660d9f29cd0a https://github.com/NixOS/nixpkgs/commit/17eaa5fe25a3b3020b8c3d257e26660d9f29cd0a Author: Frederik Rietdijk Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/interpreters/renpy/default.nix Log Message: --- Merge pull request #23986 from lheckemann/renpy-broken renpy: mark as broken Compare: https://github.com/NixOS/nixpkgs/compare/7ff27013ac79...17eaa5fe25a3___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-dev] Props to ndowens
Hey, just wanted to thank the github user "ndowens" (whoever this is) - awesome job of package updates in the last few days! -- Mit freundlichen Grüßen, Kind regards, Matthias Beyer Consider switching to free software. It adds value to your life. https://www.gnu.org/ signature.asc Description: PGP signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 9c3c22: Python: redo setuptools bootstrapping
Branch: refs/heads/python-wip Home: https://github.com/NixOS/nixpkgs Commit: 9c3c22f5aa93dbeff97fca427abb1da8881a6216 https://github.com/NixOS/nixpkgs/commit/9c3c22f5aa93dbeff97fca427abb1da8881a6216 Author: Frederik Rietdijk Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/interpreters/python/build-python-package-setuptools.nix M pkgs/development/interpreters/python/build-python-package.nix M pkgs/development/interpreters/python/mk-python-derivation.nix M pkgs/development/python-modules/bootstrapped-pip/default.nix M pkgs/development/python-modules/setuptools/default.nix M pkgs/top-level/python-packages.nix Log Message: --- Python: redo setuptools bootstrapping Commit: 181d71483f2fbd801742944c66ec836dc46d1c1f https://github.com/NixOS/nixpkgs/commit/181d71483f2fbd801742944c66ec836dc46d1c1f Author: Frederik Rietdijk Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/python-modules/bootstrapped-pip/default.nix Log Message: --- bootstrapped-pip: remove unnecessary dependencies Commit: 87c08cb5d63a31e1c9777084abf064ad6646f6bf https://github.com/NixOS/nixpkgs/commit/87c08cb5d63a31e1c9777084abf064ad6646f6bf Author: Frederik Rietdijk Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/python-modules/setuptools/default.nix Log Message: --- pythonPackages.setuptools: pass --no-dependencies Somehow pip complaints it can't find the setuptools dependencies, but they're really there and they're working. Commit: a6d54bf1e4c81694127e2ab06903e7311958720a https://github.com/NixOS/nixpkgs/commit/a6d54bf1e4c81694127e2ab06903e7311958720a Author: Frederik Rietdijk Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/interpreters/python/build-python-package-setuptools.nix R pkgs/development/interpreters/python/run_setup.py Log Message: --- Python: use setuptools shim instead of our own Commit: 8d36e3c9e147fae323944709f5c918d71250f573 https://github.com/NixOS/nixpkgs/commit/8d36e3c9e147fae323944709f5c918d71250f573 Author: Frederik Rietdijk Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/python-modules/bootstrapped-pip/default.nix Log Message: --- Python: bootstrapped-pip rewrite Commit: 9c163cbd24e28c0470f8180dfe08fdee80b703db https://github.com/NixOS/nixpkgs/commit/9c163cbd24e28c0470f8180dfe08fdee80b703db Author: Frederik Rietdijk Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/python-modules/pycryptodome/default.nix Log Message: --- pythonPackages.pycryptodome: remove namePrefix argument Commit: 146f69a1a76c682824746794e2829c1cc6ab77ac https://github.com/NixOS/nixpkgs/commit/146f69a1a76c682824746794e2829c1cc6ab77ac Author: Frederik Rietdijk Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/python-modules/llvmlite/default.nix M pkgs/top-level/python-packages.nix Log Message: --- pythonPackages.llvmlite: 0.15.0 -> 0.16.0 Commit: 74f25ad05f6b560d8a570e32aaa23b247399879c https://github.com/NixOS/nixpkgs/commit/74f25ad05f6b560d8a570e32aaa23b247399879c Author: Frederik Rietdijk Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/python-modules/numba/default.nix Log Message: --- pythonPackages.numba: 0.30.1 -> 0.31.0 Compare: https://github.com/NixOS/nixpkgs/compare/03605ac6e83c...74f25ad05f6b___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 088a1b: pygame: 1.9.1 -> 1.9.3
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 088a1bc3110d0c0ccbd97570e851a5f4e22ab4c2 https://github.com/NixOS/nixpkgs/commit/088a1bc3110d0c0ccbd97570e851a5f4e22ab4c2 Author: Linus Heckemann Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/python-modules/pygame/default.nix Log Message: --- pygame: 1.9.1 -> 1.9.3 Commit: 7ff27013ac792082bde1675d7f8a901dfe60eb2e https://github.com/NixOS/nixpkgs/commit/7ff27013ac792082bde1675d7f8a901dfe60eb2e Author: Michael Raskin <7c6f4...@mail.ru> Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/development/python-modules/pygame/default.nix Log Message: --- Merge pull request #23981 from lheckemann/pygame pygame: 1.9.1 -> 1.9.3 Compare: https://github.com/NixOS/nixpkgs/compare/c216a7121545...7ff27013ac79___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] c216a7: terraform: use generic builder and add 0.9.0 (#239...
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: c216a7121545d3e5f2b0f904fe7c3fc736d9b212 https://github.com/NixOS/nixpkgs/commit/c216a7121545d3e5f2b0f904fe7c3fc736d9b212 Author: Peter Hoeg Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: R pkgs/applications/networking/cluster/terraform/0.8.5.nix M pkgs/applications/networking/cluster/terraform/default.nix M pkgs/top-level/all-packages.nix Log Message: --- terraform: use generic builder and add 0.9.0 (#23979) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 0c262a: kmod-blacklist-ubuntu: 9.3 -> 22.1
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 0c262a639e1f5754ebe0701b7f622e2ada26ddfa https://github.com/NixOS/nixpkgs/commit/0c262a639e1f5754ebe0701b7f622e2ada26ddfa Author: Peter Hoeg Date: 2017-03-14 (Tue, 14 Mar 2017) Changed paths: M pkgs/os-specific/linux/kmod-blacklist-ubuntu/default.nix Log Message: --- kmod-blacklist-ubuntu: 9.3 -> 22.1 Commit: 605ee9e92b83554ef2e122c3ef254e4c3428cd00 https://github.com/NixOS/nixpkgs/commit/605ee9e92b83554ef2e122c3ef254e4c3428cd00 Author: Peter Hoeg Date: 2017-03-14 (Tue, 14 Mar 2017) Changed paths: M pkgs/os-specific/linux/kmod-blacklist-ubuntu/default.nix Log Message: --- kmod-blacklist-ubuntu: do not blacklist i2c_i801 Commit: 89724f152a9ab933142f07dc9da0eafb2a7f42a6 https://github.com/NixOS/nixpkgs/commit/89724f152a9ab933142f07dc9da0eafb2a7f42a6 Author: Peter Hoeg Date: 2017-03-14 (Tue, 14 Mar 2017) Changed paths: M pkgs/os-specific/linux/kmod/default.nix Log Message: --- kmod: 23 -> 24 Commit: cb73e06989031574de19e497a4d23e2b3673daa0 https://github.com/NixOS/nixpkgs/commit/cb73e06989031574de19e497a4d23e2b3673daa0 Author: Peter Hoeg Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M pkgs/os-specific/linux/kmod-blacklist-ubuntu/default.nix M pkgs/os-specific/linux/kmod/default.nix Log Message: --- Merge pull request #23890 from peterhoeg/u/kmod kmod: 23 -> 24 and update kmod-blacklist-ubuntu to zesty Compare: https://github.com/NixOS/nixpkgs/compare/6f226a872517...cb73e0698903___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs]
Branch: refs/heads/u/tf Home: https://github.com/NixOS/nixpkgs ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 350603: terraform: use generic builder and add 0.9.0
Branch: refs/heads/u/tf Home: https://github.com/NixOS/nixpkgs Commit: 35060366c80dcd771d3efd682c431ad8991b4563 https://github.com/NixOS/nixpkgs/commit/35060366c80dcd771d3efd682c431ad8991b4563 Author: Peter Hoeg Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: R pkgs/applications/networking/cluster/terraform/0.8.5.nix M pkgs/applications/networking/cluster/terraform/default.nix M pkgs/top-level/all-packages.nix Log Message: --- terraform: use generic builder and add 0.9.0 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 1da636: terraform: use generic builder and add 0.9.0
Branch: refs/heads/u/tf Home: https://github.com/NixOS/nixpkgs Commit: 1da6367177eaa1528dff4c5798b1862874ed69f7 https://github.com/NixOS/nixpkgs/commit/1da6367177eaa1528dff4c5798b1862874ed69f7 Author: Peter Hoeg Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: R pkgs/applications/networking/cluster/terraform/0.8.5.nix M pkgs/applications/networking/cluster/terraform/default.nix M pkgs/top-level/all-packages.nix Log Message: --- terraform: use generic builder and add 0.9.0 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 389423: terraform: use generic builder and add 0.9.0
Branch: refs/heads/u/tf Home: https://github.com/NixOS/nixpkgs Commit: 389423ba809108df1b60c801bf896e27b3de02b8 https://github.com/NixOS/nixpkgs/commit/389423ba809108df1b60c801bf896e27b3de02b8 Author: Peter Hoeg Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: R pkgs/applications/networking/cluster/terraform/0.8.5.nix M pkgs/applications/networking/cluster/terraform/default.nix M pkgs/top-level/all-packages.nix Log Message: --- terraform: use generic builder and add 0.9.0 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits