Branch: refs/heads/staging
Home: https://github.com/NixOS/nixpkgs
Commit: 2d3d105b02a6057dcac1c4e78472e8b55cc8ad30
https://github.com/NixOS/nixpkgs/commit/2d3d105b02a6057dcac1c4e78472e8b55cc8ad30
Author: Tuomas Tynkkynen
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 659bea9dda982c7bf4518d58ebc7db4186b9fd5b
https://github.com/NixOS/nixpkgs/commit/659bea9dda982c7bf4518d58ebc7db4186b9fd5b
Author: Nikolay Amiantov
Date: 2016-06-11 (Sat, 11 Jun 2016)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 5dc116e4566b360720ea78a9901ebd785fe27d43
https://github.com/NixOS/nixpkgs/commit/5dc116e4566b360720ea78a9901ebd785fe27d43
Author: Nikolay Amiantov
Date: 2016-06-11 (Sat, 11 Jun 2016)
Changed paths:
On Wed, Jun 8, 2016 at 5:34 AM, Peter Simons wrote:
> Fellow Haskell Hackers,
>
> once the LTS 7.x package set comes out, I intend to make the following
> changes in "master":
>
> - haskellPackages will loosely follow the most recent LTS release,
>
> where "loosely" means that we'll honor the man
hmmm,
so I changed the Vagrantfile that was working and tried to break it (to
replicate the travis failed build), by adding the chroot option.
But it still works fine.
The Vagrantfile that fails is executing the same build steps as the travis
builds.
This is causing me an itch.
```
vbox_versio
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 527077f02c01c3bc62766703dd315ea438dcf994
https://github.com/NixOS/nixpkgs/commit/527077f02c01c3bc62766703dd315ea438dcf994
Author: Christian Lask
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
M
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 2b7b6047a548d12ebd85c82ef655bac311db073c
https://github.com/NixOS/nixpkgs/commit/2b7b6047a548d12ebd85c82ef655bac311db073c
Author: Matthew Bauer
Date: 2016-06-08 (Wed, 08 Jun 2016)
Changed paths:
M
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 7537e228bcb8406dda4e4b475c6014120450f7aa
https://github.com/NixOS/nixpkgs/commit/7537e228bcb8406dda4e4b475c6014120450f7aa
Author: Matthias Beyer
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
M
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 0b30c3ab95ebf23016126fa1c50c336f7a3279d8
https://github.com/NixOS/nixpkgs/commit/0b30c3ab95ebf23016126fa1c50c336f7a3279d8
Author: Joel Moberg
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
M pk
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: da021cdda1f019f9a75982f44bd8c9b748ae947d
https://github.com/NixOS/nixpkgs/commit/da021cdda1f019f9a75982f44bd8c9b748ae947d
Author: Michael Raskin <7c6f4...@mail.ru>
Date: 2016-06-10 (Fri, 10 Jun 2016)
Ch
ohh first time I've seen such gauntlet throwing. Passionate Haskellers!
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 76b331ae592150c853e01e6451ff0781a8513766
https://github.com/NixOS/nixpkgs/commit/76b331ae592150c853e01e6451ff0781a8513766
Author: Kamil Chmielewski
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
Just as a point of reference, in my job at LumiGuide I'm in camp 4: "I want
total control over my entire package set."
* We run a high-profile production system consisting of multiple NixOS
machines deployed using nixops to physical machines across the Netherlands
and to machines on Hetzner. I als
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: b21329e0e04a7f7a6f37686f75ced7207750885e
https://github.com/NixOS/nixpkgs/commit/b21329e0e04a7f7a6f37686f75ced7207750885e
Author: Alexey Shmalko
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
M
Hi Daniel,
I'm going to reply to your remarks out of order, because there is a
clarification I need to make before I go on.
On Fri, Jun 10, 2016 at 8:05 AM, Daniel Peebles wrote:
> I see a few possible outcomes here:
>
> Peter is swayed by Anthony and Thomas's arguments, and decides to keep
> (p
Hi Thomas,
> Anthony's complaint is:
>
> The choice to discontinue Stackage support makes Nixpkgs
> significantly less useful to some of our users.
which packages do you (or Anthony) compile in old LTS package sets today
that you would be unable to build in haskell.packages.lts? If there
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 4fbafb23957c04dded895a17f052428fa21e51e9
https://github.com/NixOS/nixpkgs/commit/4fbafb23957c04dded895a17f052428fa21e51e9
Author: Shea Levy
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
M pkgs
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 9e959ce6441a3309c2f3e7b07c62f7c681e8eb6f
https://github.com/NixOS/nixpkgs/commit/9e959ce6441a3309c2f3e7b07c62f7c681e8eb6f
Author: Shea Levy
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: d1e4ee146d68a21c263d094acb416b050af32939
https://github.com/NixOS/nixpkgs/commit/d1e4ee146d68a21c263d094acb416b050af32939
Author: uwap
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M nixos/mod
Hi,
I'd like to reinforce Thomas'es writing and I'd like to add that as it
is important how we do things, it is also important how we reach the
consensus. I think any of us want only what produces best results.
Nix being a tool that works on many platforms with many different
languages, different
Yeah. I think there's a tough balance to strike in OSS between feedback and
gratitude, and most of us have been on both wrong sides of it in the past.
Peter is putting all this work in for free and has almost single-handedly
been responsible for drawing a sizable chunk of the Haskell community
(in
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: d73f5d69930fe7293f53548c682cc2ef6711cfbf
https://github.com/NixOS/nixpkgs/commit/d73f5d69930fe7293f53548c682cc2ef6711cfbf
Author: Kamil Chmielewski
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: ff42b489c16da92b19d647d2a7cd65bdd355d9ee
https://github.com/NixOS/nixpkgs/commit/ff42b489c16da92b19d647d2a7cd65bdd355d9ee
Author: obadz
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
M pkgs/top
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 1f99f81d24f131ddc9c9b2c847aa873391e715e2
https://github.com/NixOS/nixpkgs/commit/1f99f81d24f131ddc9c9b2c847aa873391e715e2
Author: rushmorem
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
M pkgs
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: aea7158e794dcf30e83f29c8c2f59a2db59a60ca
https://github.com/NixOS/nixpkgs/commit/aea7158e794dcf30e83f29c8c2f59a2db59a60ca
Author: Herwig Hochleitner
Date: 2016-05-29 (Sun, 29 May 2016)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: a6072331c0237999c6dfcdf618d2ea9ee6dcc10a
https://github.com/NixOS/nixpkgs/commit/a6072331c0237999c6dfcdf618d2ea9ee6dcc10a
Author: Michael Raskin <7c6f4...@mail.ru>
Date: 2016-06-10 (Fri, 10 Jun 2016)
Ch
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 0f7a0a037744c2693f3899258c141406199d
https://github.com/NixOS/nixpkgs/commit/0f7a0a037744c2693f3899258c141406199d
Author: Peter Simons
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
M p
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 42b3156b4e005aae743caee3547f700d8b77188e
https://github.com/NixOS/nixpkgs/commit/42b3156b4e005aae743caee3547f700d8b77188e
Author: Stefan Junker
Date: 2016-06-09 (Thu, 09 Jun 2016)
Changed paths:
M
Hi Peter and Anthony,
On Thu, Jun 9, 2016 at 4:04 PM, Peter Simons wrote:
> 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 ha
Fellow Haskell Hackers,
Nix gives you great freedom to choose how to develop and deploy your
Haskell software. That's good, but at the same time that flexibility can
be confusing and feel like a burden. Therefore, I'd like to shed some
light on this issue and discuss different types of strategies
Hi Tomasz,
That sounds really interesting, I read the other threads and it seems like
I can implement this strategy.
I'm not yet 100% clear on how I can have the keys from /run/keys loaded in
the various configuration files. For plain PHP config files like wordpress
uses, I'm sure a simple file_
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: e0e9df7c8d81eaca4ef0113cef97016705bd8485
https://github.com/NixOS/nixpkgs/commit/e0e9df7c8d81eaca4ef0113cef97016705bd8485
Author: Christian Lask
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
A
Le 10/06/16 à 12:09, Joachim Schiele a écrit :
> On 09.06.2016 19:21, Layus wrote:
>> 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-closur
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 64a6e099796764708e24888ced7196ce3d5df6fd
https://github.com/NixOS/nixpkgs/commit/64a6e099796764708e24888ced7196ce3d5df6fd
Author: Christian L
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
M pk
I would switch in a heartbeat, using ubuntu, docker+virtualbox(inside
virtualbox), virtualbox screen size issues, something called
docker-machine I have to install manually into /usr/local/bin/ is not
fun, and I'm actively suppressing grumpiness ... it's times like this
I really appreciate nix. My
On 09.06.2016 19:21, Layus wrote:
> 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-libXcomp
On 10.06.2016 02:11, stewart mackenzie 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.
your observation is correct.
> Is there a faster route?
you can also deploy wordpress manually as you probably d
On 16-06-09 05:25pm, Anthony Cowley wrote:
> I think that telling users to stick to a single version of nixpkgs and take
> responsibility for cherry-picking individual security and bug fix commits to
> all Haskell and system libraries they depend on is the worst job a package
> management system ca
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 548a136345db627ca52cc3f12b222002ac0655b4
https://github.com/NixOS/nixpkgs/commit/548a136345db627ca52cc3f12b222002ac0655b4
Author: Rickard Nilsson
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 656c48f141be5886c515a1a874a47472cbbac6bd
https://github.com/NixOS/nixpkgs/commit/656c48f141be5886c515a1a874a47472cbbac6bd
Author: Rickard Nilsson
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
I usually try to look at the recent changes to find out what might gotten
wrong, both in the configuration.nix and nixpkgs. Unfortunately I don't
know of a tool that could provide that diff between two generations so I
usually stick to one change at a time.
On Fri, 10 Jun 2016, 01:48 Evan Rowley,
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 335ccfcf3440b5f45ea45ba4216a68cb8b84e249
https://github.com/NixOS/nixpkgs/commit/335ccfcf3440b5f45ea45ba4216a68cb8b84e249
Author: Rickard Nilsson
Date: 2016-06-10 (Fri, 10 Jun 2016)
Changed paths:
It doesn't look like your vms are using the nix sandbox so some things
could get picked from the environment?
On Thu, 9 Jun 2016, 22:36 Azul, wrote:
> 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:
43 matches
Mail list logo