Re: [Nix-dev] [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

[Shea Levy]

Hey Ludo’,

Amazing, more than a decade of close working with these tools and I
never knew about C_INCLUDE_PATH et al! It looks like those will solve a
huge portion of the problem.

Will look at your gcc and clang patches as well, thank you!

~Shea

Ludovic Courtès <l...@gnu.org> writes:

> Hi Shea,
>
> Shea Levy skribis:
>
>> Unlike the traditional approach of installing system libraries into one
>> central location like /usr/{lib,include}, the nix package manager [1]
>> installs each package into it's own prefix
>> (e.g. /nix/store/mn9kqag3d24v6q41x747zd7n5qnalch7-zlib-1.2.8-dev). Moreover,
>> each package is built in its own environment determined from its
>> explicitly listed dependencies, regardless of what else is installed on
>> the system. Because not all package build scripts properly respect
>> CFLAGS etc., we currently wrap the compiler [2] to respect custom
>> environment variables like NIX_CFLAGS_COMPILE, so during the build of a
>> package that depends on zlib and Xlib might have NIX_CFLAGS_COMPILE set
>> to "-isystem 
>> /nix/store/bl0rz2xinsm9yslghd7n5vaba86zxknh-libX11-1.6.3-dev/include 
>> -isystem /nix/store/mn9kqag3d24v6q41x747zd7n5qnalch7-zlib-1.2.8-dev/include".
>>
>> Unfortunately, as you can see if you click through the link or look
>> through the git history, the wrapper is quite complex (frankly, hacky)
>
>> [2]: 
>> https://github.com/NixOS/nixpkgs/blob/8cbdd9d0c290e294a9d783c8868e738db05c9ce2/pkgs/build-support/cc-wrapper/cc-wrapper.sh
>
> Guix avoids the compiler wrapper altogether like this:
>
>   • We use C_INCLUDE_PATH, LIBRARY_PATH, and friends:
> 
> <http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/gcc.scm#n296>.
>
>   • We have a simple linker wrapper aimed at adding -Wl,-rpath flags:
> 
> <http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/ld-wrapper.in#n42>.
> The comment in that file explains why the other options considered
> were unsuitable.
>
>   • We modify the built-in “lib” spec of GCC to add the necessary -L and
> -rpath flags:
> 
> <http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/gcc.scm#n218>.
>
>   • Likewise, we tell Clang where to find libc and friends:
> 
> <http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/patches/clang-libc-search-path.patch>
> 
> <http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/llvm.scm#n161>.
>
> This is not too intrusive and more robust than wrapping everything.
>
> I suppose GCC and Clang could facilitate this by providing configure
> options to augment the “lib” spec, specify the location of libc alone,
> or something along these lines.
>
> Thoughts?
>
> Ludo’.


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Proposal: Highly available security-specific trusted build infrastructure

[Shea Levy]

I think an automated system would be nicer, but yes this would resolve
the majority of my concern here.

Kevin Cox <kevin...@kevincox.ca> writes:

> [ Unknown signature status ]
> On 16/10/16 18:24, Shea Levy wrote:
>> The existing infrastructure will always have more load and be more
>> complex than what is needed for security updates. hydra is a fully
>> general CI system, and properly so, but it means the system is subject
>> to bugs and constraints that a simpler more focused system can avoid.
>> 
>> Moreover, for better or for worse hydra.nixos.org is only manageable by
>> a small set of people who are not always available to service it (nor
>> should they have to be!). No amount of improving hydra will fix that.
>> 
>
> I see your point. But for a emergency rebuild system for security fixes
> wouldn't it just make sense to have a couple of people with S3
> credentials? Most packages can be built on a mildly powerful machine in
> an hour. In the rare case that the package would take longer it probably
> wouldn't be improved by a cluster as it will be a serial dependency chain.
>
> So if we really want to reduce dependencies how about a couple of people
> trusted to push these updated packages?


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Proposal: Highly available security-specific trusted build infrastructure

[Shea Levy]

The existing infrastructure will always have more load and be more
complex than what is needed for security updates. hydra is a fully
general CI system, and properly so, but it means the system is subject
to bugs and constraints that a simpler more focused system can avoid.

Moreover, for better or for worse hydra.nixos.org is only manageable by
a small set of people who are not always available to service it (nor
should they have to be!). No amount of improving hydra will fix that.

~Shea

Graham Christensen <gra...@grahamc.com> writes:

>  -1 I think a better approach would be to bolster and support the existing
> infrastructure and fix its issues, not create a whole new set. Hydra
> already spins up and down AWS nodes depending on the number of jobs.
>
>  - https://github.com/NixOS/hydra-provisioner
>  -
> https://github.com/NixOS/nixos-org-configurations/tree/master/hydra-provisioner
>  - https://hydra.nixos.org/machines -- I believe if you whois the
> struck-out IPs they'll all belong to AWS
>
> On Sun, Oct 16, 2016 at 12:56 PM Shea Levy <s...@shealevy.com> wrote:
>
>> Hi all,
>>
>> hydra.nixos.org is a wonderful community resource, but its broad scope
>> and somewhat frequent downtime concerns me when it comes to security
>> updates. As a supplemental service, I propose we have a service, hosted
>> by a professional hosting company with 24/7 support and with multiple
>> trusted community members having administrative access, dedicated to
>> building only critical security updates and uploading them to the binary
>> cache, with the intention that these be used with
>> system.replaceRuntimeDependencies/pkgs.replaceDependency until hydra has
>> had a chance to update the entire channel. This service could work via
>> manual triggering by trusted users, github push notifications and commit
>> message parsing (to get the relevant attributes to build), signed git
>> commits, or some combination of these, and would *only* build the
>> directly affected packages (e.g. only rebuild glibc for a glibc
>> vulnerability, expecting users to use replaceDependency until hydra is
>> caught up). If it turns out to be useful, it could spin up AWS build
>> machines on demand to ensure a very rapid turnaround.
>>
>> Thoughts on this? I'm happy to help fund this significantly, but it
>> loses a lot of its value if it doesn't directly upload to the nixos.org
>> cache so I think it needs official support before following through.
>>
>> Thanks,
>> Shea
>> ___
>> 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] Proposal: Highly available security-specific trusted build infrastructure

[Shea Levy]

Hi all,

hydra.nixos.org is a wonderful community resource, but its broad scope
and somewhat frequent downtime concerns me when it comes to security
updates. As a supplemental service, I propose we have a service, hosted
by a professional hosting company with 24/7 support and with multiple
trusted community members having administrative access, dedicated to
building only critical security updates and uploading them to the binary
cache, with the intention that these be used with
system.replaceRuntimeDependencies/pkgs.replaceDependency until hydra has
had a chance to update the entire channel. This service could work via
manual triggering by trusted users, github push notifications and commit
message parsing (to get the relevant attributes to build), signed git
commits, or some combination of these, and would *only* build the
directly affected packages (e.g. only rebuild glibc for a glibc
vulnerability, expecting users to use replaceDependency until hydra is
caught up). If it turns out to be useful, it could spin up AWS build
machines on demand to ensure a very rapid turnaround.

Thoughts on this? I'm happy to help fund this significantly, but it
loses a lot of its value if it doesn't directly upload to the nixos.org
cache so I think it needs official support before following through.

Thanks,
Shea


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] [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

[Shea Levy]

Hello GCC and Clang devs!

Unlike the traditional approach of installing system libraries into one
central location like /usr/{lib,include}, the nix package manager [1]
installs each package into it's own prefix
(e.g. /nix/store/mn9kqag3d24v6q41x747zd7n5qnalch7-zlib-1.2.8-dev). Moreover,
each package is built in its own environment determined from its
explicitly listed dependencies, regardless of what else is installed on
the system. Because not all package build scripts properly respect
CFLAGS etc., we currently wrap the compiler [2] to respect custom
environment variables like NIX_CFLAGS_COMPILE, so during the build of a
package that depends on zlib and Xlib might have NIX_CFLAGS_COMPILE set
to "-isystem 
/nix/store/bl0rz2xinsm9yslghd7n5vaba86zxknh-libX11-1.6.3-dev/include -isystem 
/nix/store/mn9kqag3d24v6q41x747zd7n5qnalch7-zlib-1.2.8-dev/include".

Unfortunately, as you can see if you click through the link or look
through the git history, the wrapper is quite complex (frankly, hacky)
and has evolved mostly through trial and error. Moreover, it's known to
break things like response files [3] and is generally speaking a source
of frustration. I believe the situation would be much improved if gcc
and clang supported some form of "environment-specific" configuration,
either through environment variables or, if absolutely necessary,
command line flags that can be passed unconditionally (note, for
example, that we currently parse the cc command line to see if we're
going to do any linking before deciding to pass in linking-specific
options) and clearly have the semantics we want. Ideally we would be
able to specify something on the level of abstraction of "this directory
should be treated like you would normally treat /usr" and get
e.g. /include, /lib, frameworks on OS X, etc. handled properly.

Would patches aimed at achieving this be considered for inclusion
upstream? My current thought for a first step would be an environment
variable specifying a file with command line flags that are ignored by
the compiler driver in contexts where they are inapplicable or
overridden by other command line flags, but I'm definitely open to
guidance on how this should best be achieved from your perspective. I'm
happy to do the work needed to get this in place if there is interest,
please let me know!

Thanks,
Shea Levy

[1]: https://nixos.org/nix
[2]: 
https://github.com/NixOS/nixpkgs/blob/8cbdd9d0c290e294a9d783c8868e738db05c9ce2/pkgs/build-support/cc-wrapper/cc-wrapper.sh
[3]: 
https://github.com/NixOS/nixpkgs/commit/a421e7bd4a28c69bded8b17888325e31554f61a1


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] bcb236: uri: init at 2016-09-04

[Shea Levy]

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: bcb23619ef70902a466c1f2f76dcc756188351e1
  
https://github.com/NixOS/nixpkgs/commit/bcb23619ef70902a466c1f2f76dcc756188351e1
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-10 (Mon, 10 Oct 2016)

  Changed paths:
A pkgs/development/libraries/uri/default.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  uri: init at 2016-09-04

(cherry picked from commit ecb596b898bcf3992ab3b90fa0b301153801f810)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] ecb596: uri: init at 2016-09-04

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: ecb596b898bcf3992ab3b90fa0b301153801f810
  
https://github.com/NixOS/nixpkgs/commit/ecb596b898bcf3992ab3b90fa0b301153801f810
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-10 (Mon, 10 Oct 2016)

  Changed paths:
A pkgs/development/libraries/uri/default.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  uri: init at 2016-09-04


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] e7634e: melpa: Fix nix-buffer and inherit-local, add stabl...

[Shea Levy]

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: e7634ecdc51587f407869a9e225618a6b7fdea79
  
https://github.com/NixOS/nixpkgs/commit/e7634ecdc51587f407869a9e225618a6b7fdea79
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-07 (Fri, 07 Oct 2016)

  Changed paths:
M pkgs/applications/editors/emacs-modes/melpa-stable-generated.nix

  Log Message:
  ---
  melpa: Fix nix-buffer and inherit-local, add stable

Only cherry-picked the stable additions

(cherry picked from commit 38f074435a3a4a92ca0950e33cea1554f364fe70)


  Commit: 2c3b10ea650170627aad939432b13e3bf2841da7
  
https://github.com/NixOS/nixpkgs/commit/2c3b10ea650170627aad939432b13e3bf2841da7
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-07 (Fri, 07 Oct 2016)

  Changed paths:
M pkgs/applications/science/logic/coq/default.nix
M pkgs/build-support/cc-wrapper/default.nix
M pkgs/build-support/emacs/buffer.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  nix-buffer support improvements.

Use inherit-local, add per-package elisp hooks.

(cherry picked from commit eca0f17ad20e9604a60efa57c7fa717ee2c8f1b7)


Compare: https://github.com/NixOS/nixpkgs/compare/51ca699309df...2c3b10ea6501___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] eca0f1: nix-buffer support improvements.

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: eca0f17ad20e9604a60efa57c7fa717ee2c8f1b7
  
https://github.com/NixOS/nixpkgs/commit/eca0f17ad20e9604a60efa57c7fa717ee2c8f1b7
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-07 (Fri, 07 Oct 2016)

  Changed paths:
M pkgs/applications/science/logic/coq/default.nix
M pkgs/build-support/cc-wrapper/default.nix
M pkgs/build-support/emacs/buffer.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  nix-buffer support improvements.

Use inherit-local, add per-package elisp hooks.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 874411: cpp-netlib: propagate asio.

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 874411c0e31bcd86afdd9657882cab5dcd6f36ea
  
https://github.com/NixOS/nixpkgs/commit/874411c0e31bcd86afdd9657882cab5dcd6f36ea
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-06 (Thu, 06 Oct 2016)

  Changed paths:
M pkgs/development/libraries/cpp-netlib/default.nix

  Log Message:
  ---
  cpp-netlib: propagate asio.

See cpp-netlib/cpp-netlib#629


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] e54313: Revert "Revert "Linux 4.8""

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: e54313d183ff04d722241ad137367d9fd1f6af4c
  
https://github.com/NixOS/nixpkgs/commit/e54313d183ff04d722241ad137367d9fd1f6af4c
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-04 (Tue, 04 Oct 2016)

  Changed paths:
A pkgs/os-specific/linux/kernel/linux-4.8.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Revert "Revert "Linux 4.8""

Now featuring @aszlig's modinst_arg_list_too_long patch.

This reverts commit 43bedb970d7518794f8e82ce23952c06083f.

Fixes #19213


  Commit: e70a2badc2f956ecfb975484e2dc3037a2e24573
  
https://github.com/NixOS/nixpkgs/commit/e70a2badc2f956ecfb975484e2dc3037a2e24573
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-04 (Tue, 04 Oct 2016)

  Changed paths:
M pkgs/applications/editors/emacs-modes/elpa-generated.nix
M pkgs/applications/editors/emacs-modes/melpa-generated.nix
M pkgs/applications/editors/emacs-modes/melpa-stable-generated.nix
M pkgs/applications/editors/emacs-modes/org-generated.nix

  Log Message:
  ---
  Merge branch 'master' of github.com:NixOS/nixpkgs


Compare: https://github.com/NixOS/nixpkgs/compare/772d7262a171...e70a2badc2f9___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] d26075: Revert "Revert "Linux 4.8""

[Shea Levy]

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: d260758a1e72d727ce8fde12bdcb8a8698086b7b
  
https://github.com/NixOS/nixpkgs/commit/d260758a1e72d727ce8fde12bdcb8a8698086b7b
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-04 (Tue, 04 Oct 2016)

  Changed paths:
A pkgs/os-specific/linux/kernel/linux-4.8.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Revert "Revert "Linux 4.8""

Now featuring @aszlig's modinst_arg_list_too_long patch.

This reverts commit 43bedb970d7518794f8e82ce23952c06083f.

Fixes #19213

(cherry picked from commit e54313d183ff04d722241ad137367d9fd1f6af4c)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] bb961e: Revert "Linux 4.8"

[Shea Levy]

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: bb961e1f9df365b2aa84518f164e316a310533ef
  
https://github.com/NixOS/nixpkgs/commit/bb961e1f9df365b2aa84518f164e316a310533ef
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-03 (Mon, 03 Oct 2016)

  Changed paths:
R pkgs/os-specific/linux/kernel/linux-4.8.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Revert "Linux 4.8"

This reverts commit e4958d54b13909281ee01ef241abab5d955f6f75.

(cherry picked from commit 43bedb970d7518794f8e82ce23952c06083f)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 43bedb: Revert "Linux 4.8"

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 43bedb970d7518794f8e82ce23952c06083f
  
https://github.com/NixOS/nixpkgs/commit/43bedb970d7518794f8e82ce23952c06083f
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-03 (Mon, 03 Oct 2016)

  Changed paths:
R pkgs/os-specific/linux/kernel/linux-4.8.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Revert "Linux 4.8"

This reverts commit e4958d54b13909281ee01ef241abab5d955f6f75.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] d8d270: Linux 4.8

[Shea Levy]

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: d8d270d6cc9d93c0a65c95020e3c702ac6d1f767
  
https://github.com/NixOS/nixpkgs/commit/d8d270d6cc9d93c0a65c95020e3c702ac6d1f767
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-03 (Mon, 03 Oct 2016)

  Changed paths:
A pkgs/os-specific/linux/kernel/linux-4.8.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Linux 4.8

(cherry picked from commit e4958d54b13909281ee01ef241abab5d955f6f75)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] e4958d: Linux 4.8

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: e4958d54b13909281ee01ef241abab5d955f6f75
  
https://github.com/NixOS/nixpkgs/commit/e4958d54b13909281ee01ef241abab5d955f6f75
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-10-03 (Mon, 03 Oct 2016)

  Changed paths:
A pkgs/os-specific/linux/kernel/linux-4.8.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Linux 4.8


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] NixOS Contract Opportunity

[Shea Levy]

Hi Phillip,

I would be interested in this. I can forward on my standard contract,
but before I do so is my usual rate of $100/hr acceptable?

For reference, I am shlevy on github and have been contributing
regularly to nix and nixpkgs/NixOS for 6 years now, including several
previous contracts in this vein.

Thanks,
Shea

Phillip Zedalis  writes:

> [ Unknown signature status ]
> Hello all,
>
>  
>
> I am seeking a NixOS expert/developer/user who is familiar with creating 
> custom NixOS packages. I have posted this opportunity on Upwork at: 
> https://www.upwork.com/jobs/~01e73d0091cb4e3749 
>
>  
>
> Please contact me if this would interest you. We can work through Upwork or 
> B2B (your preference). Thanks in advance for your consideration.
>
>  
>
> Thanks,
>
> Phillip Zedalis
>
> Chief Warp Engineer
>
> http://www.serverwarp.com 
>
> 1-844-687-WARP
>
>  
>
> ___
> 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-commits] [NixOS/nixpkgs] e5bd75: supplicant: Make the device pull in the supplicant...

[Shea Levy]

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: e5bd75f3e6b814157a1100c7a35bfd300d806344
  
https://github.com/NixOS/nixpkgs/commit/e5bd75f3e6b814157a1100c7a35bfd300d806344
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-30 (Fri, 30 Sep 2016)

  Changed paths:
M nixos/modules/services/networking/supplicant.nix

  Log Message:
  ---
  supplicant: Make the device pull in the supplicant service.

The udev rule should do this. Not sure why it doesn't.

Fixes #19029.

(cherry picked from commit b692e06686fc3550f8076070780c10140e14eb0c)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] b692e0: supplicant: Make the device pull in the supplicant...

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: b692e06686fc3550f8076070780c10140e14eb0c
  
https://github.com/NixOS/nixpkgs/commit/b692e06686fc3550f8076070780c10140e14eb0c
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-30 (Fri, 30 Sep 2016)

  Changed paths:
M nixos/modules/services/networking/supplicant.nix

  Log Message:
  ---
  supplicant: Make the device pull in the supplicant service.

The udev rule should do this. Not sure why it doesn't.

Fixes #19029.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Can vim 8.0 be included in 16.09

[Shea Levy]

See [1], though I should have wrapped the callPackage call in lowPrio
(See e.g. [2] for an example of using lowPrio).

[1]: 
https://github.com/NixOS/nixpkgs/commit/01f571148583bcc85fad1963536a788d828befbf
[2]: 
https://github.com/NixOS/nixpkgs/blob/01f571148583bcc85fad1963536a788d828befbf/pkgs/top-level/all-packages.nix#L1615

Wink Saville <w...@saville.com> writes:

> If you can point to me an example I'll prepare a pull request.
>
> On Thu, Sep 29, 2016, 5:43 AM Shea Levy <s...@shealevy.com> wrote:
>
>> We could bring vim 8 to 16.09, as long as it had a separate attribute
>> and were set lo-prio so only people who explicitly asked for it would
>> get it.
>>
>> Domen Kožar <do...@dev.si> writes:
>>
>> > After the branch off (beta release) we only port minor updates and
>> security
>> > upgrades. It's a day until the release so we can't do a major vim upgrade
>> > since we risk there are issues and it's an important part of the
>> ecosystem.
>> >
>> > On Thu, Sep 29, 2016 at 5:33 AM, Wink Saville <w...@saville.com> wrote:
>> >
>> >> What is the criteria for inclusion in 16.09, any possibility we could
>> >> include 16.09?
>> >>
>> >> -- Wink
>> >>
>> >> ___
>> >> 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
>>


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Can vim 8.0 be included in 16.09

[Shea Levy]

We could bring vim 8 to 16.09, as long as it had a separate attribute
and were set lo-prio so only people who explicitly asked for it would
get it.

Domen Kožar  writes:

> After the branch off (beta release) we only port minor updates and security
> upgrades. It's a day until the release so we can't do a major vim upgrade
> since we risk there are issues and it's an important part of the ecosystem.
>
> On Thu, Sep 29, 2016 at 5:33 AM, Wink Saville  wrote:
>
>> What is the criteria for inclusion in 16.09, any possibility we could
>> include 16.09?
>>
>> -- Wink
>>
>> ___
>> 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


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] e7b3d9: wl-pprint: update to 2016-09-28

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: e7b3d9c7c899401ddfc9da2752304084bfdc8675
  
https://github.com/NixOS/nixpkgs/commit/e7b3d9c7c899401ddfc9da2752304084bfdc8675
  Author: Langston Barrett <langston.barr...@gmail.com>
  Date:   2016-09-28 (Wed, 28 Sep 2016)

  Changed paths:
M pkgs/development/idris-modules/wl-pprint.nix

  Log Message:
  ---
  wl-pprint: update to 2016-09-28


  Commit: 299ef14cb117f6bf79be83fc0471ec2e0409c1e1
  
https://github.com/NixOS/nixpkgs/commit/299ef14cb117f6bf79be83fc0471ec2e0409c1e1
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-28 (Wed, 28 Sep 2016)

  Changed paths:
M pkgs/development/idris-modules/wl-pprint.nix

  Log Message:
  ---
  Merge branch 'wl-pprint/4cc88a' of git://github.com/siddharthist/nixpkgs


Compare: https://github.com/NixOS/nixpkgs/compare/58ce50fedfa0...299ef14cb117___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] NixOS 16.09 not cleaning /boot/EFI/nixos

[Shea Levy]

Right, this is why I recommended directly calling
/run/current-system/bin/switch-to-configuration. If the configuration is
already present in /boot, you can be sure it doesn't need to add
anything.

Roger Qiu <roger@matrix.ai> writes:

> I discovered a while back that NixOS rebuild is only time boot efi gets
> cleaned. But here's a question. Does it delete then add the new efi, or
> does it add the new efi then delete? The former would mean that even if
> your efi is full, it will work, but raises the possibility that if a
> rebuild gets interrupted, then you will have no efi. The latter is what I
> think it currently does. So I think if your efi is full, you won't be able
> to do a nixos rebuild.
> On 28/09/2016 5:49 PM, "Damien Cassou" <dam...@cassou.me> wrote:
>
>> Shea Levy <s...@shealevy.com> writes:
>>
>> > After deleting the old profiles (which nix-collect-garbage -d does), did
>> > you run '/run/current-system/bin/switch-to-configuration boot'? I think
>> > that or doing a nixos-rebuild is the only way to trigger the /boot
>> > garbage collection.
>>
>> you saved me, thank you very much.
>>
>> --
>> Damien Cassou
>> http://damiencassou.seasidehosting.st
>>
>> "Success is the ability to go from one failure to another without
>> losing enthusiasm." --Winston Churchill
>> ___
>> 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

Re: [Nix-dev] NixOS 16.09 not cleaning /boot/EFI/nixos

[Shea Levy]

Hi Damien,

After deleting the old profiles (which nix-collect-garbage -d does), did
you run '/run/current-system/bin/switch-to-configuration boot'? I think
that or doing a nixos-rebuild is the only way to trigger the /boot
garbage collection.

~Shea

Damien Cassou  writes:

