[Nix-dev] Overriding python with python3 in vim_configurable.customize
Hello everyone, I am following [this](https://github.com/kamilchm/.nixpkgs/blob/master/vim-config/default.nix) template for configuring my custom vim with Nix. My `vim-config/default.nix` is as follows: { pkgs }: let my_plugins = import ./plugins.nix { inherit (pkgs) vimUtils fetchFromGitHub; }; in with (pkgs // { python = pkgs.python3; }); vim_configurable.customize { name = "vim"; vimrcConfig = { customRC = '' syntax on filetype on " ... ''; vam.knownPlugins = vimPlugins // my_plugins; vam.pluginDictionaries = [ { names = [ "ctrlp" # ... ]; } ]; }; } Although there is a `(pkgs // { python = pkgs.python3; })` override on line 5, python3 is still not used (when I run `vim --version` it shows `+python -python3`). Am I missing anything? Thanks, Ben ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Trying to compile palemoon with gcc49
Hi. I have some bug in the palemoon browser, which I already asked in the palemoon forum [1]. The compile flags can be viewed in about:buildconfig, I attached it to this mail. It apparently uses gcc 5.4.0. So I was trying to override this package in my ~/config.nix. I have the channel [2] named "unstable" for this user, and the system wide channel [3] as "nixos". My current ~/config.nix I pasted in [4]. The error message is error: attribute ‘palemoon’ missing, at /home/christoph/.nixpkgs/config.nix:33:16 which apparently means that it cannot find pkgs.palemoon. This might be due to the fact that palemoon is only in the unstable channel, not in the nixos one. So I would appreciate your help with these two questions: 1. how can I override packages from the unstable channel? 2. probably it would be a good thing to compile palemoon with gcc49 by default if it's true that there are known problems with newer gcc versions. Kind Regards, Christoph-Simon Senjak [1]:https://forum.palemoon.org/viewtopic.php?f=57=15296=1 [2]:https://nixos.org/channels/nixos-unstable [3]:https://nixos.org/channels/nixos-16.09 [4]:http://lpaste.net/3110338289819713536 Title: about:buildconfig about:buildconfig Build Machine Build platform target x86_64-unknown-linux-gnu Build tools Compiler Version Compiler flags gcc 5.4.0 -Wall -Wdeclaration-after-statement -Wempty-body -Wpointer-to-int-cast -Wsign-compare -Wtype-limits -Wno-unused -Wcast-align -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno -pthread -pipe g++ 5.4.0 -Wall -Wempty-body -Woverloaded-virtual -Wsign-compare -Wwrite-strings -Wno-invalid-offsetof -Wcast-align -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED -g -O2 -fomit-frame-pointer Configure arguments --enable-release --prefix=/nix/store/wb0f3rjvsksynyw0m0gq3i9rvfrg2pkk-palemoon-27.2.1 --enable-application=browser --enable-official-branding --enable-optimize=-O2 --enable-jemalloc --enable-shared-js --disable-tests ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Darwin + staging + libcxx
I don't think it's reproducible. I was able to build locally, and I think it's just failing repeatedly on Hydra because it's a cached failure. Of course, the missing logs means it's impossible for us to figure out what's failing on Hydra, but it seemed to be working on my machine. It'd be nice to be able to override the "cached failure" status on Hydra... On Mon, Apr 3, 2017 at 4:34 PM, Vladimír Čunátwrote: > Hi, > can someone look into why libcxx started to fail? It reproducibly fails > now on Hydra, killing almost all Darwin packages, but since I can't even > see the (final) build log, it's really hard for me to do anything about it. > > Thanks > --Vladimir > ___ > 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] 968e6d: finalterm-git: Cosmetic change
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 968e6d823b669f52b541219b53de59073ea3713a https://github.com/NixOS/nixpkgs/commit/968e6d823b669f52b541219b53de59073ea3713a Author: ndowensDate: 2017-04-02 (Sun, 02 Apr 2017) Changed paths: M pkgs/applications/misc/finalterm/default.nix Log Message: --- finalterm-git: Cosmetic change Commit: 81e1d7eb55e6c91b6094a63fbb4c81bdda4e98af https://github.com/NixOS/nixpkgs/commit/81e1d7eb55e6c91b6094a63fbb4c81bdda4e98af Author: ndowens Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/applications/misc/finalterm/default.nix Log Message: --- Merge pull request #24572 from ndowens/finalterm finalterm-git: Cosmetic change Compare: https://github.com/NixOS/nixpkgs/compare/d5a623cb39ee...81e1d7eb55e6___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-dev] NixOS Security Advisory: Docker Local Privilege Escalation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Date:2017-04-03 CVE-ID: CVE-2017-7412 Service: docker Type:local privilege escalation Summary === NixOS 17.03 before 17.03.887 has a world-writable Docker socket, which allows local users to gain privileges by executing docker commands. NixOS 16.09 is not vulnerable. Resolution == # nix-channel --update and ensure your NixOS channel is advanced to 17.03.887 or greater. Workaround == Manually apply socket permission restrictions to the Docker socket. In your configuration.nix: systemd.sockets.docker = { socketConfig.SocketMode = "0660"; socketConfig.SocketUser = "root"; socketConfig.SocketGroup = "docker"; }; Thank You = Thank you Alexey Shmalko (rasendubi on GitHub) for promptly reporting the vulnerablity and submitting a patch. References == Fix applied to 17.03: https://github.com/NixOS/nixpkgs/commit/6c59d851e2967410cc8fb6ba3f374b1d3efa988e Fix applied to unstable: https://github.com/NixOS/nixpkgs/commit/fa4fe7110566d8370983fa81f2b04a89236d 16.09 and older are not affected. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEP+htk0GpxXspt+y6BhIdNm/pQ1wFAlji5qYACgkQBhIdNm/p Q1zX7hAAr8SXo49f8eVc5k1vryUQmESaKDRkVPtk5AANyHiXhBsViUdNVlHsPvon Ciqfl/3vMcaBJGiXOYXRurZIy9i5XQuhMfTYDcA38qXqM2Sn0eyEYi38xJZGdZqf d2ajClcfHh70jqtdJpuffhc4eWoN7Y+5TrkKG7wANRBX4rXfmPtcpzESBzVhQNu6 iarJhjypr0M/9cTDG7k9E5kV2HyFlRUpSIhmNhPsM1N3DioSuCtfQcy2K3KnRRQf 1jWvt5fvq/pjLCZ4Z3JiVj6NUai46HoD99iBVXeCsEHh9DLZmidrT5lrW2RP0Cyt PQSiM/dZBeqPyRCQ7yRUcJrUjMHJQMM75T2SwCP8+UDAbNRSlJWwJy3ml5KukBcz zUJNBj1BY2/6CmGqoopuF1GkqtIuwO7gXt/U9ze8N32epXb2EVk3xzNRqjuw6YWV uBIQU68sWkKIYqw1Fi32UILBhn3CRBuK5S7I05zDgNKi15s98GGqMlIyPcPpn+YA mX3zt6Jll8b3eN8vnZezW6HZdCC3lEwlfJ9Oxenodp8/JjPa9q/PnUiRd+FBK983 OF7bJCsuM028FB21GsyqksW/YhBaTUT3mjk2ua/LJ2kw+3XauQB3Pb9mnk8/Pssr RqRyYacgAxZvtpdD/DzS9HLwwiXmNWAm/iXOrI4A1SR5zA/Xgvk= =JnIC -END PGP SIGNATURE- ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] nixops: how to deploy containers with specified IP addresses
You may be interested in https://github.com/NixOS/nixpkgs/issues/18355#issuecomment-288903363 But perhaps the easiest option would be to generate container .conf file via `environment.etc."containers/***.conf"`, if you control host. 2017-04-03 21:57 GMT+03:00 Bas van Dijk: > Dear list, > > I have a nixops deployment configuration where the machines are configured > to run in a container on localhost: > > deployment.targetEnv = "container" > > When deploying the configuration a machine gets the IP address 10.233.n.2 > where n is the order in which the machines got deployed. Since this happens > in parallel the IP addresses are nondeterministic. I see that this is > happening here: > > https://github.com/NixOS/nixpkgs/blob/master/pkgs/ > tools/virtualization/nixos-container/nixos-container.pl#L155 > > With declarative containers user can specify the address using: > > containers..localAddress > > Is there a way to override the computed IP address with a user supplied > address for imperative containers deployed using nixops? > > Cheers, > > Bas > > ___ > 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] 9626bc: Update 17.03 release notes
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 9626bc7db7690fdbd26e83403a627057a7a0a89d https://github.com/NixOS/nixpkgs/commit/9626bc7db7690fdbd26e83403a627057a7a0a89d Author: Carles PagèsDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/doc/manual/release-notes/rl-1703.xml Log Message: --- Update 17.03 release notes (cherry picked from commit d5a623cb39ee33ddb9589abe6bc640315437258f) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] d5a623: Update 17.03 release notes
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: d5a623cb39ee33ddb9589abe6bc640315437258f https://github.com/NixOS/nixpkgs/commit/d5a623cb39ee33ddb9589abe6bc640315437258f Author: Carles PagèsDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/doc/manual/release-notes/rl-1703.xml Log Message: --- Update 17.03 release notes ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-dev] Darwin + staging + libcxx
Hi, can someone look into why libcxx started to fail? It reproducibly fails now on Hydra, killing almost all Darwin packages, but since I can't even see the (final) build log, it's really hard for me to do anything about it. Thanks --Vladimir ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] paths in user's i3 configs broken by upgrade
I just upgraded from an early 17.03 beta to 17.03 and the $mod+d key combination for invoking dmenu no longer works in i3. The problem is that the paths to dmenu in the ${i3}/etc/config* files are hard coded when the config files are created and propagated to the user's .config/i3/config file by i3-config-wizard upon first logging in. At some point in the future, an upgrade causes the config file to point outside the current-system closure. This is certainly an error but won't be obvious until the path to the obsolete dmenu is garbage collected. In my case, I upgraded from 16.09 to 17.03 beta and then 17.03. Things seemed to be working so I garbage collected my original 16.09 installation which broke $mod+d as the path to the original 16.09 dmenu was now dangling. Instead of: bindsym $mod+d exec /nix/store/04sx6lx7hssid7a6iwdbdvxbkp25xsx1-dmenu-4.6/bin/dmenu_run I think it should be to be: bindsym $mod+d exec /run/current-system/sw/bin/dmenu_run That way, the path is still within the current-system closure and is guaranteed to exist if dmenu is installed. I believe the place to make the change is in the post fixup (lines 33-38 in nixpkgs/pkgs/applications/window-managers/i3/default.nix). I would be glad to issue a PR but I don't know how the substitution should change to result in /run/current-system/sw instead. Note: the path for i3status is also hard-coded and shouldn't be. Since there wasn't an update to i3status, it continues to work but is still wrong because it points outside of the current-system closure. Mark -- Mark Gardner -- ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Nix init system
Your messages to this list are non-constructive, needlessly inflammatory, and combative. Several people have pointed out that there is interest in supporting alternate init systems with Nix, and nobody is attacking you for preferring not to use systemd. Please stop trying to provoke a flamewar. On Mon, Apr 3, 2017 at 12:08 PM, lavernewrote: > On Mon, 03 Apr 2017 10:22:13 -0500 *Luescher Claude > >* wrote > > On 2017-04-03 16:20, Profpatsch wrote: > > On 17-04-03 11:14am, Luescher Claude wrote: > >> Hello, > > > > Guess what? > > > > NOBODY CARES. > > > > Keep your hate. > > Go back to the hole you came from. > > No I won't keep my hate because if everybody does nothing will happen > towards eliminating the cancer from the linux community what malware(d) > is. > > > Yet, what you are doing is WORSE than doing nothing. You are perpetuating > and enforcing the idea that all those opposed to systemd are ignorant, > whiny people who want others to do work for free. Your actions only > decrease the chance that intelligent, motivated people will want to have > anything to do with the non-systemd folks. > > I hope you all realize that this whole system(d) pottering scheme is > putting the worse NSA funded malware backdoor into linux. > > System(d) taking away the control from users, sysadmins and hackers and > giving it all to Redhat & associates. > > Your project is still just couple of months old so removing systemd > should happen now at early stages! > ___ > 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
Re: [Nix-dev] Google Summer of Code 2017
Hi Anderson, Please do! Just submit a PR and I'll give you push permissions. The more ideas we have the better. ~ On 28 March 2017 at 18:48, Anderson Torreswrote: > No problems, guys! Just keep calm and carry on! We gained another year > to rally efforts on a GSOC 2018! > > Thomas, can I add my ideas to your Github repo? > > 2017-03-15 12:33 GMT-03:00 Oliver Charles : > > On Wed, Mar 15, 2017 at 12:47 PM Domen Kožar wrote: > >> > >> We aren't participating in GSOC 2017, because I missed the submission > >> deadline. > >> > >> > >> That being said, I know people will be disappointed by this. I'm sorry, > >> I have no excuses really. I was overworked at that time and totally > forgot > >> to watch the dates. > >> > >> I already applied us two times, I hope I'll gather the energy to try > again > >> next year. > >> But since I screwed up this year, someone else can take over if wanted, > >> I understand not to be trusted :) > > > > > > As Thomas said, no hard feelings - this is not your fault! There's always > > next year :) > > > > - ocharles > ___ > 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] 75319e: nomacs: 3.4 -> 3.6.1
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 75319eb2035e7c9ec0a8f45ab816dd34689fd77a https://github.com/NixOS/nixpkgs/commit/75319eb2035e7c9ec0a8f45ab816dd34689fd77a Author: LprndnDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/applications/graphics/nomacs/default.nix Log Message: --- nomacs: 3.4 -> 3.6.1 fixes #24589 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-dev] Trying to build L4Linux kernel on NixOS: how to cross-compile?
I'm testing my luck trying to get L4Linux kernel running on NixOS. I tried to get the L4Linux kernel to build (it uses the regular kernel infrastructure) with an expression like below (full contents at: https://github.com/akavel/l4.nix/blob/9fb900a88619eb4830710e531cd3f076d74b584d/l4linux.nix ): [...] kernel = pkgs.callPackage "${nixpkgs}/pkgs/os-specific/linux/kernel/generic.nix" (rec { version = "4.7.0-l4-2016082114"; # TODO(akavel): ok or not? modDirVersion = "4.7.0-l4"; # see: nixpkgs issue #17801 and linux-mptcp.nix src = l4re; kernelPatches = []; }); in kernel But then I found out [1], that this actually builds a *vanilla* (non-L4) kernel, because of nonempty argument ARCH passed to make by /.../kernel/generic.nix. To fix this, I believe I need to use the cross-compilation infrastructure of Nix, so that generic.nix would see stdenv.cross.platform.kernelArch == "l4", and thus pass it as ARCH="l4" to make. Now, based on some rudimentary info in The Nixpkgs Manual + linked wiki, I tried changing the final line to read "kernel.crossDrv", then putting various variants of: crossSystem = { platform = { kernelArch = "l4"; }; }; in various places (including the {} just after `import `, or the {} just after pkgs.callPackage), also supplemented with more fields stolen from /.../platforms.nix's pcBase or from some random snippets found on The Internets. But whatever I tried to do, nix-build always seemed to reject my courting with a blunt: error: attribute `crossDrv' missing, at /l4linux.nix:: What should I do to make it happy? Also, as a somewhat related question: what exactly triggers appearance of a .crossDrv attribute in a derivation? (Is there some place in nixpkgs where I can find the code for that?) Thanks & Best Regards, /Mateusz. [1]: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2017/007995.html ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] nixops: how to deploy containers with specified IP addresses
Dear list, I have a nixops deployment configuration where the machines are configured to run in a container on localhost: deployment.targetEnv = "container" When deploying the configuration a machine gets the IP address 10.233.n.2 where n is the order in which the machines got deployed. Since this happens in parallel the IP addresses are nondeterministic. I see that this is happening here: https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/virtualization/nixos-container/nixos-container.pl#L155 With declarative containers user can specify the address using: containers..localAddress Is there a way to override the computed IP address with a user supplied address for imperative containers deployed using nixops? Cheers, Bas ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 1bf690: iosevka: 1.11.4 -> 1.12.1 (#24527)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 1bf690c1bb7bfc167d6ad78102a625320691e1ac https://github.com/NixOS/nixpkgs/commit/1bf690c1bb7bfc167d6ad78102a625320691e1ac Author: zimbatmDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/data/fonts/iosevka/default.nix Log Message: --- iosevka: 1.11.4 -> 1.12.1 (#24527) iosevka: 1.11.4 -> 1.12.1 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 1bc3c6: Merge #24574: ntp: security 4.2.8p9 -> 4.2.8p10
Branch: refs/heads/release-16.09 Home: https://github.com/NixOS/nixpkgs Commit: 1bc3c64849e33d6e228b4b82a203df0bf1f6c5ec https://github.com/NixOS/nixpkgs/commit/1bc3c64849e33d6e228b4b82a203df0bf1f6c5ec Author: Vladimír ČunátDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/tools/networking/ntp/default.nix Log Message: --- Merge #24574: ntp: security 4.2.8p9 -> 4.2.8p10 (cherry picked from commit 59b548069c1db00c5e37b4e9ee4027cbb125073b) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] d560fb: Merge #24574: ntp: security 4.2.8p9 -> 4.2.8p10
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: d560fbcdbc9272d3257d85b4c1fa4178020da325 https://github.com/NixOS/nixpkgs/commit/d560fbcdbc9272d3257d85b4c1fa4178020da325 Author: Vladimír ČunátDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/tools/networking/ntp/default.nix Log Message: --- Merge #24574: ntp: security 4.2.8p9 -> 4.2.8p10 (cherry picked from commit 59b548069c1db00c5e37b4e9ee4027cbb125073b) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 500818: ntp: 4.2.8p9 -> 4.2.8p10; fix 10 medium/4 low CVEs
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 500818b997fd871534ef13bdd642a899007f3fb3 https://github.com/NixOS/nixpkgs/commit/500818b997fd871534ef13bdd642a899007f3fb3 Author: Jörg ThalheimDate: 2017-04-02 (Sun, 02 Apr 2017) Changed paths: M pkgs/tools/networking/ntp/default.nix Log Message: --- ntp: 4.2.8p9 -> 4.2.8p10; fix 10 medium/4 low CVEs http://nwtime.org/network-time-foundation-publishes-ntp-4-2-8-p10/ Commit: 59b548069c1db00c5e37b4e9ee4027cbb125073b https://github.com/NixOS/nixpkgs/commit/59b548069c1db00c5e37b4e9ee4027cbb125073b Author: Vladimír Čunát Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/tools/networking/ntp/default.nix Log Message: --- Merge #24574: ntp: security 4.2.8p9 -> 4.2.8p10 Compare: https://github.com/NixOS/nixpkgs/compare/8cc3db6b6718...59b548069c1d___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] Nix init system
On Mon, 03 Apr 2017 10:22:13 -0500 Luescher Claude starg...@tango.lu wrote On 2017-04-03 16:20, Profpatsch wrote: On 17-04-03 11:14am, Luescher Claude wrote: Hello, Guess what? NOBODY CARES. Keep your hate. Go back to the hole you came from. No I won't keep my hate because if everybody does nothing will happen towards eliminating the cancer from the linux community what malware(d) is. Yet, what you are doing is WORSE than doing nothing. You are perpetuating and enforcing the idea that all those opposed to systemd are ignorant, whiny people who want others to do work for free. Your actions only decrease the chance that intelligent, motivated people will want to have anything to do with the non-systemd folks. I hope you all realize that this whole system(d) pottering scheme is putting the worse NSA funded malware backdoor into linux. System(d) taking away the control from users, sysadmins and hackers and giving it all to Redhat associates. Your project is still just couple of months old so removing systemd should happen now at early stages! ___ 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] e6faf2: create-amis.sh: Use pv-grub-hd0_1.05
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: e6faf2a4e6c9d079e9c04dc88988479a73a54b34 https://github.com/NixOS/nixpkgs/commit/e6faf2a4e6c9d079e9c04dc88988479a73a54b34 Author: Eelco DolstraDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/maintainers/scripts/ec2/create-amis.sh Log Message: --- create-amis.sh: Use pv-grub-hd0_1.05 Commit: fbe6d23624b0b62cb5754d37ab81007cd4c035ab https://github.com/NixOS/nixpkgs/commit/fbe6d23624b0b62cb5754d37ab81007cd4c035ab Author: Eelco Dolstra Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/maintainers/scripts/ec2/create-amis.sh M nixos/modules/virtualisation/amazon-options.nix Log Message: --- EC2: Disable PV support Unfortunately, somewhere between 16.09 and 17.03, paravirtualized instances stopped working. They hang at the pv-grub prompt ("grubdom>"). I tried reverting to a 4.4 kernel, reverting kernel compression from xz to bzip2 (even though pv-grub is supposed to support xz), and reverting the only change to initrd generation (5a8147479e794d5932273d01790c3602b8abeedc). Nothing worked so I'm giving up. Commit: 8cc3db6b671854b4433adf741f9b06931b7be1ce https://github.com/NixOS/nixpkgs/commit/8cc3db6b671854b4433adf741f9b06931b7be1ce Author: Eelco Dolstra Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/modules/virtualisation/ec2-amis.nix Log Message: --- Add 17.03 AMIs Compare: https://github.com/NixOS/nixpkgs/compare/c34db6e41976...8cc3db6b6718___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] Nix init system
I was almost convinced by that message but I think there was not enough f word (but almost!). I think it would be a + when you attach your scream as mp3 or something (just more interactive!) Actually, I'm little disapointed that only few kind of curses were there, I think you didn't put too much effort into that email. Not enough non-substantive arguments as well; hate is directed to dead things, make it personal! You can blame me if this will help you :-) Use all the power, memes and tweets! Use curses to encourage volontiers to do the work! That's how you do it. PS. Please send me details to your Personal Communication coach, looks like I need that as well. (please) - at the end is really sweet :-) btw, https://youtu.be/CT6Mn8UZqnY?t=3m50s - tomorrow Ulrich has presentation about immutable infrastructures on NixOS Dublin if anyone interested :-) 2017-04-03 16:24 GMT+01:00 Graham Christensen: > NixOS is 14 years old and has used systemd for about five years. > > On Mon, Apr 3, 2017 at 11:22 AM Luescher Claude wrote: > >> On 2017-04-03 16:20, Profpatsch wrote: >> > On 17-04-03 11:14am, Luescher Claude wrote: >> >> Hello, >> > >> > Guess what? >> > >> > NOBODY CARES. >> > >> > Keep your hate. >> > Go back to the hole you came from. >> >> No I won't keep my hate because if everybody does nothing will happen >> towards eliminating the cancer from the linux community what malware(d) >> is. >> >> I hope you all realize that this whole system(d) pottering scheme is >> putting the worse NSA funded malware backdoor into linux. >> >> System(d) taking away the control from users, sysadmins and hackers and >> giving it all to Redhat & associates. >> >> Your project is still just couple of months old so removing systemd >> should happen now at early stages! >> ___ >> 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 > > -- Tomasz Czyż ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] b603a9: corebird: 1.3.3 -> 1.4.2
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: b603a943e53d28496a79492124e8d5f467cae990 https://github.com/NixOS/nixpkgs/commit/b603a943e53d28496a79492124e8d5f467cae990 Author: Jens GrunertDate: 2017-03-28 (Tue, 28 Mar 2017) Changed paths: M pkgs/applications/networking/corebird/default.nix Log Message: --- corebird: 1.3.3 -> 1.4.2 Commit: 04223369e37e1c7c59737d546741dee583534b2e https://github.com/NixOS/nixpkgs/commit/04223369e37e1c7c59737d546741dee583534b2e Author: Jörg Thalheim Date: 2017-03-30 (Thu, 30 Mar 2017) Changed paths: M pkgs/desktops/gnome-3/3.22/misc/gspell/default.nix M pkgs/desktops/gnome-3/3.22/misc/gspell/src.nix Log Message: --- gspell: 1.0.3 -> 1.2.1 also enable vala bindings Commit: ca87b3a130da099b207ef1b5d5ca72e824883533 https://github.com/NixOS/nixpkgs/commit/ca87b3a130da099b207ef1b5d5ca72e824883533 Author: Jörg Thalheim Date: 2017-03-30 (Thu, 30 Mar 2017) Changed paths: M pkgs/applications/networking/corebird/default.nix Log Message: --- corebird: fix spell check Commit: c34db6e419763f97297f97e598d140bc36842eaf https://github.com/NixOS/nixpkgs/commit/c34db6e419763f97297f97e598d140bc36842eaf Author: Jörg Thalheim Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/applications/networking/corebird/default.nix M pkgs/desktops/gnome-3/3.22/misc/gspell/default.nix M pkgs/desktops/gnome-3/3.22/misc/gspell/src.nix Log Message: --- Merge pull request #24414 from jensbin/corebird corebird: 1.3.3 -> 1.4.2 Compare: https://github.com/NixOS/nixpkgs/compare/94c2f3e772cc...c34db6e41976___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 94c2f3: jp2a: 1.0.6 -> 1.0.7 (#24579)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 94c2f3e772cccdc681be720ffe95fc0483d7f9cf https://github.com/NixOS/nixpkgs/commit/94c2f3e772cccdc681be720ffe95fc0483d7f9cf Author: ndowensDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/applications/misc/jp2a/default.nix Log Message: --- jp2a: 1.0.6 -> 1.0.7 (#24579) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] ef4b73: libappindicator: propagate dependencies
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: ef4b73a0386a088ac77e1c3e0d0db2d6d770dd50 https://github.com/NixOS/nixpkgs/commit/ef4b73a0386a088ac77e1c3e0d0db2d6d770dd50 Author: Nikolay AmiantovDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/development/libraries/libappindicator/default.nix Log Message: --- libappindicator: propagate dependencies Commit: 74f7db075a89c92cf65c68a6e2bc64fd01d7da7f https://github.com/NixOS/nixpkgs/commit/74f7db075a89c92cf65c68a6e2bc64fd01d7da7f Author: Nikolay Amiantov Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/applications/networking/instant-messengers/telegram/tdesktop/default.nix M pkgs/top-level/all-packages.nix Log Message: --- tdesktop: 1.0.2 -> 1.0.27 Use system Qt. Compare: https://github.com/NixOS/nixpkgs/compare/bd0163fc3428...74f7db075a89___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] Help wanted with Nixos on ZFS in an encrypted LUKS volume
Hi Vince, NixOS does support ZFS on top of an encrypted LUKS volume (I've been using this configuration myself for years), but I'm not 100% sure it will work fine in your particular situation. The error you are seeing is because ZFS is detecting 2 (or more) ZFS pools with the same name in your system. This usually happens when you're fiddling with ZFS pool creation using different partition layouts and do not properly destroy a pool before creating another one with the same name. As specified in the error message, this can be solved by specifying the ZFS pool by its ID number instead of by name, e.g., by changing all instances of the string "zroot" in your NixOS configuration to the ID number of the pool. That said, I've never seen a NixOS configuration like this, so I'm not 100% sure it will work correctly (feel free to file a new bug if this type of configuration doesn't work). To find out the ID number of the correct ZFS pool, you will have to run (possibly in a LiveCD environment) the "zpool import" command and look at the ID number of the correct ZFS pool (where "correct" is the one that is located in your LUKS partition, and both the pool state and all its devices are in the "ONLINE" state). See below for a sample output of the "zpool import" command when 2 ZFS pools have the same name [1]. That said, the easiest way to fix your issue, and my recommendation, is for you to perform a new installation but this time create the ZFS pool only once, on top of your LUKS volume, with a new name (such as "rpool" instead of "zroot", for example). This will avoid any ambiguities as to where your ZFS pool is located. I hope this helps! [1] $ zpool import pool: test id: 18056344713568302535 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: test ONLINE /tmp/test2.tmp ONLINE pool: test id: 12658723009881072891 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: test ONLINE /tmp/test1.tmp ONLINE On Sun, Apr 2, 2017 at 9:06 PM,wrote: > Hi fellow Nix enthusiasts, > > I'm trying to install Nixos on a ZFS root filesystem which in turn resides > in an encrypted volume (using LUKS). > I already succeeded in a minimal ZFS install on an unencrypted partition, > and I also succeeded in installing in an encrypted LUKS volume with ext4 as > root fs. > But with the combination I get errors during stage 1; the zpool that > contains the root dataset cannot be imported. This occurs after I enter the > correct LUKS passphrase. > This made me question if this is at all possible (it should, shouldn't > it?). Could some of you please take a look? I documented most of it in the > gist here: https://gist.github.com/awesomefireduck/ > ffea6517042af87b8b7ef6ea1c7d50e3 . If you need more information I'd be > happy to supply it. > > Sincerely, > Vince > > ___ > 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] 7a7889: nixos/fontconfig: disable autohint by default
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 7a78892c478be77fd53a9fdec25a4dac043e9560 https://github.com/NixOS/nixpkgs/commit/7a78892c478be77fd53a9fdec25a4dac043e9560 Author: Thomas TuegelDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/modules/config/fonts/fontconfig.nix Log Message: --- nixos/fontconfig: disable autohint by default Commit: 21c9190a5fd8387c90feff08198c47894c0a541d https://github.com/NixOS/nixpkgs/commit/21c9190a5fd8387c90feff08198c47894c0a541d Author: Thomas Tuegel Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/modules/config/fonts/fontconfig.nix M nixos/modules/rename.nix Log Message: --- nixos/fontconfig: remove forceAutohint option Commit: 03942659ca1189ba50f9f1b86bbe6d925eba237b https://github.com/NixOS/nixpkgs/commit/03942659ca1189ba50f9f1b86bbe6d925eba237b Author: Thomas Tuegel Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/modules/config/fonts/fontconfig.nix M nixos/modules/rename.nix Log Message: --- nixos/fontconfig: remove renderMonoTTFAsBitmap Commit: 89bfa112cfd8a8b3da642169d33f1dfe3ea1e839 https://github.com/NixOS/nixpkgs/commit/89bfa112cfd8a8b3da642169d33f1dfe3ea1e839 Author: Thomas Tuegel Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/modules/config/fonts/fontconfig-penultimate.nix M nixos/modules/config/fonts/fontconfig.nix M pkgs/data/fonts/fontconfig-penultimate/default.nix Log Message: --- fontconfig-penultimate: 0.2.1 -> 0.3.2 Commit: bd0163fc3428e0a0373432565a997a14f558418e https://github.com/NixOS/nixpkgs/commit/bd0163fc3428e0a0373432565a997a14f558418e Author: Thomas Tuegel Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/modules/config/fonts/fontconfig-penultimate.nix M nixos/modules/config/fonts/fontconfig.nix M nixos/modules/rename.nix M pkgs/data/fonts/fontconfig-penultimate/default.nix Log Message: --- Merge branch 'fontconfig-penultimate' Compare: https://github.com/NixOS/nixpkgs/compare/b0d07aa89400...bd0163fc3428___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nix] dfcd78: Really fix the RPM build
Branch: refs/heads/master Home: https://github.com/NixOS/nix Commit: dfcd78d851c14355a09f5b8845042ade098e739a https://github.com/NixOS/nix/commit/dfcd78d851c14355a09f5b8845042ade098e739a Author: Eelco DolstraDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nix.spec.in Log Message: --- Really fix the RPM build ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] Nix init system
On Mon, 03 Apr 2017 04:27:00 -0500 Domen Kožar do...@dev.si wrote http://www.shirky.com/writings/herecomeseverybody/group_enemy.html On Mon, Apr 3, 2017, 11:14 Luescher Claude starg...@tango.lu wrote: Garbage Collected Very interesting read. Thanks for sharing! ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 6c59d8: docker: fix socket permissions
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 6c59d851e2967410cc8fb6ba3f374b1d3efa988e https://github.com/NixOS/nixpkgs/commit/6c59d851e2967410cc8fb6ba3f374b1d3efa988e Author: Alexey ShmalkoDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/modules/virtualisation/docker.nix Log Message: --- docker: fix socket permissions Docker socket is world writable. This means any user on the system is able to invoke docker command. (Which is equal to having a root access to the machine.) This commit makes socket group-writable and owned by docker group. Inspired by https://github.com/docker/docker/blob/master/contrib/init/systemd/docker.socket (cherry picked from commit fa4fe7110566d8370983fa81f2b04a89236d) Commit: 6018464c49dc60b1779f10a714974dcb4eb21c30 https://github.com/NixOS/nixpkgs/commit/6018464c49dc60b1779f10a714974dcb4eb21c30 Author: Graham Christensen Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/tests/docker.nix Log Message: --- docker: test for socket permissions (cherry picked from commit c7453084ef71e286699b7414894178e5559f5563) Compare: https://github.com/NixOS/nixpkgs/compare/6024dd4067c4...6018464c49dc___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] fa4fe7: docker: fix socket permissions
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: fa4fe7110566d8370983fa81f2b04a89236d https://github.com/NixOS/nixpkgs/commit/fa4fe7110566d8370983fa81f2b04a89236d Author: Alexey ShmalkoDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/modules/virtualisation/docker.nix Log Message: --- docker: fix socket permissions Docker socket is world writable. This means any user on the system is able to invoke docker command. (Which is equal to having a root access to the machine.) This commit makes socket group-writable and owned by docker group. Inspired by https://github.com/docker/docker/blob/master/contrib/init/systemd/docker.socket Commit: c7453084ef71e286699b7414894178e5559f5563 https://github.com/NixOS/nixpkgs/commit/c7453084ef71e286699b7414894178e5559f5563 Author: Graham Christensen Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M nixos/tests/docker.nix Log Message: --- docker: test for socket permissions Compare: https://github.com/NixOS/nixpkgs/compare/a29d0df28c30...c7453084ef71___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] a29d0d: linux: 4.11-rc4 -> 4.11-rc5
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: a29d0df28c3036e26c1806fe9172e79c0ab386ed https://github.com/NixOS/nixpkgs/commit/a29d0df28c3036e26c1806fe9172e79c0ab386ed Author: Tim SteinbachDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/os-specific/linux/kernel/linux-testing.nix Log Message: --- linux: 4.11-rc4 -> 4.11-rc5 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 6024dd: haskellPackages: Export haskellSrc2nix and hackage...
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 6024dd4067c43eda1cd3590a8ebc0e7edda1a25e https://github.com/NixOS/nixpkgs/commit/6024dd4067c43eda1cd3590a8ebc0e7edda1a25e Author: Shea LevyDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/development/haskell-modules/default.nix Log Message: --- haskellPackages: Export haskellSrc2nix and hackage2nix Allows using a different haskell package set to generate the nix expressions (during eval time) than the one used to actually build the package (at build time). (cherry picked from commit 1feca4cae3bf243c1efe11918067cec269a8bfb2) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 5cf9cb: isyncUnstable: 20161218 -> 20170329
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 5cf9cbdc1798d189e3b269f2f40d08ecc82650e8 https://github.com/NixOS/nixpkgs/commit/5cf9cbdc1798d189e3b269f2f40d08ecc82650e8 Author: Thomas TuegelDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/tools/networking/isync/unstable.nix Log Message: --- isyncUnstable: 20161218 -> 20170329 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 5f8d6a: ua: init at 2017-02-24
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 5f8d6a56a880871724790704c8c9ce8100b60526 https://github.com/NixOS/nixpkgs/commit/5f8d6a56a880871724790704c8c9ce8100b60526 Author: Thomas TuegelDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: A pkgs/tools/networking/ua/default.nix A pkgs/tools/networking/ua/deps.nix M pkgs/top-level/all-packages.nix Log Message: --- ua: init at 2017-02-24 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 1feca4: haskellPackages: Export haskellSrc2nix and hackage...
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 1feca4cae3bf243c1efe11918067cec269a8bfb2 https://github.com/NixOS/nixpkgs/commit/1feca4cae3bf243c1efe11918067cec269a8bfb2 Author: Shea LevyDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/development/haskell-modules/default.nix Log Message: --- haskellPackages: Export haskellSrc2nix and hackage2nix Allows using a different haskell package set to generate the nix expressions (during eval time) than the one used to actually build the package (at build time). Commit: 04e3cf80057eeed4a16f73aed2e9f3d570b04936 https://github.com/NixOS/nixpkgs/commit/04e3cf80057eeed4a16f73aed2e9f3d570b04936 Author: Peter Simons Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/development/haskell-modules/default.nix Log Message: --- Merge pull request #24591 from shlevy/haskell-export-2nix haskellPackages: Export haskellSrc2nix and hackage2nix Compare: https://github.com/NixOS/nixpkgs/compare/e9a636648c94...04e3cf80057e___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-dev] Help wanted with Nixos on ZFS in an encrypted LUKS volume
Hi fellow Nix enthusiasts, I'm trying to install Nixos on a ZFS root filesystem which in turn resides in an encrypted volume (using LUKS). I already succeeded in a minimal ZFS install on an unencrypted partition, and I also succeeded in installing in an encrypted LUKS volume with ext4 as root fs. But with the combination I get errors during stage 1; the zpool that contains the root dataset cannot be imported. This occurs after I enter the correct LUKS passphrase. This made me question if this is at all possible (it should, shouldn't it?). Could some of you please take a look? I documented most of it in the gist here: https://gist.github.com/awesomefireduck/ffea6517042af87b8b7ef6ea1c7d50e3 . If you need more information I'd be happy to supply it. Sincerely, Vince ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Google Summer of Code 2017
No problems, guys! Just keep calm and carry on! We gained another year to rally efforts on a GSOC 2018! Thomas, can I add my ideas to your Github repo? 2017-03-15 12:33 GMT-03:00 Oliver Charles: > On Wed, Mar 15, 2017 at 12:47 PM Domen Kožar wrote: >> >> We aren't participating in GSOC 2017, because I missed the submission >> deadline. >> >> >> That being said, I know people will be disappointed by this. I'm sorry, >> I have no excuses really. I was overworked at that time and totally forgot >> to watch the dates. >> >> I already applied us two times, I hope I'll gather the energy to try again >> next year. >> But since I screwed up this year, someone else can take over if wanted, >> I understand not to be trusted :) > > > As Thomas said, no hard feelings - this is not your fault! There's always > next year :) > > - ocharles ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Nix init system
On Mon, Apr 03, 2017 at 11:14:32AM +0200, Luescher Claude wrote: > Hello, > > After watching some videos about nix I gave it a try but as soon as I > noticed systemd I deleted the VM image right away. Either remove it or just > close the development of this whole OS. Oh but why? You don't have to use NixOS, and there's a lot of people perfectly happy with systemd. No need to close development. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 19e03a: epdfview: Fixed SRC URL; Cosmetic Change (#24568)
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 19e03a1b7e23f45b1617a17021addbc8816a3b55 https://github.com/NixOS/nixpkgs/commit/19e03a1b7e23f45b1617a17021addbc8816a3b55 Author: ndowensDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/applications/misc/epdfview/default.nix Log Message: --- epdfview: Fixed SRC URL; Cosmetic Change (#24568) (cherry picked from commit 969ed8832c9897d57d7d1678efeea04beb20d1c6) Upstream has disappeared. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] Nix init system
Hi, You might be interested in GuixSD then, their development comes from a common point but they have decided to use GNU's shepherd init system. For myself it sadly doesn't manage to reach the value i get from NixOS but it definitely is one of the best options available! And I'd be happy to be informed about any better option as I haven't seen one. Alternatively you might just be interested in that actually you are by far not the first to express some dislike for systemd, partly probably because of valid reasons. We have always expressed our appreciation of people working on a service abstraction layer and supporting other init systems, too, but for some reason the people crying out the loudest have not been that supportive in actually putting work into their cause. And although we have quite a number of contributors all of them are quite occupied with the work they are doing now and have higher priority and interest in other stuff. So long and thanks for the fish Robin PS: actually GuixSD will be looking for motivated contributors so you may be better off with just (s)trolling along ¯\_(ツ)_/¯ On 3 April 2017 11:14:32 CEST, Luescher Claudewrote: >Hello, > >After watching some videos about nix I gave it a try but as soon as I >noticed systemd I deleted the VM image right away. Either remove it or >just close the development of this whole OS. Oh but why? > >There are 100 people who have chosen to use systemd. Yet they override >everyone else because they are in the right position. > > >Fuck systemd from the bottom of my heart. >Fuck it. >Fuck it. > >FUCK SYSTEMD. > >I do not want to learn systemd. >I do not want to deal with systemd. >I hate the way it does things. >I hate the way their community works. > >I hate that it does so much. >I hate that it changes the system. >I hate what it is: system Daemon. > >I want an init that does few things. >An init that doesn't crash (not systemd!) >An init that doesn't care that I have encrypted hdd, and _never_ did >care. >An init that's small and doesn't contain >security errors (the larger the code the more there are, >and nope C is not run directly on the iron, so whatever >you think you're coding, guess again because you don't >have as much control as you think once the real code >is running on the machine) > >SystemD isn't it. >I hate the attitude of it's fuck faced devs and fans. >It's either them or us. >They make that clear. > >Fuck them, Fuck their system. Fuck SystemD >Fuck SystemD. > >We are "obsolete" and must obey their way. >Our beliefs are superceded, says them. >Fuck Systemd. > >Viva unix (please!). >Fuck Systemd. > >___ >nix-dev mailing list >nix-dev@lists.science.uu.nl >http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Sent from my Android device with K-9 Mail. Please excuse my brevity.___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 1a0a60: snapraid: 11.0 -> 11.1
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 1a0a60482bcf92d1ca87f709206904806dfa06d9 https://github.com/NixOS/nixpkgs/commit/1a0a60482bcf92d1ca87f709206904806dfa06d9 Author: makefuDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/tools/filesystems/snapraid/default.nix Log Message: --- snapraid: 11.0 -> 11.1 build from source, not the release configure scripts already generated Commit: e9a636648c94cf22b869414604d913ca06fef766 https://github.com/NixOS/nixpkgs/commit/e9a636648c94cf22b869414604d913ca06fef766 Author: Jörg Thalheim Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/tools/filesystems/snapraid/default.nix Log Message: --- Merge pull request #24587 from makefu/pkgs/snapraid/update-11.1 pkgs/snapraid/update 11.1 Compare: https://github.com/NixOS/nixpkgs/compare/969ed8832c98...e9a636648c94___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 969ed8: epdfview: Fixed SRC URL; Cosmetic Change (#24568)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 969ed8832c9897d57d7d1678efeea04beb20d1c6 https://github.com/NixOS/nixpkgs/commit/969ed8832c9897d57d7d1678efeea04beb20d1c6 Author: ndowensDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/applications/misc/epdfview/default.nix Log Message: --- epdfview: Fixed SRC URL; Cosmetic Change (#24568) epdfview: Updated Debian Mirror ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] b152bb: pam_ssh_agent_auth: Re-allow multiple authorized k...
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: b152bbd699d9379e11ccd4d40885cf84f465d127 https://github.com/NixOS/nixpkgs/commit/b152bbd699d9379e11ccd4d40885cf84f465d127 Author: Alexander KirchhoffDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/os-specific/linux/pam_ssh_agent_auth/default.nix A pkgs/os-specific/linux/pam_ssh_agent_auth/multiple-key-files.patch Log Message: --- pam_ssh_agent_auth: Re-allow multiple authorized keys files This functionality was initially introduced in 3644f9124aaf35f2ad7b17cd05df19226d4e4d1c to fix https://github.com/NixOS/nixos/pull/52, but was broken in the update from 0.9.5 to 0.10.3. The original patch does not cleanly apply due to reformatting and parameter changes upstream, but the adaptations of the patch to the new version are not too severe. (cherry picked from commit 39488911128ad5d5df0b549baf53840dedfc6d21) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] Nix init system
http://www.shirky.com/writings/herecomeseverybody/group_enemy.html On Mon, Apr 3, 2017, 11:14 Luescher Claudewrote: > Hello, > > After watching some videos about nix I gave it a try but as soon as I > noticed systemd I deleted the VM image right away. Either remove it or > just close the development of this whole OS. Oh but why? > > There are 100 people who have chosen to use systemd. Yet they override > everyone else because they are in the right position. > > > Fuck systemd from the bottom of my heart. > Fuck it. > Fuck it. > > FUCK SYSTEMD. > > I do not want to learn systemd. > I do not want to deal with systemd. > I hate the way it does things. > I hate the way their community works. > > I hate that it does so much. > I hate that it changes the system. > I hate what it is: system Daemon. > > I want an init that does few things. > An init that doesn't crash (not systemd!) > An init that doesn't care that I have encrypted hdd, and _never_ did > care. > An init that's small and doesn't contain > security errors (the larger the code the more there are, > and nope C is not run directly on the iron, so whatever > you think you're coding, guess again because you don't > have as much control as you think once the real code > is running on the machine) > > SystemD isn't it. > I hate the attitude of it's fuck faced devs and fans. > It's either them or us. > They make that clear. > > Fuck them, Fuck their system. Fuck SystemD > Fuck SystemD. > > We are "obsolete" and must obey their way. > Our beliefs are superceded, says them. > Fuck Systemd. > > Viva unix (please!). > Fuck Systemd. > > ___ > 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] 969849: mesa: maintenance 17.0.2 -> 17.0.3
Branch: refs/heads/staging Home: https://github.com/NixOS/nixpkgs Commit: 969849acf876bb4e40d6fc7f488757886fe84ea9 https://github.com/NixOS/nixpkgs/commit/969849acf876bb4e40d6fc7f488757886fe84ea9 Author: Vladimír ČunátDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/development/libraries/mesa/default.nix Log Message: --- mesa: maintenance 17.0.2 -> 17.0.3 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-dev] Nix init system
Hello, After watching some videos about nix I gave it a try but as soon as I noticed systemd I deleted the VM image right away. Either remove it or just close the development of this whole OS. Oh but why? There are 100 people who have chosen to use systemd. Yet they override everyone else because they are in the right position. Fuck systemd from the bottom of my heart. Fuck it. Fuck it. FUCK SYSTEMD. I do not want to learn systemd. I do not want to deal with systemd. I hate the way it does things. I hate the way their community works. I hate that it does so much. I hate that it changes the system. I hate what it is: system Daemon. I want an init that does few things. An init that doesn't crash (not systemd!) An init that doesn't care that I have encrypted hdd, and _never_ did care. An init that's small and doesn't contain security errors (the larger the code the more there are, and nope C is not run directly on the iron, so whatever you think you're coding, guess again because you don't have as much control as you think once the real code is running on the machine) SystemD isn't it. I hate the attitude of it's fuck faced devs and fans. It's either them or us. They make that clear. Fuck them, Fuck their system. Fuck SystemD Fuck SystemD. We are "obsolete" and must obey their way. Our beliefs are superceded, says them. Fuck Systemd. Viva unix (please!). Fuck Systemd. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] 438ac6: nomacs: init at 3.4 (#24580)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 438ac662aa598a065d2f270e78076c55f5d09aa9 https://github.com/NixOS/nixpkgs/commit/438ac662aa598a065d2f270e78076c55f5d09aa9 Author: Taahir AhmedDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M lib/maintainers.nix A pkgs/applications/graphics/nomacs/default.nix A pkgs/applications/graphics/nomacs/fix-appdata-install.patch M pkgs/top-level/all-packages.nix Log Message: --- nomacs: init at 3.4 (#24580) * nomacs: init at 3.4 * nomacs: add gsettings for gtk open dialogs * nomacs: use fetchurl instead of fetchFromGitHub ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] NixOS 17.03 'Gorilla' Released
Great work! On 31 March 2017 at 16:29, Robin Glosterwrote: > Dear community, > > I'm proud to announce the 7th NixOS stable release 17.03 named > "Gorilla". > > With over 12479 (last release: 13283) commits from 625 (last release > 554) contributors the release brings a few highlights: > > * Nixpkgs is now extensible through overlays. See the Nixpkgs manual for > more information. > > * This release is based on Glibc 2.25, GCC 5.4.0 and systemd 232. The > default Linux kernel is 4.9 and Nix is at 1.11.8. > > * The default desktop environment now is KDE's Plasma 5. KDE 4 has been > removed > > * The setuid wrapper functionality now supports setting capabilities. > > * X.org server uses branch 1.19. Due to ABI incompatibilities, > ati_unfree keeps forcing 1.17 and amdgpu-pro starts forcing 1.18. > > * Cross compilation has been rewritten. See the nixpkgs manual for > details. The most obvious breaking change is that in derivations there > is no .nativeDrv nor .crossDrv and are now cross by default, not > native. > > * The overridePackages function has been rewritten to be replaced by > overlays > > * Packages in nixpkgs can be marked as insecure through listed > vulnerabilities. See the Nixpkgs manual for more information. > > There are two open issues currently: > * gdm crashes on some hardware, using slim to start gnome works, see > the github issue for more information: >https://github.com/NixOS/nixpkgs/issues/24172 > * Firefox e10s tabs crash, see the github issue for more information: >https://github.com/NixOS/nixpkgs/issues/24295 > > See release notes for more information about major changes and updates > at http://nixos.org/nixos/manual/release-notes.html#sec-release-17.03 > > ISO and VirtualBox images can be downloaded from: > http://nixos.org/nixos/download.html > (Azure BLOBs and EC2 AMIs will follow) > > The NixOS manual is at http://nixos.org/nixos/manual/ > > A fresh installation can be done by following "Installation chapter" in > the manual: > > http://nixos.org/nixos/manual/index.html#sec-installation > > Upgrading existing NixOS installations: > > $ nix-channel --add https://nixos.org/channels/nixos-17.03 nixos > $ nixos-rebuild switch --upgrade > > Please report issues to our bug tracker: > https://github.com/NixOS/nixpkgs/issues > > The most active contributors for this release were: > 621 commits: Frederik Rietdijk > 498 commits: Franz Pletz > 379 commits: Vladimír Čunát > 377 commits: Thomas Tuegel > 324 commits: Joachim Fasting > > And of course the regular thank you to Eelco Dolstra for his tireless > work on NixOS, Nix and all the projects around that. I'd like to thank > Domen Kožar for his help on getting this release out smoothly and his > regular work on NixOS, the security team for taking a lot of workload > off the release manager by always making sure to keep our systems and > packages secure and also Mayflower for allowing me to work on NixOS a > lot in working hours. > > Also I'd like to start a discussion if we want to start rotating the > release manager for every release or maybe have two release managers > each rotating after two releases, so you always have one who has > managed one release. Any opinions? I'm not opposed to doing it again > but it needs quite some time I could also spend on other work. > > PS: Note that according to our new policy, 16.09 is still supported one > month by our security team until the end of April. > > Cheers, > Robin > ___ > 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] db6a29: kt: init at 11.1.0
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: db6a2918b9427f8f82c025e7f7aac4c5ed138f7a https://github.com/NixOS/nixpkgs/commit/db6a2918b9427f8f82c025e7f7aac4c5ed138f7a Author: Utku DemirDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M lib/maintainers.nix A pkgs/tools/misc/kt/default.nix M pkgs/top-level/all-packages.nix Log Message: --- kt: init at 11.1.0 Commit: a054f6c0769181d36145011c7bde97d3ada66fd0 https://github.com/NixOS/nixpkgs/commit/a054f6c0769181d36145011c7bde97d3ada66fd0 Author: Jörg Thalheim Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M lib/maintainers.nix A pkgs/tools/misc/kt/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Merge pull request #24585 from utdemir/master kt: init at 11.1.0 Compare: https://github.com/NixOS/nixpkgs/compare/b6036c95d069...a054f6c07691___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] b6036c: release-small: use unar instead of unrar
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: b6036c95d069e074eaa408e5f2ca2a84f49278ba https://github.com/NixOS/nixpkgs/commit/b6036c95d069e074eaa408e5f2ca2a84f49278ba Author: Vladimír ČunátDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/top-level/release-small.nix Log Message: --- release-small: use unar instead of unrar It's a free (SW) alternative. See #16868. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 11e196: Revert "steam: use custom openssl"
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 11e196d28867d52edff59ea51f9ef1b6396acdc6 https://github.com/NixOS/nixpkgs/commit/11e196d28867d52edff59ea51f9ef1b6396acdc6 Author: David McFarlandDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/games/steam/runtime-wrapped.nix Log Message: --- Revert "steam: use custom openssl" No longer necessary. See https://github.com/NixOS/nixpkgs/pull/23034#issuecomment-291005754 This reverts commit a120bad30cbd63019971e9d03edd82423131852c. (cherry picked from commit 398823da6e8a98d92086606988a78fda7bbeca5b) Commit: d1c477e0077c59cf9c1dbcb4afe2bb46a8c01385 https://github.com/NixOS/nixpkgs/commit/d1c477e0077c59cf9c1dbcb4afe2bb46a8c01385 Author: David McFarland Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/development/libraries/openssl/default.nix R pkgs/development/libraries/openssl/openssl-fix-cpuid_setup.patch M pkgs/top-level/all-packages.nix Log Message: --- Revert "openssl: add custom build of 1.0.2 for steam" No longer necessary. See https://github.com/NixOS/nixpkgs/pull/23034#issuecomment-291005754 This reverts commit a50784b34e771aa4a6c5f4eeb8c25295c15e4ed4. (cherry picked from commit 2c006ca80565a2a58fbf992f6442722baed497cc) Compare: https://github.com/NixOS/nixpkgs/compare/e840e05425d0...d1c477e0077c___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 398823: Revert "steam: use custom openssl"
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 398823da6e8a98d92086606988a78fda7bbeca5b https://github.com/NixOS/nixpkgs/commit/398823da6e8a98d92086606988a78fda7bbeca5b Author: David McFarlandDate: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/games/steam/runtime-wrapped.nix Log Message: --- Revert "steam: use custom openssl" No longer necessary. See https://github.com/NixOS/nixpkgs/pull/23034#issuecomment-291005754 This reverts commit a120bad30cbd63019971e9d03edd82423131852c. Commit: 2c006ca80565a2a58fbf992f6442722baed497cc https://github.com/NixOS/nixpkgs/commit/2c006ca80565a2a58fbf992f6442722baed497cc Author: David McFarland Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M pkgs/development/libraries/openssl/default.nix R pkgs/development/libraries/openssl/openssl-fix-cpuid_setup.patch M pkgs/top-level/all-packages.nix Log Message: --- Revert "openssl: add custom build of 1.0.2 for steam" No longer necessary. See https://github.com/NixOS/nixpkgs/pull/23034#issuecomment-291005754 This reverts commit a50784b34e771aa4a6c5f4eeb8c25295c15e4ed4. Compare: https://github.com/NixOS/nixpkgs/compare/9f34d1f19a34...2c006ca80565___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits