Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 5f34b5476b8132b5eee7873f2cc4777843bc4f85
https://github.com/NixOS/nixpkgs/commit/5f34b5476b8132b5eee7873f2cc4777843bc4f85
Author: Rok Garbas
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
M pkg
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 4c96860b5380e0ccb4df2b280286946416505c22
https://github.com/NixOS/nixpkgs/commit/4c96860b5380e0ccb4df2b280286946416505c22
Author: Rok Garbas
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
M pkg
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 511565e996ff4eac7dc114eb39d6f81dba0e50bb
https://github.com/NixOS/nixpkgs/commit/511565e996ff4eac7dc114eb39d6f81dba0e50bb
Author: Rickard Nilsson
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
Hi Everyone,
I performed a nixos-rebuild switch --upgrade and after rebooting, was
not able to see my usual KDE session. There was no X session. I
selected a previous generation in gummiboot and was able to have my
KDE session back. What can I do about the upgraded components which
did not work? I
Naa time critical nature, just decided to spin up an ubuntu virtualbox.
Ah I recognize the email address from the code you wrote :-)
It would seem it's very centered around deploying stock releases not
amenable for developing on wordpress. But I didn't get that far.
Is there a faster route?
On
On 06.06.2016 10:51, Nicolas Petton wrote:
> hi,
>
> I'm trying to properly install rails on nixos. I'm not interested in
> packaging an existing rails app, but rather to do rails development.
>
> I guess using rubygems is not the nixos way (and installing the rails
> gem globally won't work any
On 09.06.2016 12:06, stewart mackenzie wrote:
> Ah I see this: https://nixos.org/wiki/Wordpress
>
> I'll need to override the src of wordpress with my own version of wordpress.
>
got it working?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: c1cb5ca57e4b067afaa13fd93ed1392ec84c9da2
https://github.com/NixOS/nixpkgs/commit/c1cb5ca57e4b067afaa13fd93ed1392ec84c9da2
Author: Joachim Fasting
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: f8a0f1ce686674fc53830e2a1c61c40f53df4571
https://github.com/NixOS/nixpkgs/commit/f8a0f1ce686674fc53830e2a1c61c40f53df4571
Author: mimadrid
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M pkgs/
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 0e262f52f30143e9f6fdc171fee69075934604e3
https://github.com/NixOS/nixpkgs/commit/0e262f52f30143e9f6fdc171fee69075934604e3
Author: rushmorem
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M pkgs
n00b here
Trying to sort out PR: https://github.com/NixOS/nixpkgs/pull/15986
while "it works on my machine", travis barks out at me with:
https://travis-ci.org/NixOS/nixpkgs/builds/135414974
so I looked into the travis builds to find out what they were doing, and
come up with this to replicate t
Peter Simons writes:
> Hi Anthony,
>
> >> [What is] a concrete use case that works for you today but that
> >> won't work after LTS-4 has been dropped?
> >
> > Someone who has a project that works with package versions in LTS-4,
> > but hasn't yet been upgraded to LTS-5 or 6. They can simply
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 7bd515979c59fa2b5786fba2fddbca9d56c04cb1
https://github.com/NixOS/nixpkgs/commit/7bd515979c59fa2b5786fba2fddbca9d56c04cb1
Author: Joachim Fasting
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
Hi Anthony,
>> [What is] a concrete use case that works for you today but that
>> won't work after LTS-4 has been dropped?
>
> Someone who has a project that works with package versions in LTS-4,
> but hasn't yet been upgraded to LTS-5 or 6. They can simply refer to
> LTS-4 in their shell.ni
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 58599744ee9673d309d5e4d8415077c242545e8d
https://github.com/NixOS/nixpkgs/commit/58599744ee9673d309d5e4d8415077c242545e8d
Author: Jonathan Lange
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: d77e65360ea0e5d5c3bdebf5f0c7f24204303053
https://github.com/NixOS/nixpkgs/commit/d77e65360ea0e5d5c3bdebf5f0c7f24204303053
Author: taku0
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M p
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: cf042ae750a9fe911addd6ffddea2c8c6fa45548
https://github.com/NixOS/nixpkgs/commit/cf042ae750a9fe911addd6ffddea2c8c6fa45548
Author: Peter Simons
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M p
Peter Simons writes:
> Hi Anthony,
>
> > I draw a distinction between newer minor versions obsoleting old ones
> > for purposes of bug fixes vs. for purposes of freezing packages.
>
> I am sorry, but I don't understand that distinction. In your original
> response you suggested that dropping ol
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 32ff5bbc3088ca9afff585898947ecf173ffb9a1
https://github.com/NixOS/nixpkgs/commit/32ff5bbc3088ca9afff585898947ecf173ffb9a1
Author: Nikolay Amiantov
Date: 2016-06-01 (Wed, 01 Jun 2016)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 97d791978cca24515409b53c9cc0cef28f972ea8
https://github.com/NixOS/nixpkgs/commit/97d791978cca24515409b53c9cc0cef28f972ea8
Author: Nikolay Amiantov
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
Hi Anthony,
> I draw a distinction between newer minor versions obsoleting old ones
> for purposes of bug fixes vs. for purposes of freezing packages.
I am sorry, but I don't understand that distinction. In your original
response you suggested that dropping old LTS major releases like LTS-4
fro
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 4959bd75db62589691112f871b070b81382092a8
https://github.com/NixOS/nixpkgs/commit/4959bd75db62589691112f871b070b81382092a8
Author: Vladimír Čunát
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths
Erik,
https://nixos.org/nixops/manual/#opt-deployment.keys
Deployment keys won't end up in nix store, I think they are deployed using
ssh just to /run/keys. They also will be removed after reboot as /run will
disappear, untill you set some other option.
Also there was a thread on this list few w
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: de842765bec692a5b1bf00063bc98406599d07b2
https://github.com/NixOS/nixpkgs/commit/de842765bec692a5b1bf00063bc98406599d07b2
Author: Thomas Tuegel
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M
Hi,
Due to a wrong manipulation when activating dir_index on my root
partition, I have now plenty of live orphaned paths in my store (about
5G) like this one:
|$ nix-store -q --referrers-closure
/nix/store/4zhkw0g564g3ljdpnn8j5krrsvcxildn-libXcomposite-0.4.4.tar.bz2
/nix/store/4zhkw0g564g3l
Hi Kevin,
Thanks for the extra info!
I was wondering though, if the generated config files do end up in
/nix/store anyway, does it even make a difference if I use the
deployment.keys method? Or is there another way to have eg. a php script
read from these keys without actually writing them out?
S
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 09d63127de6ed74be5947322f8af3b0c8b393374
https://github.com/NixOS/nixpkgs/commit/09d63127de6ed74be5947322f8af3b0c8b393374
Author: Thomas Tuegel
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M
Hi,
The status of Hydra job ‘nixpkgs:trunk:tarball’ (on x86_64-linux) has changed
from "Failed" to "Success". For details, see
https://hydra.nixos.org/build/36745433
This may be due to 3 commits by Franz Pletz or
Thomas Tuegel .
Yay!
Regards,
The Hydra build daemon.
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 45d4d6212274acd80cf2c6a8bcbca2ba1107d313
https://github.com/NixOS/nixpkgs/commit/45d4d6212274acd80cf2c6a8bcbca2ba1107d313
Author: Franz Pletz
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M pk
Peter Simons writes:
> Hi Anthony,
>
> > I know you didn't ask for feedback [...].
>
> I'm always happy to get feedback!
>
> > If the top priority is receiving bug fixes, then keeping an LTS-4,
> > LTS-5, LTS-6, etc. that tracks the most recent minor version makes
> > sense.
>
> You seem to b
On 09/06/16 11:03, 4levels wrote:
> Hi Kevin,
>
> I'm very curious how you setup sensitive information using deployment.keys
> This still seems like the best option to do this, but I failed to get
> it working..
>
> Could you be so kind to post a small example, showing how you define
> the keys and
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: bfa32800c3df6dd3a8e23bd239ec102173407249
https://github.com/NixOS/nixpkgs/commit/bfa32800c3df6dd3a8e23bd239ec102173407249
Author: Kamil Chmielewski
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
Hi Kevin,
I'm very curious how you setup sensitive information using deployment.keys
This still seems like the best option to do this, but I failed to get it
working..
Could you be so kind to post a small example, showing how you define the
keys and use them in functions that generate eg. a confi
Hi,
The status of Hydra job ‘nixpkgs:trunk:tarball’ (on x86_64-linux) has changed
from "Success" to "Failed". For details, see
https://hydra.nixos.org/build/36745160
This may be due to 5 commits by Joachim Fasting , Nikolay
Amiantov , Ryan Mulligan or Thomas Tuegel
.
Go forth and fix it.
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 4d2cf4baaccf093a63b7e76793bffdc339f2379d
https://github.com/NixOS/nixpkgs/commit/4d2cf4baaccf093a63b7e76793bffdc339f2379d
Author: Thomas Tuegel
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M
Hi Vladimir,
I was just reading strings.nix, removeSuffix seems indeed the best
candidate, thanks for confirming this!
Kind regards,
Erik aka 4levels
On Thu, Jun 9, 2016 at 4:32 PM Vladimír Čunát wrote:
> On 06/09/2016 04:24 PM, 4levels wrote:
> > 'd like to know if there's an easy way to str
On 06/09/2016 04:24 PM, 4levels wrote:
> 'd like to know if there's an easy way to strip off the trailing newline
> from a file read with builtins.readFile.
lib.removeSuffix "\n"
--Vladimir
smime.p7s
Description: S/MIME Cryptographic Signature
___
n
On 09/06/16 10:21, 4levels wrote:
> Hi Nix Devs,
>
> I've tried using the deployment.keys but that seems to be only there for
> user accounts and not for custom configurations. As I need multiple
> keys for each platform (eg. symfony, wordpress - cipher, key, database
> password, admin user passw
Hi Nix Devs,
In a related question to have my sensitive info separated from the normal
NixOps configuration files, I am reading the passwords, keys, ciphers, ...
from separate files (which are encrypted with git-crypt).
My IDE (webstorm) keeps adding a trailing newline when saving these files.
I
Hi Nix Devs,
I've tried using the deployment.keys but that seems to be only there for
user accounts and not for custom configurations. As I need multiple keys
for each platform (eg. symfony, wordpress - cipher, key, database password,
admin user password etc etc) it seems that deployment.keys wil
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: edc36a0091c61cc60d3607d5e73ad22e078f8307
https://github.com/NixOS/nixpkgs/commit/edc36a0091c61cc60d3607d5e73ad22e078f8307
Author: Joachim Fasting
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: b54fa1e351074531628178cd4da7dccc7c334824
https://github.com/NixOS/nixpkgs/commit/b54fa1e351074531628178cd4da7dccc7c334824
Author: Ryan Mulligan
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: f1d7572a5fb8f327ca74307fe9e2722008e774ca
https://github.com/NixOS/nixpkgs/commit/f1d7572a5fb8f327ca74307fe9e2722008e774ca
Author: Joachim Fasting
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed path
Hi Anthony,
> I know you didn't ask for feedback [...].
I'm always happy to get feedback!
> If the top priority is receiving bug fixes, then keeping an LTS-4,
> LTS-5, LTS-6, etc. that tracks the most recent minor version makes
> sense.
You seem to be saying that keeping an old major releas
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 8eb439701ef881260ab8a29326c4c266445f92a0
https://github.com/NixOS/nixpkgs/commit/8eb439701ef881260ab8a29326c4c266445f92a0
Author: Vladimír Čunát
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: f3ebf1376284629b3da9ed57774a31ae79a7ec53
https://github.com/NixOS/nixpkgs/commit/f3ebf1376284629b3da9ed57774a31ae79a7ec53
Author: Tim Steinbach
Date: 2016-06-07 (Tue, 07 Jun 2016)
Changed paths:
M
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: dd06c4e52bb54171237eca8c6f113f1d550c7c13
https://github.com/NixOS/nixpkgs/commit/dd06c4e52bb54171237eca8c6f113f1d550c7c13
Author: Rahul Gopinath
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: c860de987d5eb97a2c8d41e9e1a311c3cf988988
https://github.com/NixOS/nixpkgs/commit/c860de987d5eb97a2c8d41e9e1a311c3cf988988
Author: Rahul Gopinath
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 140e48f3c1986f8bb5820e9a9bef394b3908ac62
https://github.com/NixOS/nixpkgs/commit/140e48f3c1986f8bb5820e9a9bef394b3908ac62
Author: Andrew Kelley
Date: 2016-03-16 (Wed, 16 Mar 2016)
Changed paths:
A
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 4bc528ce280d3a2e65ee3937949f4b8793928615
https://github.com/NixOS/nixpkgs/commit/4bc528ce280d3a2e65ee3937949f4b8793928615
Author: Jinjing Wang
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M p
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 376ba5f17f81a33be8ee6db6b43bd2b08e5a2491
https://github.com/NixOS/nixpkgs/commit/376ba5f17f81a33be8ee6db6b43bd2b08e5a2491
Author: Joachim Fasting
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 3b28b5673b67670ee61212f2043ef641c7d70dc6
https://github.com/NixOS/nixpkgs/commit/3b28b5673b67670ee61212f2043ef641c7d70dc6
Author: José Romildo Malaquias
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed path
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 8f4755a0ae4d70577a62238f93ddf4849755212c
https://github.com/NixOS/nixpkgs/commit/8f4755a0ae4d70577a62238f93ddf4849755212c
Author: Tim Steinbach
Date: 2016-06-07 (Tue, 07 Jun 2016)
Changed paths:
M
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 35c544e6d4e685af7d3ef5cfc4294c094199e57f
https://github.com/NixOS/nixpkgs/commit/35c544e6d4e685af7d3ef5cfc4294c094199e57f
Author: Rahul Gopinath
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 31f4a9b5590fdef5412f13e16888d2fa94f6f5f7
https://github.com/NixOS/nixpkgs/commit/31f4a9b5590fdef5412f13e16888d2fa94f6f5f7
Author: obadz
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M pkgs/des
Ah I see this: https://nixos.org/wiki/Wordpress
I'll need to override the src of wordpress with my own version of wordpress.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Hi all,
thank you for your replies!
The thing is, I seem not to be able to merge at the level I need, at the
hostname level that is.
I mean, I need to have a file with the combined sets to be used by NixOps.
There is an mapAttrsRecursive function in attrsets.nix that sounds like it
does what I ne
Probably some function from
https://github.com/NixOS/nixpkgs/blob/master/lib/attrsets.nix could be
useful to merge them.
2016-06-09 11:19 GMT+01:00 zimbatm :
> @dario: that doesn’t work recursively. { a = { x = 3; } } // { a = { y =
> 4; } produces { a = { y = 4 }; }
>
>
> On Thu, 9 Jun 2016 at
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: cc174b3d556945eff999efe44ab18dd7b3e99f76
https://github.com/NixOS/nixpkgs/commit/cc174b3d556945eff999efe44ab18dd7b3e99f76
Author: Vladimír Čunát
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M
@dario: that doesn’t work recursively. { a = { x = 3; } } // { a = { y = 4;
} produces { a = { y = 4 }; }
On Thu, 9 Jun 2016 at 10:44 Dario Bertini wrote:
> {a=1;}// {b=2;}
> Yields
> {a=1; b=2;}
>
> Is this enough to help you?
>
> On 9 June 2016 10:31:07 BST, 4levels <4lev...@gmail.com> wrote
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 10c87e69b4ab04a499be1a54bca1b8548f657d63
https://github.com/NixOS/nixpkgs/commit/10c87e69b4ab04a499be1a54bca1b8548f657d63
Author: Maciek Starzyk
Date: 2016-06-08 (Wed, 08 Jun 2016)
Changed paths:
M
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 109096247a20ed1141f1f373cd41c1674027c7f1
https://github.com/NixOS/nixpkgs/commit/109096247a20ed1141f1f373cd41c1674027c7f1
Author: Eelco Dolstra
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 72b4009367257c2447aac89d5f34f2421bbc88dc
https://github.com/NixOS/nixpkgs/commit/72b4009367257c2447aac89d5f34f2421bbc88dc
Author: Eelco Dolstra
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
Hi,
I see there's a wordpress package:
https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/web-servers/apache-httpd/wordpress.nix
There are no available wordpress attributes.
How do I install wordpress?
Kind regards
Stewart
___
nix-dev
On 9 June 2016 at 08:54, 4levels <4lev...@gmail.com> wrote:
> ...
> I've modified my nixops deploy to have keys.nix loaded after the servers.nix
> and platforms.nix files, but I keep getting errors like "the attribute
> password does not exist"
What's the output of: 'nixops info' for your deploy
{a=1;}// {b=2;}
Yields
{a=1; b=2;}
Is this enough to help you?
On 9 June 2016 10:31:07 BST, 4levels <4lev...@gmail.com> wrote:
>Hi,
>
>thank you for your swift reply!
>I'd like to avoid to literally mention all sensitive config params in
>the
>network.nix config.
>
>What would be the "normal"
Hi Tomasz,
that is indeed the case: all these configuration values are being used to
generate different config files (for eg. a symfony project, or a wordpress
site, etc etc) and they do appear in /nix/store
I was not really aware of the security concerns here, but if
deployment.keys can be an at
I'm not 100% sure as I'm pretty new to nixops, but probably if you put
credentials like that, they can end up in /nix/store.
As someone explained to me before, probably the only good way at the moment
to do that is to use deployment.keys.
Can anyone confirm that?
2016-06-09 10:31 GMT+01:00 4level
Hi,
thank you for your swift reply!
I'd like to avoid to literally mention all sensitive config params in the
network.nix config.
What would be the "normal" procedure to recursively merge 2 attribute sets?
So if I have in one file
servers.nix: {
vm01 = {
services.symfony.platforms = {
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 51a7260fba63167bd17d58631fa0991029521841
https://github.com/NixOS/nixpkgs/commit/51a7260fba63167bd17d58631fa0991029521841
Author: Rahul Gopinath
Date: 2016-06-08 (Wed, 08 Jun 2016)
Changed paths:
A
Hi,
I don’t know where you are getting this error. All I can do is suggest a
workaround:
In keys.nix:
{
database_password = "12345678";
}
In network.nix:
let
secrets = import ./keys.nix {};in;
{
vm01 = {
{ config, pkgs, ... }:
{
services.symfony.platforms.database.password
It might make sense to create an external repo (nix-hackage?) with the
stackage releases and it's own release.nix. That way it can evolve
independently from nixpkgs and not clobber the main repo. It can also offer
it's own binary cache as a service to haskell developers. You might even be
able to j
On 06/09/2016 10:17 AM, Andreas Herrmann wrote:
>> IIRC its' conditioned on $NIX_ENFORCE_NO_NATIVE exactly in order
>> not to be filtered out when run outside a nix builder. IMO that's a
>> good default. Hydra isn't the only reason; many devs use remote
>> builds or nix-copy-closure.
> How would yo
I pin my Haskell packages by using fetchFromGitHub with a specific nixpkgs
revisions, and then import the result. The only downside is the Haskell
packages linking against things like OpenSSL as you say wouldn't get
patched.
On Wed, 8 Jun 2016, 8:58 p.m. Teo Klestrup Röijezon,
wrote:
> So there
Thanks for your response.
On Wednesday 08 June 2016 22:54:04 Vladimír Čunát wrote:
> On 06/08/2016 04:14 PM, Andreas Herrmann wrote:
> > Especially, when being run outside of a nix-builder.
>
> IIRC its' conditioned on $NIX_ENFORCE_NO_NATIVE exactly in order not to
> be filtered out when run outs
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: fcb0023e8030074f140c69013a6b339880cd24de
https://github.com/NixOS/nixpkgs/commit/fcb0023e8030074f140c69013a6b339880cd24de
Author: obadz
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M pkgs/dev
76 matches
Mail list logo