> Hi,
>
> this morning I got notified that there is no space left on /boot:
>
> $ df -h /boot
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/nvme0n1p1  256M  249M  7.9M  97% /boot
>
> When I look at it, I can see many nixos efi files:
>
>  $ du -sh /boot/EFI/nixos/*
> 3.9M
> /boot/EFI/nixos/0k505mxyzj50dljm8bhvnrjzz8rlyjx6-linux-4.6.7-bzImage.efi
> 4.2M
> /boot/EFI/nixos/7zqdzaqm5racflik1bljqrym4whincb7-linux-4.7-bzImage.efi
> 4.2M
> /boot/EFI/nixos/kyzvb5xaws0kw5i0gnjc5mjjzmy4xm4a-linux-4.7.2-bzImage.efi
> 4.2M
> /boot/EFI/nixos/ns9hlp2s6yv0iqg2nd1hsz9mn77b66d8-linux-4.7-bzImage.efi
> 4.2M
> /boot/EFI/nixos/vyw884qnkqh1xrpw2qcfyl71cy8a7p5n-linux-4.7-bzImage.efi
> 4.2M
> /boot/EFI/nixos/zd7vsh4iad8i3vf8xzify973vydviva4-linux-4.7.2-bzImage.efi
> 4.3M
> /boot/EFI/nixos/l4n4b8igv88s5g0xr48f6n5gir7bgyqq-linux-4.6.7-bzImage.efi
> 4.3M
> /boot/EFI/nixos/rkmxvm29xp51r7672lnd8pbvwhhlxhrx-linux-4.6.7-bzImage.efi
> 4.3M
> /boot/EFI/nixos/rny17ngh4cf8zrplx281v51rgzqhnv35-linux-4.6.7-bzImage.efi
> 4.4M
> /boot/EFI/nixos/0sww42pc5d01dv74mw6g5fn4wbdznz5y-linux-4.7.2-bzImage.efi
> 4.4M
> /boot/EFI/nixos/ajc33qx6vzf5yv698rvpgw8p75vliri3-linux-4.7.5-bzImage.efi
> 4.4M
> /boot/EFI/nixos/d0w54174d3vg6pvjb3s3877z2ri8saah-linux-4.7.4-bzImage.efi
> 4.4M
> /boot/EFI/nixos/sfy167wbwvhb29vpbdk0v5sxznr245d3-linux-4.7.4-bzImage.efi
> 7.1M
> /boot/EFI/nixos/3bsdwvdmzxaddw3ydqx40fry0b2gj406-initrd-initrd.efi
> 7.1M
> /boot/EFI/nixos/3gwpx18ryhkcs4m7hdhp5c5w00mx3x4l-initrd-initrd.efi
> [... 22 more of these last 2...]
> 226M/boot/EFI/nixos
>
> I just did a "nix-collect-garbage --delete-older-than 2d" but that
> doesn't remove files in /boot/EFI/nixos. Moreover, systemd-boot still
> shows me many entries, starting at number 83, but these entries are not
> in /nix/var/nix/profiles anymore:
>
> $ ls /nix/var/nix/profiles/
> per-container  per-user  system  system-153-link  system-154-link
> system-155-link  system-156-link
>
> So, I'm lost. Can you please tell me how to make room on this partition?
>
> Thank you very much.
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Success is the ability to go from one failure to another without
> losing enthusiasm." --Winston Churchill
> ___
> 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-commits] [NixOS/nixpkgs] 7bda74: idris-modules: pkgs.gnome is now pkgs.gnome2.

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 7bda74f676ac4e48c39cd1fb8233106f39bcbca2
  
https://github.com/NixOS/nixpkgs/commit/7bda74f676ac4e48c39cd1fb8233106f39bcbca2
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-27 (Tue, 27 Sep 2016)

  Changed paths:
M pkgs/development/idris-modules/default.nix

  Log Message:
  ---
  idris-modules: pkgs.gnome is now pkgs.gnome2.

Fixes #18998.

Closes #19002.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 82ba4d: Sphinx: 1.3.6 -> 1.4.6

[Shea Levy]

NixOS/nixpkgs/commit/33da338bde291c664eb124ad8948a311c81ed221
  Author: Eelco Dolstra <eelco.dols...@logicblox.com>
  Date:   2016-09-19 (Mon, 19 Sep 2016)

  Changed paths:
M pkgs/servers/sql/mariadb/default.nix

  Log Message:
  ---
  mariadb: Don't install mysqlbug

This causes a dependency on gcc.


  Commit: 3a534e8609ebf8e683d3e896380a90c3e222b942
  
https://github.com/NixOS/nixpkgs/commit/3a534e8609ebf8e683d3e896380a90c3e222b942
  Author: Stefan Goetz <goet...@hotmail.de>
  Date:   2016-09-19 (Mon, 19 Sep 2016)

  Changed paths:
M pkgs/tools/misc/youtube-dl/default.nix

  Log Message:
  ---
  youtube-dl: 2016.07.16 -> 2016.09.19 (#18723)

* youtube-dl: 2016.07.16 -> 2016.09.18

* youtube-dl: 2016.09.18 -> 2016.09.19


  Commit: 2f8913c7a59abd1a35316c318bbf34ad159524a8
  
https://github.com/NixOS/nixpkgs/commit/2f8913c7a59abd1a35316c318bbf34ad159524a8
  Author: Alexander Ried <r...@mytum.de>
  Date:   2016-09-19 (Mon, 19 Sep 2016)

  Changed paths:
R pkgs/servers/sql/monetdb/default.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  monetdb: remove pkg

This used a source from 2009 and has been removed from all-packages.nix
4 years ago in 8020c37f55c3a2a6236ca46cec963f8928f77192


  Commit: e52418fd080e2bc8a919af61aa94ed2c4e9b80d0
  
https://github.com/NixOS/nixpkgs/commit/e52418fd080e2bc8a919af61aa94ed2c4e9b80d0
  Author: Alexander Ried <r...@mytum.de>
  Date:   2016-09-19 (Mon, 19 Sep 2016)

  Changed paths:
M nixos/modules/misc/ids.nix
M nixos/modules/module-list.nix
R nixos/modules/services/databases/monetdb.nix

  Log Message:
  ---
  monetdb module: remove since it's not packaged


  Commit: e453c62885324cc84f41e73ce8dec551cc21094d
  
https://github.com/NixOS/nixpkgs/commit/e453c62885324cc84f41e73ce8dec551cc21094d
  Author: Domen Kožar <do...@dev.si>
  Date:   2016-09-19 (Mon, 19 Sep 2016)

  Changed paths:
M nixos/modules/misc/ids.nix
M nixos/modules/module-list.nix
R nixos/modules/services/databases/monetdb.nix
R pkgs/servers/sql/monetdb/default.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Merge pull request #18769 from groxxda/monetdb

monetdb: remove because it's package is dead since 4 years (8020c37)


  Commit: 3f02cbbcaf18626e1f6a1824cfce142ad48ec614
  
https://github.com/NixOS/nixpkgs/commit/3f02cbbcaf18626e1f6a1824cfce142ad48ec614
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-19 (Mon, 19 Sep 2016)

  Changed paths:
M nixos/modules/security/rngd.nix

  Log Message:
  ---
  Merge branch 'rngd-wantedBy' of git://github.com/srp/nixpkgs-1


Compare: https://github.com/NixOS/nixpkgs/compare/cc22b5f2adc8...3f02cbbcaf18___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] a56022: rngd: update modalias to match cpu type

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: a560223119a7d434ad09b26246bd485f893036e1
  
https://github.com/NixOS/nixpkgs/commit/a560223119a7d434ad09b26246bd485f893036e1
  Author: Scott R. Parish <srpar...@gmail.com>
  Date:   2016-09-17 (Sat, 17 Sep 2016)

  Changed paths:
M nixos/modules/security/rngd.nix

  Log Message:
  ---
  rngd: update modalias to match cpu type

It looks like the cpu type part of modalias might have changed, my
systems (4.4.20 and 4.7.2) show something like the following:

```
cpu:type:x86,venfam0006mod003F:feature:,,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0017,0018,0019,001A,001C,002B,0034,003B,003D,0068,006F,0070,0072,0074,0075,0076,007D,0080,0081,0089,008C,008D,0091,0093,0094,0095,0096,0097,0098,0099,009A,009B,009C,009D,009E,009F,00C0,00C5,0120,0123,0125,0127,0128,0129,012A,0140
```

Update the rngd modalias rule to match this so udev properly has
systemd start rngd.


  Commit: 3f02cbbcaf18626e1f6a1824cfce142ad48ec614
  
https://github.com/NixOS/nixpkgs/commit/3f02cbbcaf18626e1f6a1824cfce142ad48ec614
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-19 (Mon, 19 Sep 2016)

  Changed paths:
M nixos/modules/security/rngd.nix

  Log Message:
  ---
  Merge branch 'rngd-wantedBy' of git://github.com/srp/nixpkgs-1


Compare: https://github.com/NixOS/nixpkgs/compare/e453c6288532...3f02cbbcaf18___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] beb349: darwin.cctools: Fix build on linux

[Shea Levy]

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: beb349339d07b52cf2bbc77485eaed018363ea7a
  
https://github.com/NixOS/nixpkgs/commit/beb349339d07b52cf2bbc77485eaed018363ea7a
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-17 (Sat, 17 Sep 2016)

  Changed paths:
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  darwin.cctools: Fix build on linux

(cherry picked from commit 11f4921cdf7da0e50b48363814d23aaf568cca2e)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 11f492: darwin.cctools: Fix build on linux

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 11f4921cdf7da0e50b48363814d23aaf568cca2e
  
https://github.com/NixOS/nixpkgs/commit/11f4921cdf7da0e50b48363814d23aaf568cca2e
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-17 (Sat, 17 Sep 2016)

  Changed paths:
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  darwin.cctools: Fix build on linux


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 952c47: nodePackages.bower2nix: Add back PATH wrapping

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 952c477f901f35a99758bcc8fdf8b685ad8fa3e0
  
https://github.com/NixOS/nixpkgs/commit/952c477f901f35a99758bcc8fdf8b685ad8fa3e0
  Author: Rodney Lorrimar <d...@rodney.id.au>
  Date:   2016-09-15 (Thu, 15 Sep 2016)

  Changed paths:
M pkgs/development/node-packages/default-v4.nix
M pkgs/development/node-packages/default-v5.nix
M pkgs/development/node-packages/default-v6.nix

  Log Message:
  ---
  nodePackages.bower2nix: Add back PATH wrapping

bower2nix and fetch-bower need git in the PATH to operate. This wrapping
got lost with the nodePackages updates.

(Fixes #18454)


  Commit: 131b8d4edb39d302db64ff284a7f5863d2d53522
  
https://github.com/NixOS/nixpkgs/commit/131b8d4edb39d302db64ff284a7f5863d2d53522
  Author: Rodney Lorrimar <d...@rodney.id.au>
  Date:   2016-09-15 (Thu, 15 Sep 2016)

  Changed paths:
M pkgs/development/node-packages/node-packages-v4.nix
M pkgs/development/node-packages/node-packages-v5.nix
M pkgs/top-level/node-packages-generated.nix

  Log Message:
  ---
  nodePackages.bower2nix: 3.0.1 -> 3.1.1


  Commit: bca7b782ae00e6f8f2be0d59bc473b7d00b745fc
  
https://github.com/NixOS/nixpkgs/commit/bca7b782ae00e6f8f2be0d59bc473b7d00b745fc
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-15 (Thu, 15 Sep 2016)

  Changed paths:
M pkgs/development/node-packages/default-v4.nix
M pkgs/development/node-packages/default-v5.nix
M pkgs/development/node-packages/default-v6.nix
M pkgs/development/node-packages/node-packages-v4.nix
M pkgs/development/node-packages/node-packages-v5.nix
M pkgs/top-level/node-packages-generated.nix

  Log Message:
  ---
  Merge branch 'bower2nix-3.1.1' of git://github.com/rvl/nixpkgs


Compare: https://github.com/NixOS/nixpkgs/compare/a32281639e19...bca7b782ae00___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 40e47a: freerdp: add missing libXrender dependency

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 40e47a95d71b9886932fdf7190d403f578f9e75e
  
https://github.com/NixOS/nixpkgs/commit/40e47a95d71b9886932fdf7190d403f578f9e75e
  Author: Peter Hoeg <pe...@speartail.com>
  Date:   2016-09-13 (Tue, 13 Sep 2016)

  Changed paths:
M pkgs/applications/networking/remote/freerdp/unstable.nix

  Log Message:
  ---
  freerdp: add missing libXrender dependency


  Commit: 49ba0b7896a4e8f70c2c8e9571c814e5dd1d3931
  
https://github.com/NixOS/nixpkgs/commit/49ba0b7896a4e8f70c2c8e9571c814e5dd1d3931
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-13 (Tue, 13 Sep 2016)

  Changed paths:
M pkgs/applications/networking/remote/freerdp/unstable.nix

  Log Message:
  ---
  Merge branch 'freerdp2' of git://github.com/peterhoeg/nixpkgs


Compare: https://github.com/NixOS/nixpkgs/compare/c542e6d239f6...49ba0b7896a4___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 38f074: melpa: Fix nix-buffer and inherit-local, add stabl...

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 38f074435a3a4a92ca0950e33cea1554f364fe70
  
https://github.com/NixOS/nixpkgs/commit/38f074435a3a4a92ca0950e33cea1554f364fe70
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-12 (Mon, 12 Sep 2016)

  Changed paths:
M pkgs/applications/editors/emacs-modes/melpa-generated.nix
M pkgs/applications/editors/emacs-modes/melpa-stable-generated.nix

  Log Message:
  ---
  melpa: Fix nix-buffer and inherit-local, add stable


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] c6460f: melpa: Add inherit-local, bump f.el

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: c6460fb0cbda179b83558a6e19c13a2d5f81a5ed
  
https://github.com/NixOS/nixpkgs/commit/c6460fb0cbda179b83558a6e19c13a2d5f81a5ed
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-10 (Sat, 10 Sep 2016)

  Changed paths:
M pkgs/applications/editors/emacs-modes/melpa-generated.nix
M pkgs/top-level/emacs-packages.nix

  Log Message:
  ---
  melpa: Add inherit-local, bump f.el


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 127924: Linux-kernel: Workaround for https://github.com/Ni...

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 127924954ba8d6452e1fbb67f18f9e67cb337aa3
  
https://github.com/NixOS/nixpkgs/commit/127924954ba8d6452e1fbb67f18f9e67cb337aa3
  Author: Lengyel Balázs <ikervag...@gmail.com>
  Date:   2016-09-09 (Fri, 09 Sep 2016)

  Changed paths:
M nixos/modules/system/boot/kernel.nix

  Log Message:
  ---
  Linux-kernel: Workaround for https://github.com/NixOS/nixpkgs/issues/18451

remove after upstream gets fixed


  Commit: 8ef2ed478ee1a1c2ed29936a79c87dc1e0c44708
  
https://github.com/NixOS/nixpkgs/commit/8ef2ed478ee1a1c2ed29936a79c87dc1e0c44708
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-09 (Fri, 09 Sep 2016)

  Changed paths:
M nixos/modules/system/boot/kernel.nix

  Log Message:
  ---
  Merge branch 'test' of https://github.com/ikervagyok/nixpkgs

Linux-kernel: Workaround for keyboard not working (#18462)


Compare: https://github.com/NixOS/nixpkgs/compare/c2397bf42540...8ef2ed478ee1___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nix] 8bddc3: Fix early removal of rc-file for nix-shell

[Shea Levy]

  Branch: refs/heads/1.11-maintenance
  Home:   https://github.com/NixOS/nix
  Commit: 8bddc3d406a07fcd10f2d08eaa81a2c4f4d66f1c
  
https://github.com/NixOS/nix/commit/8bddc3d406a07fcd10f2d08eaa81a2c4f4d66f1c
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-08 (Thu, 08 Sep 2016)

  Changed paths:
M scripts/nix-build.in

  Log Message:
  ---
  Fix early removal of rc-file for nix-shell

BASH_ENV causes all non-interactive shells called via eg. /etc/bashrc to
remove the rc-file before the main shell gets to run it. Completion
scripts will often do this. Fixes #976.

Adapted from and fixes #1034.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nix] a5f275: Fix early removal of rc-file for nix-shell

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nix
  Commit: a5f2750ebb1fb59679079139810e48b53abc51de
  
https://github.com/NixOS/nix/commit/a5f2750ebb1fb59679079139810e48b53abc51de
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-08 (Thu, 08 Sep 2016)

  Changed paths:
M src/nix-build/nix-build.cc

  Log Message:
  ---
  Fix early removal of rc-file for nix-shell

BASH_ENV causes all non-interactive shells called via eg. /etc/bashrc to
remove the rc-file before the main shell gets to run it. Completion
scripts will often do this. Fixes #976.

Adapted from and fixes #1034.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 4829cd: kernel: 4.7.2 -> 4.7.3

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 4829cd7f653fc3b33a8eeedba12568ee72a1599a
  
https://github.com/NixOS/nixpkgs/commit/4829cd7f653fc3b33a8eeedba12568ee72a1599a
  Author: Tim Steinbach <t...@nequissimus.com>
  Date:   2016-09-08 (Thu, 08 Sep 2016)

  Changed paths:
M pkgs/os-specific/linux/kernel/linux-4.7.nix

  Log Message:
  ---
  kernel: 4.7.2 -> 4.7.3


  Commit: f4c233929baee13b4af0237aa49e6e9521f3dfda
  
https://github.com/NixOS/nixpkgs/commit/f4c233929baee13b4af0237aa49e6e9521f3dfda
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-08 (Thu, 08 Sep 2016)

  Changed paths:
M pkgs/os-specific/linux/kernel/linux-4.7.nix

  Log Message:
  ---
  Merge branch 'kernel473' of https://github.com/NeQuissimus/nixpkgs


Compare: https://github.com/NixOS/nixpkgs/compare/e57b658049d0...f4c233929bae___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] ab9537: nixos: Generalise the container tests in stage-2 b...

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: ab9537ca22ce3fd4efc1795c58105504022d0c48
  
https://github.com/NixOS/nixpkgs/commit/ab9537ca22ce3fd4efc1795c58105504022d0c48
  Author: Rickard Nilsson <rickyn...@gmail.com>
  Date:   2016-09-07 (Wed, 07 Sep 2016)

  Changed paths:
M nixos/modules/system/boot/stage-2-init.sh

  Log Message:
  ---
  nixos: Generalise the container tests in stage-2 boot

This way, stage-2 behaves correctly also for libvirt-lxc containers.

Some more discussion on this:
https://github.com/NixOS/nixpkgs/commit/a7a08188bf650ababa36300a9a6f34169e2a73bf
https://github.com/NixOS/nixpkgs/commit/bfe46a653ba2f8ff9902128f485cbd87c49cbca7


  Commit: 03b888e205e030b2272582d7f4ff037daacc2ab0
  
https://github.com/NixOS/nixpkgs/commit/03b888e205e030b2272582d7f4ff037daacc2ab0
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-07 (Wed, 07 Sep 2016)

  Changed paths:
M nixos/modules/system/boot/stage-2-init.sh

  Log Message:
  ---
  Merge branch 'stage2-generalise-containers' of 
https://github.com/rickynils/nixpkgs


Compare: https://github.com/NixOS/nixpkgs/compare/70be99c6459b...03b888e205e0___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 29aac2: st: 0.6 -> 0.7

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 29aac270898118a446255ec00540e5ef258f802c
  
https://github.com/NixOS/nixpkgs/commit/29aac270898118a446255ec00540e5ef258f802c
  Author: asildnes <ands...@gmail.com>
  Date:   2016-09-06 (Tue, 06 Sep 2016)

  Changed paths:
M lib/maintainers.nix
M pkgs/applications/misc/st/default.nix
A pkgs/applications/misc/st/st-fix-deletekey.patch

  Log Message:
  ---
  st: 0.6 -> 0.7


  Commit: d81d59aad94db0baa0a5018c6b75e5659611cdb6
  
https://github.com/NixOS/nixpkgs/commit/d81d59aad94db0baa0a5018c6b75e5659611cdb6
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-06 (Tue, 06 Sep 2016)

  Changed paths:
M lib/maintainers.nix
M pkgs/applications/misc/st/default.nix
A pkgs/applications/misc/st/st-fix-deletekey.patch

  Log Message:
  ---
  Merge branch 'fix/st-update-0.7' of git://github.com/andsild/nixpkgs


Compare: https://github.com/NixOS/nixpkgs/compare/6340b32e4974...d81d59aad94d___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Announcing nix-buffer, nix-shell for emacs

[Shea Levy]

Hmm, I think we need more than just environment variables. See for
example my recent commit[1] to nixpkgs, where in addition to setting up
process-environment and exec-path I also set, when appropriate, several
proofgeneral variables like coq-prog-name and even call some
proofgeneral functions.

~Shea

[1]: 
https://github.com/NixOS/nixpkgs/commit/b04cdae902398aa76fb81a0470e18fd527c6ba3d
zimbatm <zimb...@zimbatm.com> writes:

> Hi Shea,
>
> did you look at direnv[1] yet? I have a feeling that it would mix with
> emacs pretty well and implement all that you need in a more generic way
> (which is a pro and con).
>
> Essentially what I do in my projects is use the following .envrc:
> ```bash
> use nix
> ```
> The `use nix` directive calls nix-shell under the hood so then the usual
> default.nix and shell.nix are loaded.
>
> In emacs the plugin would need to call `direnv export json` on enter/leave
> of a context. This gives you a diff of environment variables to apply.
> There is a bit more complexity when implementing the security framework but
> that's about it.
>
> I'm just curious if you thought of that approach, keep up the good work!
>
> Cheers,
> z
>
> [1]: http://direnv.net/
>
> On Mon, 5 Sep 2016 at 17:11 Shea Levy <s...@shealevy.com> wrote:
>
>> Sure! In my .emacs, I have:
>>
>> > (defun nix-buffer-find-file-hook ()
>> >   (when (not (file-remote-p (buffer-file-name)))
>> > (nix-buffer)))
>> > (add-hook 'find-file-hook 'nix-buffer-find-file-hook)
>>
>> I have coq 8.5pl1 installed in my configuration.nix, but I have a coq
>> project that requires 8.4pl6, so I have in that project's root directory
>> dir-locals.nix:
>>
>> > let pkgs = import  {}; in
>> >   pkgs.nixBufferBuilders.withPackages [ pkgs.coq ]
>>
>> (note that this relies on a recent nixpkgs commit[1]). Then whenever I
>> open a .v file in the project, ProofGeneral uses coq 8.4 rather than
>> 8.5.
>>
>> If I wanted, my dir-locals.nix could take a 'root' argument, which would
>> point to the file I opened.
>>
>> ~Shea
>>
>> [1]:
>> https://github.com/NixOS/nixpkgs/commit/05c132486d8cfae600bbfe8c9ac5d799b298afed
>>
>> Bas van Dijk <v.dijk@gmail.com> writes:
>>
>> > Hi Shea,
>> >
>> > As a Nix and Emacs user this looks very interesting. I didn't know about
>> > Buffer-Local Variables before.
>> >
>> > Can you share some applications of nix-buffer / how you are using it?
>> >
>> > Thanks!
>> >
>> > Bas
>> >
>> > On 5 September 2016 at 08:06, Shea Levy <s...@shealevy.com> wrote:
>> >
>> >> Hi all,
>> >>
>> >> I've just pushed the initial version of nix-buffer[1], and opened a PR
>> >> for adding it to melpa[2]. The description of the 'nix-buffer-enter'
>> >> command this library defines:
>> >>
>> >> > Set up the buffer according to the directory-local nix expression.
>> >> >
>> >> > Looks for dir-locals.nix upward from the current directory.  If found,
>> >> > builds the derivation defined there with the 'root' arg set to the
>> >> > current buffer file name or directory and evaluates the resulting
>> >> > elisp if safe to do so.
>> >> >
>> >> > Because in practice dir-locals.nix will always want to do things that
>> >> > are unsafe in dir-locals.el (e.g. append to 'exec-path'), we don't
>> >> > reuse that mechanism and instead just load the file as elisp.  Because
>> >> > this allows arbitrary code execution, the first time we're asked to
>> >> > load a particular store path we query the user to verify if it's safe
>> >> > to load beforehand.
>> >> >
>> >> > The Lisp code generated by dir-locals.nix should limit itself to
>> >> > modifying buffer-local variables, but there is no actual enforcement
>> >> > of this.  'setq-local' is your friend.
>> >>
>> >> It may be useful to advise the 'normal-mode' function to call
>> >> 'nix-buffer-enter' beforehand for local files, so that all visited files
>> >> have their environments set up before modes are loaded.
>> >>
>> >> Note that this is my first elisp package, so feedback definitely
>> >> welcome!
>> >>
>> >> In addition to the elisp work mentioned in the TODO[3], it would be
>> >> useful to add some f

Re: [Nix-dev] NixOps usage survey.

[Shea Levy]

If you're on a system with a pure stdenv (linux or pure-darwin) and find
yourself needing to turn off the sandbox, most likely there is a bug in
nix or you are doing something wrong. Please don't recommend turning off
the sandbox unless you are very sure you know what you're doing and that
the person you're recommending it to understands the relevant issues.

stewart mackenzie  writes:

> On 6 Sep 2016 00:01, "Aloïs Cochard"  wrote:
>> We do plan to use it for our development infrastructure
>
> You'll need to implement incremental recompilation (IR) to reduce
> compilation times. It's not too difficult to implement if you know _not_ to
> set nix.useSandbox = true; .
>
> Ping me when/if you get to that bridge and I'll assist.
>
> Kr/sjm
> ___
> 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-commits] [NixOS/nixpkgs] f4c89b: strongswan: 5.4.0 -> 5.5.0

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: f4c89ba854eb8e2adca5586b135013062272f7b3
  
https://github.com/NixOS/nixpkgs/commit/f4c89ba854eb8e2adca5586b135013062272f7b3
  Author: Alexander Ried <r...@mytum.de>
  Date:   2016-09-05 (Mon, 05 Sep 2016)

  Changed paths:
M pkgs/tools/networking/strongswan/default.nix

  Log Message:
  ---
  strongswan: 5.4.0 -> 5.5.0


  Commit: e7da789920c470cfd4279be3078a52b652a37c62
  
https://github.com/NixOS/nixpkgs/commit/e7da789920c470cfd4279be3078a52b652a37c62
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-05 (Mon, 05 Sep 2016)

  Changed paths:
M pkgs/tools/networking/strongswan/default.nix

  Log Message:
  ---
  Merge branch 'strongswan' of git://github.com/groxxda/nixpkgs


Compare: https://github.com/NixOS/nixpkgs/compare/3beacc4dbe24...e7da789920c4___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] cb9b31: nixBufferBuilders.withPackages: Make more legible, ...

[Shea Levy]

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: cb9b3110253a65a00d3f5d35ae87e18e197f85ef
  
https://github.com/NixOS/nixpkgs/commit/cb9b3110253a65a00d3f5d35ae87e18e197f85ef
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-05 (Mon, 05 Sep 2016)

  Changed paths:
M pkgs/build-support/emacs/buffer.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  nixBufferBuilders.withPackages: Make more legible, special-case proof-general.

There's some bigger changes coming, but thought I'd push this first...

(cherry picked from commit b04cdae902398aa76fb81a0470e18fd527c6ba3d)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] b04cda: nixBufferBuilders.withPackages: Make more legible, ...

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: b04cdae902398aa76fb81a0470e18fd527c6ba3d
  
https://github.com/NixOS/nixpkgs/commit/b04cdae902398aa76fb81a0470e18fd527c6ba3d
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-05 (Mon, 05 Sep 2016)

  Changed paths:
M pkgs/build-support/emacs/buffer.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  nixBufferBuilders.withPackages: Make more legible, special-case proof-general.

There's some bigger changes coming, but thought I'd push this first...


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Announcing nix-buffer, nix-shell for emacs

[Shea Levy]

Sure! In my .emacs, I have:

> (defun nix-buffer-find-file-hook ()
>   (when (not (file-remote-p (buffer-file-name)))
> (nix-buffer)))
> (add-hook 'find-file-hook 'nix-buffer-find-file-hook)

I have coq 8.5pl1 installed in my configuration.nix, but I have a coq
project that requires 8.4pl6, so I have in that project's root directory
dir-locals.nix:

> let pkgs = import  {}; in
>   pkgs.nixBufferBuilders.withPackages [ pkgs.coq ]

(note that this relies on a recent nixpkgs commit[1]). Then whenever I
open a .v file in the project, ProofGeneral uses coq 8.4 rather than
8.5.

If I wanted, my dir-locals.nix could take a 'root' argument, which would
point to the file I opened.

~Shea

[1]: 
https://github.com/NixOS/nixpkgs/commit/05c132486d8cfae600bbfe8c9ac5d799b298afed

Bas van Dijk <v.dijk@gmail.com> writes:

> Hi Shea,
>
> As a Nix and Emacs user this looks very interesting. I didn't know about
> Buffer-Local Variables before.
>
> Can you share some applications of nix-buffer / how you are using it?
>
> Thanks!
>
> Bas
>
> On 5 September 2016 at 08:06, Shea Levy <s...@shealevy.com> wrote:
>
>> Hi all,
>>
>> I've just pushed the initial version of nix-buffer[1], and opened a PR
>> for adding it to melpa[2]. The description of the 'nix-buffer-enter'
>> command this library defines:
>>
>> > Set up the buffer according to the directory-local nix expression.
>> >
>> > Looks for dir-locals.nix upward from the current directory.  If found,
>> > builds the derivation defined there with the 'root' arg set to the
>> > current buffer file name or directory and evaluates the resulting
>> > elisp if safe to do so.
>> >
>> > Because in practice dir-locals.nix will always want to do things that
>> > are unsafe in dir-locals.el (e.g. append to 'exec-path'), we don't
>> > reuse that mechanism and instead just load the file as elisp.  Because
>> > this allows arbitrary code execution, the first time we're asked to
>> > load a particular store path we query the user to verify if it's safe
>> > to load beforehand.
>> >
>> > The Lisp code generated by dir-locals.nix should limit itself to
>> > modifying buffer-local variables, but there is no actual enforcement
>> > of this.  'setq-local' is your friend.
>>
>> It may be useful to advise the 'normal-mode' function to call
>> 'nix-buffer-enter' beforehand for local files, so that all visited files
>> have their environments set up before modes are loaded.
>>
>> Note that this is my first elisp package, so feedback definitely
>> welcome!
>>
>> In addition to the elisp work mentioned in the TODO[3], it would be
>> useful to add some functions to nixpkgs to build elisp files,
>> especially:
>>
>> * A function taking a derivation and building an elisp file that sets up
>>   the buffer environment analogous to the build environment specified by
>>   that derivation
>> * A function taking a list of packages and building an elisp file that
>>   sets up the buffer environment with all of those packages available
>>   (in PATH, in the emacs load path, etc.).
>>
>> Happy hacking!
>>
>> ~Shea
>>
>> [1]: https://github.com/shlevy/nix-buffer/tree/v1.0
>> [2]: https://github.com/melpa/melpa/pull/4204
>> [3]: https://github.com/shlevy/nix-buffer/blob/v1.0/TODO.md
>>
>> ___
>> 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-commits] [NixOS/nixpkgs] 50e373: Initial version of nixBufferBuilders.withPackages.

[Shea Levy]

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 50e3737c1af2f28fad9e0a246abcba5f83724a2a
  
https://github.com/NixOS/nixpkgs/commit/50e3737c1af2f28fad9e0a246abcba5f83724a2a
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-05 (Mon, 05 Sep 2016)

  Changed paths:
A pkgs/build-support/emacs/buffer.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Initial version of nixBufferBuilders.withPackages.

This builds elisp to setup an emacs buffer with the packages given
available. See shlevy/nix-buffer for more information.

Currently only modifies $PATH.

(cherry picked from commit 05c132486d8cfae600bbfe8c9ac5d799b298afed)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 05c132: Initial version of nixBufferBuilders.withPackages.

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 05c132486d8cfae600bbfe8c9ac5d799b298afed
  
https://github.com/NixOS/nixpkgs/commit/05c132486d8cfae600bbfe8c9ac5d799b298afed
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-05 (Mon, 05 Sep 2016)

  Changed paths:
A pkgs/build-support/emacs/buffer.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Initial version of nixBufferBuilders.withPackages.

This builds elisp to setup an emacs buffer with the packages given
available. See shlevy/nix-buffer for more information.

Currently only modifies $PATH.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] cbb177: Backport proofgeneral_HEAD

[Shea Levy]

  Branch: refs/heads/release-16.03
  Home:   https://github.com/NixOS/nixpkgs
  Commit: cbb1774631f7d6a49e9e684cc1e5f3911bedf056
  
https://github.com/NixOS/nixpkgs/commit/cbb1774631f7d6a49e9e684cc1e5f3911bedf056
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-05 (Mon, 05 Sep 2016)

  Changed paths:
A pkgs/applications/editors/emacs-modes/proofgeneral/HEAD.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Backport proofgeneral_HEAD


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 97da03: proofgeneral_HEAD: bump

[Shea Levy]

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 97da0327112be686cbc3f91089d86f494bf2100c
  
https://github.com/NixOS/nixpkgs/commit/97da0327112be686cbc3f91089d86f494bf2100c
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-05 (Mon, 05 Sep 2016)

  Changed paths:
M pkgs/applications/editors/emacs-modes/proofgeneral/HEAD.nix

  Log Message:
  ---
  proofgeneral_HEAD: bump

(cherry picked from commit d1154edf441411bae1363ddb1eb5c7ddd379642d)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] d1154e: proofgeneral_HEAD: bump

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: d1154edf441411bae1363ddb1eb5c7ddd379642d
  
https://github.com/NixOS/nixpkgs/commit/d1154edf441411bae1363ddb1eb5c7ddd379642d
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-05 (Mon, 05 Sep 2016)

  Changed paths:
M pkgs/applications/editors/emacs-modes/proofgeneral/HEAD.nix

  Log Message:
  ---
  proofgeneral_HEAD: bump


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Announcing nix-buffer, nix-shell for emacs

[Shea Levy]

Doubt anyone has managed to start using this yet, but FYI I've changed
the name of the command to just 'nix-buffer'. Will add to nixpkgs once
it's merged into melpa.

Shea Levy <s...@shealevy.com> writes:

> [ Unknown signature status ]
> Hi all,
>
> I've just pushed the initial version of nix-buffer[1], and opened a PR
> for adding it to melpa[2]. The description of the 'nix-buffer-enter'
> command this library defines:
>
>> Set up the buffer according to the directory-local nix expression.
>>
>> Looks for dir-locals.nix upward from the current directory.  If found,
>> builds the derivation defined there with the 'root' arg set to the
>> current buffer file name or directory and evaluates the resulting
>> elisp if safe to do so.
>>
>> Because in practice dir-locals.nix will always want to do things that
>> are unsafe in dir-locals.el (e.g. append to 'exec-path'), we don't
>> reuse that mechanism and instead just load the file as elisp.  Because
>> this allows arbitrary code execution, the first time we're asked to
>> load a particular store path we query the user to verify if it's safe
>> to load beforehand.
>>
>> The Lisp code generated by dir-locals.nix should limit itself to
>> modifying buffer-local variables, but there is no actual enforcement
>> of this.  'setq-local' is your friend.
>
> It may be useful to advise the 'normal-mode' function to call
> 'nix-buffer-enter' beforehand for local files, so that all visited files
> have their environments set up before modes are loaded.
>
> Note that this is my first elisp package, so feedback definitely
> welcome!
>
> In addition to the elisp work mentioned in the TODO[3], it would be
> useful to add some functions to nixpkgs to build elisp files,
> especially:
>
> * A function taking a derivation and building an elisp file that sets up
>   the buffer environment analogous to the build environment specified by
>   that derivation
> * A function taking a list of packages and building an elisp file that
>   sets up the buffer environment with all of those packages available
>   (in PATH, in the emacs load path, etc.).
>
> Happy hacking!
>
> ~Shea
>
> [1]: https://github.com/shlevy/nix-buffer/tree/v1.0
> [2]: https://github.com/melpa/melpa/pull/4204
> [3]: https://github.com/shlevy/nix-buffer/blob/v1.0/TODO.md


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] Announcing nix-buffer, nix-shell for emacs

[Shea Levy]

Hi all,

I've just pushed the initial version of nix-buffer[1], and opened a PR
for adding it to melpa[2]. The description of the 'nix-buffer-enter'
command this library defines:

> Set up the buffer according to the directory-local nix expression.
>
> Looks for dir-locals.nix upward from the current directory.  If found,
> builds the derivation defined there with the 'root' arg set to the
> current buffer file name or directory and evaluates the resulting
> elisp if safe to do so.
>
> Because in practice dir-locals.nix will always want to do things that
> are unsafe in dir-locals.el (e.g. append to 'exec-path'), we don't
> reuse that mechanism and instead just load the file as elisp.  Because
> this allows arbitrary code execution, the first time we're asked to
> load a particular store path we query the user to verify if it's safe
> to load beforehand.
>
> The Lisp code generated by dir-locals.nix should limit itself to
> modifying buffer-local variables, but there is no actual enforcement
> of this.  'setq-local' is your friend.

It may be useful to advise the 'normal-mode' function to call
'nix-buffer-enter' beforehand for local files, so that all visited files
have their environments set up before modes are loaded.

Note that this is my first elisp package, so feedback definitely
welcome!

In addition to the elisp work mentioned in the TODO[3], it would be
useful to add some functions to nixpkgs to build elisp files,
especially:

* A function taking a derivation and building an elisp file that sets up
  the buffer environment analogous to the build environment specified by
  that derivation
* A function taking a list of packages and building an elisp file that
  sets up the buffer environment with all of those packages available
  (in PATH, in the emacs load path, etc.).

Happy hacking!

~Shea

[1]: https://github.com/shlevy/nix-buffer/tree/v1.0
[2]: https://github.com/melpa/melpa/pull/4204
[3]: https://github.com/shlevy/nix-buffer/blob/v1.0/TODO.md


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] 7bc6fa: php70Packages.v8js: init at 1.3.2

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 7bc6fa344a2fe616135696b2f26a328e6235366b
  
https://github.com/NixOS/nixpkgs/commit/7bc6fa344a2fe616135696b2f26a328e6235366b
  Author: Stefan Siegl <ste...@brokenpipe.de>
  Date:   2016-09-04 (Sun, 04 Sep 2016)

  Changed paths:
M pkgs/top-level/php-packages.nix

  Log Message:
  ---
  php70Packages.v8js: init at 1.3.2


  Commit: df3103729e7a34585e236896f683b4efcc077554
  
https://github.com/NixOS/nixpkgs/commit/df3103729e7a34585e236896f683b4efcc077554
  Author: Stefan Siegl <ste...@brokenpipe.de>
  Date:   2016-09-04 (Sun, 04 Sep 2016)

  Changed paths:
M pkgs/top-level/php-packages.nix

  Log Message:
  ---
  phpPackages.spidermonkey: init a 1.0.0


  Commit: c76c0bedc10a5443bce53915cb77b1c3dd89b2b0
  
https://github.com/NixOS/nixpkgs/commit/c76c0bedc10a5443bce53915cb77b1c3dd89b2b0
  Author: Stefan Siegl <ste...@brokenpipe.de>
  Date:   2016-09-04 (Sun, 04 Sep 2016)

  Changed paths:
M pkgs/top-level/php-packages.nix

  Log Message:
  ---
  php70Packages.v8: init at 0.1.0


  Commit: 224889e452fcf1067a94bb014dd266aca2c3eec8
  
https://github.com/NixOS/nixpkgs/commit/224889e452fcf1067a94bb014dd266aca2c3eec8
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-04 (Sun, 04 Sep 2016)

  Changed paths:
M pkgs/top-level/php-packages.nix

  Log Message:
  ---
  Merge branch 'php-javascript-extensions' of git://github.com/stesie/nixpkgs


Compare: https://github.com/NixOS/nixpkgs/compare/845cb949fca5...224889e452fc___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] dejavu-fonts environment collision

[Shea Levy]

Applied, thanks!

Karn Kallio  writes:

> After splitting the DejaVuSans.ttf file into a multiple output in the
> dejavu_fonts Nixpkgs expression it is not possible to install in the
> user profile due to the collision.  The attached patch makes a new
> package without the collision for user environment installing.
> From fae78903c6ce56eda70a1a9a6914c41d248b15e8 Mon Sep 17 00:00:00 2001
> From: Karn Kallio 
> Date: Sat, 3 Sep 2016 14:09:36 -0400
> Subject: [PATCH] dejavu-fonts : Prepare an environment package without
>  collision.
>
> ---
>  pkgs/top-level/all-packages.nix | 7 ++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix
> index 4f6946f..a41b0c2 100644
> --- a/pkgs/top-level/all-packages.nix
> +++ b/pkgs/top-level/all-packages.nix
> @@ -11931,8 +11931,13 @@ in
>  
>crimson = callPackage ../data/fonts/crimson {};
>  
> -  dejavu_fonts = callPackage ../data/fonts/dejavu-fonts {
> +  dejavu_fonts = lowPrio (callPackage ../data/fonts/dejavu-fonts {
>  inherit (perlPackages) FontTTF;
> +  });
> +
> +  dejavu_fontsEnv = buildEnv {
> +name = "${dejavu_fonts.name}";
> +paths = [ dejavu_fonts.out ];
>};
>  
>dina-font = callPackage ../data/fonts/dina { };
> -- 
> 2.9.3
>
> ___
> 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-commits] [NixOS/nixpkgs] a3f2c9: spl: mark it broken on kernels higher then 4.7

[Shea Levy]

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: a3f2c9d8413c3c3d437e5af11443df67ee19af4d
  
https://github.com/NixOS/nixpkgs/commit/a3f2c9d8413c3c3d437e5af11443df67ee19af4d
  Author: Rok Garbas <r...@garbas.si>
  Date:   2016-09-03 (Sat, 03 Sep 2016)

  Changed paths:
M pkgs/os-specific/linux/spl/default.nix

  Log Message:
  ---
  spl: mark it broken on kernels higher then 4.7

until new spl version is release


  Commit: a27f1dc013b07af641239f0fedd72e8d35c967e7
  
https://github.com/NixOS/nixpkgs/commit/a27f1dc013b07af641239f0fedd72e8d35c967e7
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-03 (Sat, 03 Sep 2016)

  Changed paths:
M pkgs/os-specific/linux/spl/default.nix

  Log Message:
  ---
  Merge branch 'broken-spl-on-kernel-4.7' of git://github.com/garbas/nixpkgs 
into release-16.09

Refs #18209


Compare: https://github.com/NixOS/nixpkgs/compare/e5e45773e19e...a27f1dc013b0___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Limiting access to only maintained packages and ensuring core packages are maintained

[Shea Levy]

Layus  writes:

> Could you elaborate more on how you plan to implement this ?
> Who will be responsible to maintain maintainers ;-) ?
> Do you plan to automate it somehow ?

The first thing, straightforward to do, is add an option to not build
unmaintained packages and add a jobset to build this set. Second is to
publicize the decided-upon policies to devs and users through
documentation. Then there are a few routes that in some combination can
hopefully maintain maintainership:

1. Some people can regularly watch or even possibly subscribe to the
   "maintained" jobset. If something fails, they can reach out and
   eventually remove the maintainer from that package if appropriate
2. We can have issue tags differentiating issues with maintained vs
   unmaintained packages. For PRs this can even be automated. Again
   people watching those tags can make a change if there is an
   unresponsive maintainer
3. We can encourage users to first try to get the attention of the
   maintainers of the relevant packages and then escalate to a list of
   maintainer maintainers if no response is forthcoming.

Any other ideas that might be useful here?


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Limiting access to only maintained packages and ensuring core packages are maintained

[Shea Levy]

No, not something automated like that. Though mention-bot seems to work
decently well, it doesn't know for example that changes to
all-packages.nix are much less useful than changes to a default.nix file
in a package directory. A human can know that, and additionally look at
the log messages to see the nature of the changes to see if they're
likely to be relevant.

Bardur Arantsson <s...@scientician.net> writes:

> On 2016-09-02 23:16, Shea Levy wrote:
>> Why can't people use the commit logs to see who is knowledgeable?
>
> Are you thinking of something like https://github.com/facebook/mention-bot ?
>
> This fails in the case where someone does a big cross-cutting (i.e. not
> concerned with particular packages) refactor which happens to touch a
> lot of code. Suddenly you'd get a huge number of notifications about
> *every package under the sun*.
>
> (Why, yes, I *have* been the 'victim' of this type of thing in a GitHub
> repo where the project uses mention-bot. Now, some of that may simply be
> due to the algorithm that mention-bot uses, but it's pretty hard to
> avoid unless you're *somehow* able to algorithmically distinguish
> large-scale cross-cutting refactors from actual package maintenance
> changes.)
>
> Regards,
>
>
> ___
> 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

Re: [Nix-dev] Limiting access to only maintained packages and ensuring core packages are maintained

[Shea Levy]

maintainers.nix contains email addresses and for many of us uses the
same as our github handles. So users should be told to ping on github
*and* email when they find an issue, and then if someone is unresponsive
through that we can (if we're sticking with 3) remove them after some
time.

Hydra will email you if the build status of a package you maintain
changes.


Thomas Hunger <tehun...@gmail.com> writes:

> I'm mostly worried about leaning that I need to fix a package that I'm
> maintaining. I care about fixing bugs and purging unmaintaned packages, but
> most of the time I don't even see the report, or I know it's broken in
> hydra until I test again locally.
>
> Do you have any ideas around getting word out to maintainers sooner?
>
> On 2 September 2016 at 21:22, Shea Levy <s...@shealevy.com> wrote:
>
>> Hi all,
>>
>> I think a few changes might improve package stability a bit:
>>
>> 1. Add a nixpkgs config setting to throw an error on packages with no
>>meta.maintainers
>> 2. Work to reach a point where a significant subset of nixpkgs (say,
>>release-small) is allowed on this list.
>> 3. Remove maintainers after X weeks without reply on issues they're
>>tagged in about packages they maintain
>> 4. (Optional) Separate out maintainers by system
>>
>> Thoughts on these?
>>
>> ~Shea
>>
>> ___
>> 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

Re: [Nix-dev] Limiting access to only maintained packages and ensuring core packages are maintained

[Shea Levy]

Why can't people use the commit logs to see who is knowledgeable? I
believe we should have some way to denote "this person has committed to
make reasonable efforts to keep this package working properly", and the
maintainers field seems the right fit.

But anyway, limiting 3 to release-small or whatever important subset we
choose is a good change even if we don't go all the way.

~Shea

Layus <layus...@gmail.com> writes:

> Hi Shea,
>
> I like this idea, except for the part where you forcefully remove 
> maintainers.
> I have always seen maintainers as knowledgeable on the package, not 
> bound to reply on issues about it.
> Just ensure that X is big enough :-).
>
> I really like this idea if we limit (3.) to release-small packages or 
> some subset of core packages.
>
> -- Layus.
>
> On 02/09/16 22:22, Shea Levy wrote:
>> Hi all,
>>
>> I think a few changes might improve package stability a bit:
>>
>> 1. Add a nixpkgs config setting to throw an error on packages with no
>> meta.maintainers
>> 2. Work to reach a point where a significant subset of nixpkgs (say,
>> release-small) is allowed on this list.
>> 3. Remove maintainers after X weeks without reply on issues they're
>> tagged in about packages they maintain
>> 4. (Optional) Separate out maintainers by system
>>
>> Thoughts on these?
>>
>> ~Shea
>>
>>
>> ___
>> 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] Limiting access to only maintained packages and ensuring core packages are maintained

[Shea Levy]

Hi all,

I think a few changes might improve package stability a bit:

1. Add a nixpkgs config setting to throw an error on packages with no
   meta.maintainers
2. Work to reach a point where a significant subset of nixpkgs (say,
   release-small) is allowed on this list.
3. Remove maintainers after X weeks without reply on issues they're
   tagged in about packages they maintain
4. (Optional) Separate out maintainers by system

Thoughts on these?

~Shea


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] pygobject

[Shea Levy]

Applied, thanks!

Karn Kallio  writes:

> In the pygobject package of pythonPackages the codegen python files are
> executable and get wrapped, which causes pygtk to not build because it
> uses the python program to execute them.  The attached patch makes them
> not executable so they do not get wrapped and cause pygtk to fail its
> build.
> From 931b7998658fa72323c9a76e7b336fe726a9cc61 Mon Sep 17 00:00:00 2001
> From: Karn Kallio 
> Date: Fri, 2 Sep 2016 15:30:42 -0400
> Subject: [PATCH] pygobject: prevent wrapping of codegen/*.py files.
>
> ---
>  pkgs/development/python-modules/pygobject/default.nix | 4 
>  1 file changed, 4 insertions(+)
>
> diff --git a/pkgs/development/python-modules/pygobject/default.nix 
> b/pkgs/development/python-modules/pygobject/default.nix
> index 5c9367a..7f2bd63 100644
> --- a/pkgs/development/python-modules/pygobject/default.nix
> +++ b/pkgs/development/python-modules/pygobject/default.nix
> @@ -26,6 +26,10 @@ mkPythonDerivation rec {
># effect, but we leave it in case somebody expects and calls it.
>postInstall = ''
>  mv $out/lib/${python.libPrefix}/site-packages/{pygtk.pth,${name}.pth}
> +
> +# Prevent wrapping of codegen files as these are meant to be
> +# executed by the python program
> +chmod a-x $out/share/pygobject/*/codegen/*.py
>'';
>  
>meta = {
> -- 
> 2.9.3
>
> ___
> 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-commits] [NixOS/nixpkgs] b3871e: phc-intel: 0.4.0rev19 -> 0.4.0rev22

[Shea Levy]

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: b3871e4b7bd64fd82f5353ad1e70c773eddfd42c
  
https://github.com/NixOS/nixpkgs/commit/b3871e4b7bd64fd82f5353ad1e70c773eddfd42c
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-09-02 (Fri, 02 Sep 2016)

  Changed paths:
M pkgs/os-specific/linux/phc-intel/default.nix

  Log Message:
  ---
  phc-intel: 0.4.0rev19 -> 0.4.0rev22

Fixes build on linux 4.7

(cherry picked from commit ce0043bf4cc208a4f3e0a69ff7347b39f3557964)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] glu dev in mesa attribute

[Shea Levy]

Applied, thanks!

Karn Kallio  writes:

> After making multiple outputs in the mesa_glu package the headers are
> not included in the mesa attribute.  The attached patch puts them in it.
> From ced24208a300bea8234e7898ae6fec34fbd67289 Mon Sep 17 00:00:00 2001
> From: Karn Kallio 
> Date: Thu, 1 Sep 2016 16:18:23 -0400
> Subject: [PATCH] mesa: Add the mesa glu headers to the mesa attribute.
>
> ---
>  pkgs/top-level/all-packages.nix | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix
> index 99ed6b0..eb5fdb0 100644
> --- a/pkgs/top-level/all-packages.nix
> +++ b/pkgs/top-level/all-packages.nix
> @@ -8774,7 +8774,7 @@ in
>  name = "mesa-${mesa_noglu.version}";
>  # FIXME: this causes mesa to have a runtime dependency on
>  # mesa_noglu.dev.
> -paths = [ mesa_noglu.dev mesa_noglu.out mesa_glu ];
> +paths = [ mesa_noglu.dev mesa_noglu.out mesa_glu mesa_glu.dev ];
>  meta = {
>platforms = lib.platforms.unix;
>  };
> -- 
> 2.9.3
>
> ___
> 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

Re: [Nix-dev] GHC "unable to decommit memory"

[Shea Levy]

It is common practice when developing against relatively recent features
to handle ENOSYS/EINVAL/etc. in *application* code. It's completely
proper that the library exports it anyway.

Kevin Cox  writes:

> On Sep 1, 2016 10:03, "Eelco Dolstra"  wrote:
>>
>> Hi,
>>
>> On 09/01/2016 10:09 AM, Kevin Cox wrote:
>>
>> > Sounds more like we need glibc to support the kernel we are using. GHC
> is
>> > behaving fine and probably not the only program to have this problem.
>>
>> Glibc supports our kernel just fine - it just makes available some
> features that
>> our kernel doesn't have, which is not uncommon. I mean, what should Glibc
> do in
>> this case? The fix would be to build GHC with
> --disable-large-address-space or
>> apply patch https://ghc.haskell.org/trac/ghc/ticket/12495.
>>
>
> It doesn't sound just fine if it is advertising features that don't exist.
> Is there a way to prevent glibc from saying that MADV_FREE is supported? I
> understand that glibc "supports" it but it probably shouldn't be advertised
> if the kernel underneath doesn't.
> ___
> 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

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

No, it did, I just got confused by the thread, sorry!

Moritz Ulrich <mor...@tarn-vedra.de> writes:

> [ Unknown signature status ]
> Shea Levy <s...@shealevy.com> writes:
>
>>> This Moritz is the straw breaking the camel's back
>>
>> What, where did moritz come into this conversation?
>
> Just chiming in here: I answered to his mail, explaining why I didn't
> merge one of his PR right away. Did this mail fail to make it to the
> mailing list?


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

stewart mackenzie  writes:
>  Having @globin close the PR without a complete understanding

From the discussion there, globin understood your change perfectly well
and his closure was appropriate.

> Notice eelco saying lowprio is needed yet [1] has landed in mainline.

You are the one failing to understand what happened here. lowPrio is
needed for beta/unstable packages exposed to nix-env. I pushed that
commit because rustBeta and rustUnstable are package *sets*, not
packages, which lack recurseIntoAttrs and thus aren't exposed to
nix-env. Thus, the lowPrio was doing nothing. But this has *nothing* to
do with your original PR or the issue you were dealing with there, and
only came up because I was trying to demonstrate to you how lowPrio
actually worked.

> If you guys are not prepared to break apart this forming 'in
> crowd' with the C4, then what are your procedures on removing cultivated
> bad maintainers, or will you just let this become a systemic problem?

Show us a real example of a bad maintainer or even a maintainer behaving
badly, then we can discuss solving that problem. But note that "discuss
solving the problem" is not the same as "accept the solution you propose
without justification". If there is an issue with maintainer
behavior/incentives, and I don't really think there is in the sense you
are saying, then it does not automatically follow that we must adopt C4.

> Shall I reciprocate with the same level of rudeness I receive
> when submitting a patch?

In all of the discussions relating to this, you are the only one I've
seen being rude so far.

> Then to have another PR created [1] by the person who didn't take the time
> or energy to even read or understand the C4.

I think your links were messed up here, both of the PRs in your link
list were created by you. If, however, you are referring to the commit
where I removed the lowPrio from rustUnstable and rustBeta: I read the
link you provided. It did not immediately strike me as useful nor did it
provide justification for itself. I gave you every opportunity to
clarify, and you were rude and implied I was blind to the obvious. I
disagree with you, that is not the same as not taking the time or energy
to engage with you.

> This Moritz is the straw breaking the camel's back

What, where did moritz come into this conversation?

> Having people go around running algos on your level of
> commitment is such utter and total bullshit.

Can you point to an example of this happening? If it is actually
occurring, I agree it's bullshit and should be stopped if possible.

> Maybe I should just stop interacting with
> the nix crowd? Would you prefer that? If you'll let me maintain 1, only 1
> package on nixpkgs - a nix shell I'm developing. That's it I promise. I
> won't touch any other code. (See how mental that is?)

No one asked you to make this promise, so don't blame us for how
"mental" you think it is.

> Think about it for a second, when has the legal system ever passed laws to
> limit it's own power?

Who do you think signs constitutions?

> Passing the C4 will limit even Eelco's power. Imagine
> every single maintainer not being able to merge their own commits.

That sounds like a very inefficient state of affairs, with no clear benefit.


> The way lethalman handled this PR of mine is exactly the correct way [3]
> except there should have been no dialogue or at least reducing as much
> upfront consensus as possible

Why do we have PRs at all if they're just going to be merged automatically?

> Indeed, this is exactly what @globin should have done, cause I would
> have fixed it if it was broken, why? Cause that bit of code is in my
> L1 cache not @globin's. If for example I broke it and didn't fix it
> again, revert my commit.

globin saw, correctly, that your patch was broken. Why should it be
merged if it is known to be wrong?


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/nix] 80ebc5: nix-build: Port to c++

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nix
  Commit: 80ebc553eca19dafc64c47420cd49ddd506bc9b7
  
https://github.com/NixOS/nix/commit/80ebc553eca19dafc64c47420cd49ddd506bc9b7
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-09 (Tue, 09 Aug 2016)

  Changed paths:
M .gitignore
M Makefile
M scripts/local.mk
R scripts/nix-build.in
A src/nix-build/local.mk
A src/nix-build/nix-build.cc

  Log Message:
  ---
  nix-build: Port to c++

This was a dumb line-for-line rewrite, because nix build/nix run/etc.
will replace it.


  Commit: 1bffd83e1a9cdf3271c2b178daa611c6b9c22f58
  
https://github.com/NixOS/nix/commit/1bffd83e1a9cdf3271c2b178daa611c6b9c22f58
  Author: Vladimír Čunát <vladimir.cu...@nic.cz>
  Date:   2016-08-11 (Thu, 11 Aug 2016)

  Changed paths:
M src/nix-build/nix-build.cc

  Log Message:
  ---
  nix-build: extend the meaning of $IN_NIX_SHELL

An equivalent was originally filed against the perl version:
https://github.com/NixOS/nix/pull/933


  Commit: 821380c77bbfeb945d2b8a39a876c7c6ef090988
  
https://github.com/NixOS/nix/commit/821380c77bbfeb945d2b8a39a876c7c6ef090988
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-31 (Wed, 31 Aug 2016)

  Changed paths:
M src/nix-build/nix-build.cc

  Log Message:
  ---
  nix-build: Clean up a bit


  Commit: 87b189c2b326c790a35ff53a2d825c1ef48f644e
  
https://github.com/NixOS/nix/commit/87b189c2b326c790a35ff53a2d825c1ef48f644e
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-31 (Wed, 31 Aug 2016)

  Changed paths:
M .gitignore
M Makefile
M scripts/local.mk
R scripts/nix-build.in
A src/nix-build/local.mk
A src/nix-build/nix-build.cc

  Log Message:
  ---
  Merge branch 'nix-build-c++'


Compare: https://github.com/NixOS/nix/compare/dfe093861489...87b189c2b326___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nix] 591242: nix-channel: implement in c++

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nix
  Commit: 59124228b3ac6120e73bc6a88b2c633a70bdf0fc
  
https://github.com/NixOS/nix/commit/59124228b3ac6120e73bc6a88b2c633a70bdf0fc
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-11 (Thu, 11 Aug 2016)

  Changed paths:
M .gitignore
M Makefile
M scripts/local.mk
R scripts/nix-channel.in
M src/libstore/download.cc
M src/libstore/download.hh
A src/nix-channel/local.mk
A src/nix-channel/nix-channel.cc

  Log Message:
  ---
  nix-channel: implement in c++


  Commit: 572aba284a161cb94532cec297785266ee719b99
  
https://github.com/NixOS/nix/commit/572aba284a161cb94532cec297785266ee719b99
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-31 (Wed, 31 Aug 2016)

  Changed paths:
M .gitignore
M Makefile
M scripts/local.mk
R scripts/nix-channel.in
M src/libstore/download.cc
M src/libstore/download.hh
A src/nix-channel/local.mk
A src/nix-channel/nix-channel.cc

  Log Message:
  ---
  Merge branch 'nix-channel-c++'


  Commit: dfe09386148901e4d9f2dc84641d2d5544c886f7
  
https://github.com/NixOS/nix/commit/dfe09386148901e4d9f2dc84641d2d5544c886f7
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-31 (Wed, 31 Aug 2016)

  Changed paths:
M src/libstore/download.cc
M src/libstore/download.hh
M src/nix-channel/nix-channel.cc

  Log Message:
  ---
  download.hh: Fix conflicts from nix-channel-c++ merge


Compare: https://github.com/NixOS/nix/compare/aa1ea0d1e472...dfe093861489___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Unwanted, unannounced reboot

[Shea Levy]

The chromium messages are probably unrelated, they happen all the time
here too (due to some sandboxing issue I think, plus over noisy audit
subsystem)

Sergiu Ivanov  writes:

> [ Unknown signature status ]
>
> Hello Matthias,
>
> Thus quoth  Matthias Beyer  at 14:31 on Di, Aug 30 2016:
>>
>> this is the third time I got a unwanted, unannounced reboot of my 
>> Thinkpad X220. The device just went off and rebooted.
> [...]
>> Aug 30 13:16:23 yuu kernel: audit: type=1326 
>> audit(1472555783.141:55628): auid=1000 uid=1000 gid=100 ses=1 pid=27538 
>> comm="chromium" 
>> exe="/nix/store/28b56yiqshs8kvnha23vvwp0m4rlyyis-chromium-52.0.2743.116/libexec/chromium/chro
>> -- Reboot --
> [...]
>
> Just a wild guess: there's lots of chromium-related messages in your
> logs.  Do you happen to know if the reboots happen when you are _not_
> running chromimum?
>
> -- 
> Sergiu
> ___
> 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

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

Hi Roger,

The date is at the top of the page ("This evaluation was performed on
2016-08-29 12:11:27")

~Shea

Roger Qiu <roger@matrix.ai> writes:

> It would be useful if those revision hashes were paired with a date.
>
>
> On 30/08/2016 7:34 PM, Shea Levy wrote:
>> Hi Stewart,
>>
>> If you go to
>> http://hydra.nixos.org/job/nixos/release-16.03/nixpkgs.rustUnstable.rustc.x86_64-linux/latest/eval#tabs-inputs,
>> you can see the nixpkgs revision of the latest successful build of
>> rustUnstable. If you ensure that your nixpkgs is not later then that,
>> you should always get binaries. If you don't, please report back with
>> your nixpkgs.config.
>>
>> ~Shea
>>
>> stewart mackenzie <setor...@gmail.com> writes:
>>
>>> I just want this issue resolved.
>>>
>>> Every time I update / upgrade I recompile rustBeta then rustUnstable
>>> and it results in 1/2 day lost. This has happened frequently, recently
>>> as rustUnstable and rustBeta have been broken for a long time.
>>> (ie days have been lost finding working revs then compiling rust)
>>>
>>> If the lowprio removal doesn't solve this then how can I get it such
>>> that when I issue a `nixos-rebuild --upgrade switch` and my
>>> configuration.nix contains `rustUnstable.rustc`  downloads these
>>> binaries 
>>> http://hydra.nixos.org/job/nixos/release-16.03/nixpkgs.rustUnstable.rustc.x86_64-linux.
>>>
>>> What exactly does lowprio do?
>>>
>>>
>>> ___
>>> nix-dev mailing list
>>> nix-dev@lists.science.uu.nl
>>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
> -- 
> Founder of Matrix AI
> https://matrix.ai/
> +61420925975
>
> ___
> 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-commits] [NixOS/nixpkgs] d4e012: rust{Beta, Unstable}: Remove lowPrio calls

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: d4e012780f7eee93f7600d5273edde7470f20c87
  
https://github.com/NixOS/nixpkgs/commit/d4e012780f7eee93f7600d5273edde7470f20c87
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-30 (Tue, 30 Aug 2016)

  Changed paths:
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  rust{Beta,Unstable}: Remove lowPrio calls

These are sets of derivations and there is no recurseIntoAttrs, so the
packages aren't exposed to nix-env by name at all.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

Hi Stewart,

stewart mackenzie <setor...@gmail.com> writes:

> On Tue, Aug 30, 2016 at 8:02 AM, Shea Levy <s...@shealevy.com> wrote:
>> globin missed the fact that the naming convention is messing up the
>> lowPrio logic, and your original PR had nothing to do with that. If rust
>> were named properly, your fix would be wrong.
>
> What is the exact naming scheme that rust should adopt?
>

That is what the other ml thread is about, to decide if indeed it should
be changed. If so I can change it, but essentially the -beta/-unstable
identifier should come *after* the version number/date, not before.

>
> I will make a pull request to fix this.
>
>> Even in this case where
>> your fix is harmless (which globin reasonably missed), it doesn't
>> actually fix your issue and in the event that the rust naming is fixed
>> it would be harmful then.
>
> Secondly, I want to test this harmful aspect. What is the expected
> harmful behaviour if I follow the steps to reproduce i.e.: correctly
> name each rust and remove lowprio?

Sure, check out this patch: http://sprunge.us/fieF

With that applied to nixpkgs, nix-env -f /path/to/nixpkgs -i rustc
--dry-run will choose rustc-1.11.0. However, if you remove the "lowPrio"
From the definition of rustcUnstable, then it will choose
rustc-1.13.0-master-g308824a.

It turns out due to the nested nature of rustUnstable and rustBeta in
nixpkgs, the lowPrio doesn't matter, as those packages aren't exposed to
nix-env by name at all. So I will remove that.

~Shea


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

Hi Stewart,

If you go to
http://hydra.nixos.org/job/nixos/release-16.03/nixpkgs.rustUnstable.rustc.x86_64-linux/latest/eval#tabs-inputs,
you can see the nixpkgs revision of the latest successful build of
rustUnstable. If you ensure that your nixpkgs is not later then that,
you should always get binaries. If you don't, please report back with
your nixpkgs.config.

~Shea

stewart mackenzie  writes:

> I just want this issue resolved.
>
> Every time I update / upgrade I recompile rustBeta then rustUnstable
> and it results in 1/2 day lost. This has happened frequently, recently
> as rustUnstable and rustBeta have been broken for a long time.
> (ie days have been lost finding working revs then compiling rust)
>
> If the lowprio removal doesn't solve this then how can I get it such
> that when I issue a `nixos-rebuild --upgrade switch` and my
> configuration.nix contains `rustUnstable.rustc`  downloads these
> binaries 
> http://hydra.nixos.org/job/nixos/release-16.03/nixpkgs.rustUnstable.rustc.x86_64-linux.
>
> What exactly does lowprio do?


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

IMO proposals that affect the entire community should at least be
mentioned on the ML, as the nixpkgs tracker is way too noisy for many of
us to follow all issues opened there.

obadz  writes:

> For what it's worth there's an issue about adopting C4 (and other related
> proposals). So far none have really achieved consensus but this is probably
> where the conversation (if we can call it that) should continue:
> https://github.com/NixOS/nixpkgs/issues/17407#issuecomment-236450392
>
> lowPrio's code is here
> https://github.com/NixOS/nixpkgs/blob/master/lib/meta.nix#L45-L48
> Various packages can have the same "name" field in the top-level. lowPrio
> says, «if someone tries to install something with that name, and there are
> others available, prefer one of the others»
> Personally, I prefer to use nix-env -iA so that there is no ambiguity.
> (attribute set keys are guaranteed unique or you'll get an eval error).
>
> On Tue, Aug 30, 2016 at 1:11 AM, stewart mackenzie 
> wrote:
>
>> I just want this issue resolved.
>>
>> Every time I update / upgrade I recompile rustBeta then rustUnstable
>> and it results in 1/2 day lost. This has happened frequently, recently
>> as rustUnstable and rustBeta have been broken for a long time.
>> (ie days have been lost finding working revs then compiling rust)
>>
>> If the lowprio removal doesn't solve this then how can I get it such
>> that when I issue a `nixos-rebuild --upgrade switch` and my
>> configuration.nix contains `rustUnstable.rustc`  downloads these
>> binaries http://hydra.nixos.org/job/nixos/release-16.03/nixpkgs.
>> rustUnstable.rustc.x86_64-linux.
>>
>> What exactly does lowprio do?
>> ___
>> 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] Including "beta" or "unstable" identifiers in package names?

[Shea Levy]

Hi all,

Apparently some of our packages where we have multiple versions, like
rust, have identifiers like '-beta' or '-master' appended to their names
before their versions. IMO the 'beta' and 'master' is part of the
version, not the package name, and so if it exists at all it should be
part of the version string; should we change those packages?

Cheers,
Shea


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

Alright, I'm done. If someone can come up with a real argument for this
change, I'll be happy to review it then.

stewart mackenzie  writes:

> 1+1=2


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

As globin pointed out, the lowPrio has nothing to do with
hydra. Instead, it makes it so nix-env does not consider the package by
default during install. It happens in this case that the beta and
unstable versions of rust have -beta and -unstable in their names, so
nix-env considers them separately, but anyway this PR does not achieve
what you want. In fact currently the lowPrio is doing nothing due to
that naming convention (which IMO should be changed), but removing it
will not affect hydra.

stewart mackenzie  writes:

>> adversely affect nix-env users in that case.
>
> How?


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

OK, this is a specific problem you have: it's hard to get a simple pull
request into nixpkgs. If that's the case, how does C4 help fix it? And
at what cost, if any?

By the way, I agree with the closing of the PR you linked to earlier,
removing the lowPrio has nothing to do with the hydra build and will
adversely affect nix-env users in that case.

stewart mackenzie  writes:

> Why is it like pulling teeth getting a simple pull request into nixpkgs?
>
> Something is _very_very_ broken people.
>
> Can we please fix this asap? No I don't want to hear bullshit reasons
> about keeping X Y Z maintainer's powers.


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

Let me clarify: Why do those rules specifically help achieve those
goals? As I said, the goals are very high level and the rules very
specific.

stewart mackenzie  writes:

> in the beginning Shea... where it says "Goals"


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

I have no idea what you mean by "backtrack". All I see in that link is a
list of very high level goals and very specific rules. If the rules are
justified somewhere in there, I missed it in my quick glance over. Where
should I look for the specific justification?

stewart mackenzie <setor...@gmail.com> writes:

> On Tue, Aug 30, 2016 at 7:36 AM, Shea Levy <s...@shealevy.com> wrote:
>> Perhaps they are not random if you know their origin or justification,
>> neither is given at the link though.
>
> Backtrack? Are you kidding me?


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

Perhaps they are not random if you know their origin or justification,
neither is given at the link though.

stewart mackenzie  writes:

> Sigh, random rules? Are you kidding me?
>
> Nevermind


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

If that thread represents the argument for C4, then I vote no.

stewart mackenzie  writes:

> due to multiple causes, but the latest straw on the camel's back is
> this pull request: https://github.com/NixOS/nixpkgs/pull/18101


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

This is a bunch of legalese with a lot of random rules not justified in
the link. Why should we care? What problem does it solve? What problems
might it introduce?

stewart mackenzie  writes:

> http://rfc.zeromq.org/spec:42/C4/


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

[Shea Levy]

What does this mean?

stewart mackenzie  writes:

> Dear Nixers,
>
> Please may we start a C4 adoption period of 6 months then do a review
> after this?
>
> Kind regards
> Stewart
> ___
> 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-commits] [NixOS/nix] 9fa217: callFunction: Copy functors to the heap

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nix
  Commit: 9fa21765e7f267efcc65e1aa6ab21402ea6125ad
  
https://github.com/NixOS/nix/commit/9fa21765e7f267efcc65e1aa6ab21402ea6125ad
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-29 (Mon, 29 Aug 2016)

  Changed paths:
M src/libexpr/eval.cc

  Log Message:
  ---
  callFunction: Copy functors to the heap

Normally it's impossible to take a reference to the function passed to
callFunction, so some callers (e.g. ExprApp::eval) allocate that value
on the stack. For functors, a reference to the functor itself may be
kept, so we need to have it on the heap.

Fixes #1045


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nix] dea9de: callFunction: Copy functors to the heap

[Shea Levy]

  Branch: refs/heads/1.11-maintenance
  Home:   https://github.com/NixOS/nix
  Commit: dea9de79b7d508a9f5ac5d270d97f3b5e248056d
  
https://github.com/NixOS/nix/commit/dea9de79b7d508a9f5ac5d270d97f3b5e248056d
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-29 (Mon, 29 Aug 2016)

  Changed paths:
M src/libexpr/eval.cc

  Log Message:
  ---
  callFunction: Copy functors to the heap

Normally it's impossible to take a reference to the function passed to
callFunction, so some callers (e.g. ExprApp::eval) allocate that value
on the stack. For functors, a reference to the functor itself may be
kept, so we need to have it on the heap.

Fixes #1045

(cherry picked from commit 9fa21765e7f267efcc65e1aa6ab21402ea6125ad)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] f16803: haskellPackages.unbound: 0.5.0 -> 0.5.1

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: f168030af1ec67f5f856b8fe51759fa6e6dfd883
  
https://github.com/NixOS/nixpkgs/commit/f168030af1ec67f5f856b8fe51759fa6e6dfd883
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-27 (Sat, 27 Aug 2016)

  Changed paths:
M pkgs/development/haskell-modules/hackage-packages.nix

  Log Message:
  ---
  haskellPackages.unbound: 0.5.0 -> 0.5.1


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 2b1fa9: Add initial patches for CPU Controller on Control ...

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 2b1fa9da8b1896bbc877d110b459c3fb2c8fd2cd
  
https://github.com/NixOS/nixpkgs/commit/2b1fa9da8b1896bbc877d110b459c3fb2c8fd2cd
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-25 (Thu, 25 Aug 2016)

  Changed paths:
A pkgs/os-specific/linux/kernel/cpu-cgroup-v2-patches/4.4.patch
A pkgs/os-specific/linux/kernel/cpu-cgroup-v2-patches/4.6.patch
A pkgs/os-specific/linux/kernel/cpu-cgroup-v2-patches/4.7.patch
A pkgs/os-specific/linux/kernel/cpu-cgroup-v2-patches/README.md
A pkgs/os-specific/linux/kernel/cpu-cgroup-v2-patches/default.nix
M pkgs/os-specific/linux/kernel/patches.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Add initial patches for CPU Controller on Control Group v2


  Commit: c32ab50e0f1e670fb72998b2929009e5580649d1
  
https://github.com/NixOS/nixpkgs/commit/c32ab50e0f1e670fb72998b2929009e5580649d1
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-26 (Fri, 26 Aug 2016)

  Changed paths:
A pkgs/os-specific/linux/kernel/cpu-cgroup-v2-patches/4.4.patch
A pkgs/os-specific/linux/kernel/cpu-cgroup-v2-patches/4.6.patch
A pkgs/os-specific/linux/kernel/cpu-cgroup-v2-patches/4.7.patch
A pkgs/os-specific/linux/kernel/cpu-cgroup-v2-patches/README.md
A pkgs/os-specific/linux/kernel/cpu-cgroup-v2-patches/default.nix
M pkgs/os-specific/linux/kernel/patches.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Merge branch 'cpu-cgroup-v2'


Compare: https://github.com/NixOS/nixpkgs/compare/9d22624eb064...c32ab50e0f1e___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nix] 2ac966: Bump version to 1.11.3

[Shea Levy]

  Branch: refs/heads/1.11-maintenance
  Home:   https://github.com/NixOS/nix
  Commit: 2ac966a464a830f52a9101c0a9d65f6a95cbfa0e
  
https://github.com/NixOS/nix/commit/2ac966a464a830f52a9101c0a9d65f6a95cbfa0e
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-22 (Mon, 22 Aug 2016)

  Changed paths:
M version

  Log Message:
  ---
  Bump version to 1.11.3


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nix] 2ac966: Bump version to 1.11.3

[Shea Levy]

  Branch: refs/tags/1.11.3
  Home:   https://github.com/NixOS/nix
  Commit: 2ac966a464a830f52a9101c0a9d65f6a95cbfa0e
  
https://github.com/NixOS/nix/commit/2ac966a464a830f52a9101c0a9d65f6a95cbfa0e
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-22 (Mon, 22 Aug 2016)

  Changed paths:
M version

  Log Message:
  ---
  Bump version to 1.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] 88949e: diffutils: 3.3 -> 3.5

[Shea Levy]

  Branch: refs/heads/staging
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 88949e6d134c023f545e7f3324a70aa5327e68de
  
https://github.com/NixOS/nixpkgs/commit/88949e6d134c023f545e7f3324a70aa5327e68de
  Author: Lancelot SIX <l...@lancelotsix.com>
  Date:   2016-08-21 (Sun, 21 Aug 2016)

  Changed paths:
M pkgs/tools/text/diffutils/default.nix

  Log Message:
  ---
  diffutils: 3.3 -> 3.5

Releases announcements:
3.4: http://lists.gnu.org/archive/html/info-gnu/2016-08/msg4.html
3.5: http://lists.gnu.org/archive/html/info-gnu/2016-08/msg00010.html


  Commit: ed20bbc8fb8048d35ad676c37f50628c9076ac93
  
https://github.com/NixOS/nixpkgs/commit/ed20bbc8fb8048d35ad676c37f50628c9076ac93
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-22 (Mon, 22 Aug 2016)

  Changed paths:
M pkgs/tools/text/diffutils/default.nix

  Log Message:
  ---
  Merge branch 'update_diffutils-3.5' of git://github.com/lancelotsix/nixpkgs 
into staging


Compare: https://github.com/NixOS/nixpkgs/compare/24a9183f907c...ed20bbc8fb80___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 2e1fa4: fftw: fix on darwin

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 2e1fa4a9f5f8b43a8f569aec3cb35aaf07ea7fba
  
https://github.com/NixOS/nixpkgs/commit/2e1fa4a9f5f8b43a8f569aec3cb35aaf07ea7fba
  Author: Anthony Cowley <acow...@gmail.com>
  Date:   2016-08-21 (Sun, 21 Aug 2016)

  Changed paths:
M pkgs/development/libraries/fftw/default.nix

  Log Message:
  ---
  fftw: fix on darwin

doc generation involves running Fortran wrapper generation shell scripts
that hard code references to gcc which fails on darwin.


  Commit: 1b15f1df5fc4b42d01731f2920f9dfdcc935607a
  
https://github.com/NixOS/nixpkgs/commit/1b15f1df5fc4b42d01731f2920f9dfdcc935607a
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-21 (Sun, 21 Aug 2016)

  Changed paths:
M pkgs/development/libraries/fftw/default.nix

  Log Message:
  ---
  Merge branch 'fftw' of git://github.com/acowley/nixpkgs


Compare: https://github.com/NixOS/nixpkgs/compare/175028582c55...1b15f1df5fc4___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] b4954a: Deprecate --install-grub in favor of --install-boo...

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: b4954a8f3802ba545933905428a4288622f28294
  
https://github.com/NixOS/nixpkgs/commit/b4954a8f3802ba545933905428a4288622f28294
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-16 (Tue, 16 Aug 2016)

  Changed paths:
M nixos/doc/manual/man-nixos-rebuild.xml
M nixos/modules/installer/tools/nixos-install.sh
M nixos/modules/installer/tools/nixos-rebuild.sh
M nixos/modules/system/boot/loader/grub/install-grub.pl
M nixos/modules/system/boot/loader/systemd-boot/systemd-boot-builder.py

  Log Message:
  ---
  Deprecate --install-grub in favor of --install-bootloader for nixos-rebuild.

Fixes #14293


  Commit: 2942895d552c30033d902553566a06334264d3e2
  
https://github.com/NixOS/nixpkgs/commit/2942895d552c30033d902553566a06334264d3e2
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-17 (Wed, 17 Aug 2016)

  Changed paths:
M nixos/doc/manual/man-nixos-rebuild.xml
M nixos/modules/installer/tools/nixos-install.sh
M nixos/modules/installer/tools/nixos-rebuild.sh
M nixos/modules/system/boot/loader/grub/install-grub.pl
M nixos/modules/system/boot/loader/systemd-boot/systemd-boot-builder.py

  Log Message:
  ---
  Merge branch 'install-bootloader-flag'


Compare: https://github.com/NixOS/nixpkgs/compare/3367c211c684...2942895d552c___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 9adad8: Revert "Merge branch 'modprobe-fix' of git://githu...

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 9adad8612b082bcbae30c81678a04b79a44079a4
  
https://github.com/NixOS/nixpkgs/commit/9adad8612b082bcbae30c81678a04b79a44079a4
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-15 (Mon, 15 Aug 2016)

  Changed paths:
M nixos/modules/config/zram.nix
M nixos/modules/hardware/video/bumblebee.nix
M nixos/modules/hardware/video/webcam/facetimehd.nix
M nixos/modules/services/hardware/tlp.nix
M nixos/modules/services/hardware/udev.nix
M nixos/modules/services/network-filesystems/openafs-client/default.nix
M nixos/modules/services/networking/fan.nix
M nixos/modules/services/networking/strongswan.nix
M nixos/modules/system/boot/kernel.nix
M nixos/modules/system/boot/modprobe.nix
M nixos/modules/system/boot/stage-2-init.sh
M nixos/modules/tasks/cpu-freq.nix
M nixos/modules/virtualisation/docker.nix
M nixos/modules/virtualisation/qemu-vm.nix
M pkgs/development/libraries/fftw/default.nix
M pkgs/development/libraries/libdrm/default.nix
M pkgs/development/libraries/mesa/default.nix
M pkgs/development/python-modules/generic/run_setup.py
M pkgs/development/tools/misc/lttng-tools/default.nix
M pkgs/os-specific/darwin/apple-source-releases/Libc/default.nix
M pkgs/os-specific/darwin/apple-source-releases/Libsystem/default.nix
M pkgs/os-specific/darwin/apple-source-releases/configd/default.nix
M pkgs/os-specific/darwin/apple-source-releases/default.nix
M pkgs/os-specific/darwin/apple-source-releases/libpthread/default.nix
M pkgs/os-specific/darwin/apple-source-releases/xnu/default.nix
R pkgs/os-specific/darwin/swift-corefoundation/default.nix
M pkgs/os-specific/linux/kernel/manual-config.nix
M pkgs/os-specific/linux/kmod/aggregator.nix
M pkgs/os-specific/linux/kmod/default.nix
M pkgs/os-specific/linux/kmod/module-dir.patch
M pkgs/stdenv/darwin/make-bootstrap-tools.nix
M pkgs/tools/networking/network-manager/0.9.8/default.nix
M pkgs/tools/networking/network-manager/0.9.8/nixos-purity.patch
M pkgs/tools/networking/network-manager/default.nix
M pkgs/tools/networking/network-manager/openconnect.nix
M pkgs/tools/networking/network-manager/openvpn.nix
M pkgs/tools/networking/network-manager/vpnc.nix
M pkgs/tools/text/diffutils/default.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Revert "Merge branch 'modprobe-fix' of git://github.com/abbradar/nixpkgs"

Was meant to go into staging, sorry

This reverts commit 57b2d1e9b0dcdd1d25bd2d450174764b9417ffc1, reversing
changes made to 760b2b9048ea775c319cb348d74447a20dea513e.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] b25aeb: fftw: 3.3.4 -> 3.3.5

[Shea Levy]

default.nix
M pkgs/tools/bluetooth/blueman/default.nix
M pkgs/tools/filesystems/bcache-tools/default.nix
M pkgs/tools/graphics/imgurbash2/default.nix
M pkgs/tools/misc/debian-devscripts/default.nix
M pkgs/tools/misc/grub4dos/default.nix
M pkgs/tools/misc/svtplay-dl/default.nix
M pkgs/tools/networking/logmein-hamachi/default.nix
M pkgs/tools/networking/network-manager/default.nix
M pkgs/tools/networking/openvpn/update-resolv-conf.nix
M pkgs/tools/networking/wicd/default.nix
M pkgs/tools/security/fail2ban/default.nix
M pkgs/tools/security/gnupg/21.nix
M pkgs/tools/security/knockknock/default.nix
M pkgs/tools/security/nmap/default.nix
M pkgs/tools/security/volatility/default.nix
M pkgs/tools/typesetting/tex/texlive-new/pkgs.nix
M pkgs/tools/video/mjpegtools/default.nix
M pkgs/top-level/aliases.nix
M pkgs/top-level/all-packages.nix
M pkgs/top-level/python-packages.nix

  Log Message:
  ---
  Merge branch 'master' into staging


  Commit: 131fca0a85c6a2f7912061f8f3e57f582fb94f38
  
https://github.com/NixOS/nixpkgs/commit/131fca0a85c6a2f7912061f8f3e57f582fb94f38
  Author: Nikolay Amiantov <a...@fmap.me>
  Date:   2016-08-16 (Tue, 16 Aug 2016)

  Changed paths:
M pkgs/os-specific/linux/kmod/default.nix
M pkgs/os-specific/linux/kmod/module-dir.patch

  Log Message:
  ---
  kmod: add patch to allow searching for modules in several directories


  Commit: 1afd2506768760a6a55d23c47dc064f732f27807
  
https://github.com/NixOS/nixpkgs/commit/1afd2506768760a6a55d23c47dc064f732f27807
  Author: Nikolay Amiantov <a...@fmap.me>
  Date:   2016-08-16 (Tue, 16 Aug 2016)

  Changed paths:
M nixos/modules/services/network-filesystems/openafs-client/default.nix
M nixos/modules/virtualisation/qemu-vm.nix
M pkgs/development/tools/misc/lttng-tools/default.nix
M pkgs/os-specific/linux/kernel/manual-config.nix
M pkgs/os-specific/linux/kmod/aggregator.nix
M pkgs/tools/networking/network-manager/default.nix
M pkgs/tools/networking/network-manager/openconnect.nix
M pkgs/tools/networking/network-manager/openvpn.nix
M pkgs/tools/networking/network-manager/vpnc.nix

  Log Message:
  ---
  treewide: replace several /sbin paths by /bin


  Commit: b2ebecd9e50471ec967ab9cdb2aba793d75cb747
  
https://github.com/NixOS/nixpkgs/commit/b2ebecd9e50471ec967ab9cdb2aba793d75cb747
  Author: Nikolay Amiantov <a...@fmap.me>
  Date:   2016-08-16 (Tue, 16 Aug 2016)

  Changed paths:
M nixos/modules/config/zram.nix
M nixos/modules/services/hardware/udev.nix
M nixos/modules/services/networking/fan.nix
M nixos/modules/services/networking/strongswan.nix
M nixos/modules/system/boot/modprobe.nix
M nixos/modules/tasks/cpu-freq.nix
M nixos/modules/virtualisation/docker.nix

  Log Message:
  ---
  modprobe service: drop kmod wrapper


  Commit: 1f639587729daf6c34535addbc35fd6e5c816ffc
  
https://github.com/NixOS/nixpkgs/commit/1f639587729daf6c34535addbc35fd6e5c816ffc
  Author: Nikolay Amiantov <a...@fmap.me>
  Date:   2016-08-16 (Tue, 16 Aug 2016)

  Changed paths:
M nixos/modules/hardware/video/bumblebee.nix
M nixos/modules/hardware/video/webcam/facetimehd.nix
M nixos/modules/services/hardware/tlp.nix
M nixos/modules/services/hardware/udev.nix
M nixos/modules/system/boot/kernel.nix
M nixos/modules/system/boot/modprobe.nix
M nixos/modules/system/boot/stage-2-init.sh
M nixos/modules/virtualisation/docker.nix

  Log Message:
  ---
  nixos treewide: don't set MODULE_DIR


  Commit: cd05a8ed000a48a617f3fd061c2837774f4e8c66
  
https://github.com/NixOS/nixpkgs/commit/cd05a8ed000a48a617f3fd061c2837774f4e8c66
  Author: Nikolay Amiantov <a...@fmap.me>
  Date:   2016-08-16 (Tue, 16 Aug 2016)

  Changed paths:
M pkgs/tools/networking/network-manager/default.nix

  Log Message:
  ---
  networkmanager: point to kmod's modprobe


  Commit: b067b5301104c7d09d86d69febaa423a49ce14c0
  
https://github.com/NixOS/nixpkgs/commit/b067b5301104c7d09d86d69febaa423a49ce14c0
  Author: Nikolay Amiantov <a...@fmap.me>
  Date:   2016-08-16 (Tue, 16 Aug 2016)

  Changed paths:
M pkgs/tools/networking/network-manager/0.9.8/default.nix
M pkgs/tools/networking/network-manager/0.9.8/nixos-purity.patch

  Log Message:
  ---
  networkmanager098: fix binary paths


  Commit: 57b2d1e9b0dcdd1d25bd2d450174764b9417ffc1
  
https://github.com/NixOS/nixpkgs/commit/57b2d1e9b0dcdd1d25bd2d450174764b9417ffc1
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-15 (Mon, 15 Aug 2016)

  Changed paths:
M nixos/modules/config/zram.nix
M nixos/modules/hardware/video/bumblebee.nix
M nixos/modules/hardware/video/webcam/facetimehd.nix
M nixos/modules/services/hardware/tlp.nix
M nixos/modules/services/hardware/udev.nix
M nixos/modules/services/network-filesystems/openafs-clien

[Nix-commits] [NixOS/nix] 7bb4d0: builtins.fetch{url, tarball}: Allow name attribute

[Shea Levy]

  Branch: refs/heads/1.11-maintenance
  Home:   https://github.com/NixOS/nix
  Commit: 7bb4d028a86b61ffa7cbd77b0937156ceca8af69
  
https://github.com/NixOS/nix/commit/7bb4d028a86b61ffa7cbd77b0937156ceca8af69
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-15 (Mon, 15 Aug 2016)

  Changed paths:
M src/libexpr/primops.cc
M src/libstore/download.cc
M src/libstore/download.hh

  Log Message:
  ---
  builtins.fetch{url,tarball}: Allow name attribute

(cherry picked from commit d52d391164d9a6fb4a2efec2777e24de5e19b225)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nix] d52d39: builtins.fetch{url, tarball}: Allow name attribute

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nix
  Commit: d52d391164d9a6fb4a2efec2777e24de5e19b225
  
https://github.com/NixOS/nix/commit/d52d391164d9a6fb4a2efec2777e24de5e19b225
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-15 (Mon, 15 Aug 2016)

  Changed paths:
M src/libexpr/primops.cc
M src/libstore/download.cc
M src/libstore/download.hh

  Log Message:
  ---
  builtins.fetch{url,tarball}: Allow name attribute


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 990637: long-shebang: 1.0.1 -> 1.1.0

[Shea Levy]

  Branch: refs/heads/release-16.03
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 9906378e77e6667ea90cc9363b3b9500bf5693b0
  
https://github.com/NixOS/nixpkgs/commit/9906378e77e6667ea90cc9363b3b9500bf5693b0
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-14 (Sun, 14 Aug 2016)

  Changed paths:
M pkgs/misc/long-shebang/default.nix

  Log Message:
  ---
  long-shebang: 1.0.1 -> 1.1.0

(cherry picked from commit 7069047f2ed6548910f3f2bff4a23946a363e860)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 706904: long-shebang: 1.0.1 -> 1.1.0

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 7069047f2ed6548910f3f2bff4a23946a363e860
  
https://github.com/NixOS/nixpkgs/commit/7069047f2ed6548910f3f2bff4a23946a363e860
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-14 (Sun, 14 Aug 2016)

  Changed paths:
M pkgs/misc/long-shebang/default.nix

  Log Message:
  ---
  long-shebang: 1.0.1 -> 1.1.0


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 670801: long-shebang: 1.0.0 -> 1.0.1

[Shea Levy]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 670801a56ac15b1c23f0626833c3030a7490b616
  
https://github.com/NixOS/nixpkgs/commit/670801a56ac15b1c23f0626833c3030a7490b616
  Author: Shea Levy <s...@shealevy.com>
  Date:   2016-08-14 (Sun, 14 Aug 2016)

  Changed paths:
M pkgs/misc/long-shebang/default.nix

  Log Message:
  ---
  long-shebang: 1.0.0 -> 1.0.1


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits