Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: a6860133218333e3b44dcd777936ac75ebe06767
https://github.com/NixOS/nixpkgs/commit/a6860133218333e3b44dcd777936ac75ebe06767
Author: Shea Levy <s...@shealevy.com>
Date: 2016-08-14 (Sun, 14 Au
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: a34cc59605a20cc141ab564d8535da61fb0c1d60
https://github.com/NixOS/nixpkgs/commit/a34cc59605a20cc141ab564d8535da61fb0c1d60
Author: Shea Levy <s...@shealevy.com>
Date: 2016-08-14 (Sun, 14 Au
Branch: refs/heads/master
Home: https://github.com/NixOS/nix
Commit: a6eed133c5a3602037bc48675ca783185cca5454
https://github.com/NixOS/nix/commit/a6eed133c5a3602037bc48675ca783185cca5454
Author: Shea Levy <s...@shealevy.com>
Date: 2016-08-10 (Wed, 10 Aug 2016)
Changed
Branch: refs/heads/master
Home: https://github.com/NixOS/nix
Commit: e3128014dbef2f0cd172767ff8904d25f6efccbb
https://github.com/NixOS/nix/commit/e3128014dbef2f0cd172767ff8904d25f6efccbb
Author: Shea Levy <s...@shealevy.com>
Date: 2016-08-10 (Wed, 10 Aug 2016)
Changed
ixpkgs#15974
It's not a nice fix, as it's really clang's problem. The proper fix
should modify clang's usage of IntrusiveRefCntPtr.
Commit: ca81eef7538f1be7a7e1bc3466594ae030738977
https://github.com/NixOS/nixpkgs/commit/ca81eef7538f1be7a7e1bc3466594ae030738977
Author: Shea L
Applied, thanks!
Karn Kallio writes:
> The attached patch advances the nvidia-x11 in nixpkgs to the latest
> stable version 365.35, and also patches it to build with kernel 4.7.
> From 4676cdfcb140ae4449a55828c654f0330d3f0a0f Mon Sep 17 00:00:00 2001
> From: Karn
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: be56795a5938c3475c170b83b9e4e34f68f28cf9
https://github.com/NixOS/nixpkgs/commit/be56795a5938c3475c170b83b9e4e34f68f28cf9
Author: Shea Levy <s...@shealevy.com>
Date: 2016-08-01 (Mon, 01 Au
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 52b787b0cd779f1f0da379127fa4e8db0b927551
https://github.com/NixOS/nixpkgs/commit/52b787b0cd779f1f0da379127fa4e8db0b927551
Author: Shea Levy <s...@shealevy.com>
Date: 2016-08-01 (Mon, 01 Au
?
~Shea
[1]: https://github.com/shlevy/long-shebang
Eelco Dolstra <eelco.dols...@logicblox.com> writes:
> Hi Shea,
>
> On 07/29/2016 10:48 PM, Shea Levy wrote:
>
>> For the perl->c++ work, how should we handle nix-shell shebangs given
>> that the command is now &q
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 36bc5257e395b627f7f99851f72545544f3943a9
https://github.com/NixOS/nixpkgs/commit/36bc5257e395b627f7f99851f72545544f3943a9
Author: Shea Levy <s...@shealevy.com>
Date: 2016-07-31 (Sun, 31 Ju
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 03a8f723bdce313fed87e2ef5c8931f9d6715ae3
https://github.com/NixOS/nixpkgs/commit/03a8f723bdce313fed87e2ef5c8931f9d6715ae3
Author: Shea Levy <s...@shealevy.com>
Date: 2016-07-31 (Sun, 31 Ju
I've made several PRs and issues, see https://github.com/NixOS/nix/milestone/6
Profpatsch <m...@profpatsch.de> writes:
> On 16-07-29 04:48pm, Shea Levy wrote:
>> Hi Eelco,
>>
>> For the perl->c++ work, how should we handle nix-shell shebangs given
>> that th
Hi Eelco,
For the perl->c++ work, how should we handle nix-shell shebangs given
that the command is now "nix shell"? Should the nix command itself
contain shebang-checking logic, or should we have a separate nix-shell
C++ program just for shebangs, or something else?
Thanks,
Shea
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: ac93e9f2c8bbdee7b3c88d8eb358fe4f81fb578a
https://github.com/NixOS/nixpkgs/commit/ac93e9f2c8bbdee7b3c88d8eb358fe4f81fb578a
Author: Shea Levy <s...@shealevy.com>
Date: 2016-07-24 (Sun, 24 Ju
Branch: refs/heads/master
Home: https://github.com/NixOS/nix
Commit: 18b0808475a3d252ff3dc977e510271ea5c8c284
https://github.com/NixOS/nix/commit/18b0808475a3d252ff3dc977e510271ea5c8c284
Author: Shea Levy <s...@shealevy.com>
Date: 2016-07-23 (Sat, 23 Jul 2016)
Changed
Branch: refs/heads/master
Home: https://github.com/NixOS/nix
Commit: 3c68a661f28ffb52efbca10146a059003ff579a7
https://github.com/NixOS/nix/commit/3c68a661f28ffb52efbca10146a059003ff579a7
Author: Shea Levy <s...@shealevy.com>
Date: 2016-07-21 (Thu, 21 Jul 2016)
Changed
Branch: refs/heads/find-runtime-roots-c++
Home: https://github.com/NixOS/nix
Commit: 513c65cde56d81fc65f5c303cd82a5632511cb3d
https://github.com/NixOS/nix/commit/513c65cde56d81fc65f5c303cd82a5632511cb3d
Author: Shea Levy <s...@shealevy.com>
Date: 2016-07-20 (Wed, 20 Ju
Branch: refs/heads/master
Home: https://github.com/NixOS/nix
Commit: 06068b353d7867d0e0299d4285e9b1a46195144c
https://github.com/NixOS/nix/commit/06068b353d7867d0e0299d4285e9b1a46195144c
Author: Shea Levy <s...@shealevy.com>
Date: 2016-07-13 (Wed, 13 Jul 2016)
Changed
Branch: refs/heads/master
Home: https://github.com/NixOS/nix
Commit: b33e85229d3ac78242d8bc597cfdaa282486743f
https://github.com/NixOS/nix/commit/b33e85229d3ac78242d8bc597cfdaa282486743f
Author: Shea Levy <s...@shealevy.com>
Date: 2016-07-13 (Wed, 13 Jul 2016)
Changed
Branch: refs/heads/master
Home: https://github.com/NixOS/nix
Commit: cb5e7254b66a06b78a5659551a6f28fc67e52267
https://github.com/NixOS/nix/commit/cb5e7254b66a06b78a5659551a6f28fc67e52267
Author: Shea Levy <s...@shealevy.com>
Date: 2016-07-11 (Mon, 11 Jul 2016)
Changed
With nodePackages.jsontool installed:
$ nix-env -i $(curl -LH "Accept: Application/JSON"
http://hydra.nixos.org/job/nix/master/build.x86_64-linux/latest | json
buildoutputs.out.path)
Bjørn Forsman writes:
> On 30 June 2016 at 17:12, Domen Kožar wrote:
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 1e159c7b2cdc7793a7e8034df845e439942bef83
https://github.com/NixOS/nixpkgs/commit/1e159c7b2cdc7793a7e8034df845e439942bef83
Author: Shea Levy <s...@shealevy.com>
Date: 2016-06-28 (Tue, 28 Ju
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 6857424cf307eda493d458bc77a1b53f2040cfda
https://github.com/NixOS/nixpkgs/commit/6857424cf307eda493d458bc77a1b53f2040cfda
Author: Shea Levy <s...@shealevy.com>
Date: 2016-06-28 (Tue, 28 Ju
commit/8f28dad52ce7da0dd4d2342dfb740a5b5e1f4d9b
Author: Shea Levy <s...@shealevy.com>
Date: 2016-06-21 (Tue, 21 Jun 2016)
Changed paths:
A pkgs/applications/misc/nix-tour/default.nix
M pkgs/top-level/all-packages.nix
Log Message:
---
Merge branch 'nix-tour' of git://github.com/qkn
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 4fbafb23957c04dded895a17f052428fa21e51e9
https://github.com/NixOS/nixpkgs/commit/4fbafb23957c04dded895a17f052428fa21e51e9
Author: Shea Levy <s...@shealevy.com>
Date: 2016-06-10 (Fri, 10 Ju
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 9e959ce6441a3309c2f3e7b07c62f7c681e8eb6f
https://github.com/NixOS/nixpkgs/commit/9e959ce6441a3309c2f3e7b07c62f7c681e8eb6f
Author: Shea Levy <s...@shealevy.com>
Date: 2016-06-10 (Fri, 10 Ju
n 2016)
Changed paths:
M nixos/modules/system/boot/stage-2-init.sh
Log Message:
---
stage2: if no /proc, also mount /sys
Commit: 83c2629f152304b9f031ca3bffedd32276be6cd9
https://github.com/NixOS/nixpkgs/commit/83c2629f152304b9f031ca3bffedd32276be6cd9
Author: Shea L
Hey Dan,
This sounds a lot like the motivation and design for nix-exec, have you
looked into whether it might work for you as-is or with something built
on top of it? I'd be happy to chat about this too if you want to go over
in more detail.
~Shea
Daniel Peebles writes:
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 01f571148583bcc85fad1963536a788d828befbf
https://github.com/NixOS/nixpkgs/commit/01f571148583bcc85fad1963536a788d828befbf
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-16 (Mon, 16 Ma
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: da998cffcdc27c13822d0cc713cb93cb94824ee0
https://github.com/NixOS/nixpkgs/commit/da998cffcdc27c13822d0cc713cb93cb94824ee0
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-16 (Mon, 16 Ma
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 6c23e7e59ab39b0cdb9bda1325382d5b955f3c0b
https://github.com/NixOS/nixpkgs/commit/6c23e7e59ab39b0cdb9bda1325382d5b955f3c0b
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-16 (Mon, 16 Ma
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 059fc4505d15195ce731015e0a0ba939ffd65ecd
https://github.com/NixOS/nixpkgs/commit/059fc4505d15195ce731015e0a0ba939ffd65ecd
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-16 (Mon, 16 Ma
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 1ea263ef03fd03b8e3a9cd57b8babe9735d9c77a
https://github.com/NixOS/nixpkgs/commit/1ea263ef03fd03b8e3a9cd57b8babe9735d9c77a
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-16 (Mon, 16 Ma
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 102a5d663c37d4605eea4c13b25ac3bec64ac6fb
https://github.com/NixOS/nixpkgs/commit/102a5d663c37d4605eea4c13b25ac3bec64ac6fb
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-16 (Mon, 16 Ma
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 0373eb86f17cada1454d698a750345f7b6c522e9
https://github.com/NixOS/nixpkgs/commit/0373eb86f17cada1454d698a750345f7b6c522e9
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-16 (Mon, 16 Ma
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 1906eb9cd5d701e0167b4261e6de8375b3fa7cf4
https://github.com/NixOS/nixpkgs/commit/1906eb9cd5d701e0167b4261e6de8375b3fa7cf4
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-11 (Wed, 11 Ma
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 67d430096f2527689c9abc8a48af21a5ecfe67de
https://github.com/NixOS/nixpkgs/commit/67d430096f2527689c9abc8a48af21a5ecfe67de
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-11 (Wed, 11 Ma
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: b10f61bc1bcc1f93ca0936fee5204369a09c
https://github.com/NixOS/nixpkgs/commit/b10f61bc1bcc1f93ca0936fee5204369a09c
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-10 (Tue, 10 Ma
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: e2cd6d6931b3afdc0120c4f6ae1ed3afb8012cd6
https://github.com/NixOS/nixpkgs/commit/e2cd6d6931b3afdc0120c4f6ae1ed3afb8012cd6
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-10 (Tue, 10 Ma
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 6f12b7aec4ff331f637206d1841168a9b59b8bb8
https://github.com/NixOS/nixpkgs/commit/6f12b7aec4ff331f637206d1841168a9b59b8bb8
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-10 (Tue, 10 Ma
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 042b69374da7c9d05c3d340c180c419ea2413338
https://github.com/NixOS/nixpkgs/commit/042b69374da7c9d05c3d340c180c419ea2413338
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-10 (Tue, 10 Ma
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: f298ebb957ac5ac2068fa02fd671004e26d713a0
https://github.com/NixOS/nixpkgs/commit/f298ebb957ac5ac2068fa02fd671004e26d713a0
Author: Shea Levy <s...@shealevy.com>
Date: 2016-05-10 (Tue, 10 Ma
On 2016-03-03 19:34, Profpatsch wrote:
> On 16-02-28 04:44pm, zimbatm wrote:
>> So something like that ? https://github.com/NixOS/nixpkgs/pull/13552
>> And then we would convert all of our tooling to output JSON ?
>
> As long as nixexprs embedded in the JSON are *not* evaluated in any
> way,
> we
rsion of the parent.
>
> Second,
with npm 3.x's flat module installations, we must move packages as high
as possible in the nested node_modules/ hierarchy, until a conflict has
been encountered.
>
> On Tue, Mar 1, 2016 at 1:53 PM, Shea Levy
<s...@shealevy.com> wrote:
>
>&
"including NPM dependencies is stateful" how so? Having separate
derivations symlinked in would give you sharing, no?
On 2016-03-01 08:15, Sander van der Burg wrote:
> Hi,
>
> I don't know how many of you have noticed my latest blog post
>
>
Someone (I think Vladimir?) offered to translate docs in any format
into the necessary docbook, and has done so at least for one of my PRs.
As long as that offer still stands and isn't overwhelming him, we can
avoid spending time and resources switching over our format until we
actually have
Hi all,
The printing tests are failing on hydra. Anyone know what might be
going on here? http://hydra.nixos.org/build/32105948
~Shea
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
There is a much better solution available to entirely replace a bad
store path without violating any nix invariants (e.g. modifying store
paths), see
http://lists.science.uu.nl/pipermail/nix-dev/2016-February/019564.html
for an example. It does have the same dynamic-only limitation, of
On 2016-02-16 14:25, Kosyrev Serge wrote:
> rocon...@theorem.ca writes:
>> I am using the following expression which I believe will build a
>> patched
>> version of glibc locally, and then build a patched NixOS derivation.
>>
>> system.replaceRuntimeDependencies = with pkgs.lib;
>>
ibc;
> replacement = builtins.storePath
> /nix/store/5fbwy40pa4pqr97jdgbyaal1y1ns6hb1-glibc-2.21; }) ];
and do a nixos-rebuild against the channel to get a secured system
until the channel is updated.
Regards,
Shea
On 2016-02-16 11:36, Shea Levy wrote:
> Fixed patch pushed to master, 15.0
Fixed patch pushed to master, 15.09, and 14.12.
On 2016-02-16 10:58, Shea Levy wrote:
> There was an error with the patch, we're cooking up a fix now.
>
> On 2016-02-16 10:37, Shea Levy wrote:
>> Hi all,
>>
>> I've just merged the patch to fix CVE-2015-7547, a
There was an error with the patch, we're cooking up a fix now.
On 2016-02-16 10:37, Shea Levy wrote:
> Hi all,
>
> I've just merged the patch to fix CVE-2015-7547, a buffer overrun in
> glibc with working POC exploit, into master and 15.09. It will take
> some
> time for the
Hi all,
I've just merged the patch to fix CVE-2015-7547, a buffer overrun in
glibc with working POC exploit, into master and 15.09. It will take some
time for the channel to update, so please use your judgment as to
whether you want to wait for that or switch to building from git until
it
This is intentional: @-capture captures what was actually passed. You
can always do something like: let args_ = args // { buildDepends =
args.buildDepends or buildDepends; } if you really need this behavior.
On 2016-02-12 06:11, Sergey Mironov wrote:
> Hi. I have an issue regarding the
This may not be the case any more, but in the past at least you had to
explicitly specify the newc cpio format (with -H newc) when calling cpio to
make initrds.
> On Jan 30, 2016, at 5:26 AM, Roger Qiu wrote:
>
> Hi,
>
> There's an option called: `boot.initrd.prepend`. I
chroot"-containing strings got renamed to "sandbox". In
> particular,
> some Nix options got renamed, but the old names are still
> accepted as
> lower-priority aliases.
>
> This release has contributions from Anders Claesson, Anthony Cowley,
> Bjørn
>
Nothing's stopping you from starting the conversion. If it's clearly
better, it will be a lot easier to convince people once you have actual
code to show.
On 2015-12-30 20:30, stewart mackenzie wrote:
> On Thu, Dec 31, 2015 at 4:04 AM, jeaye wrote:
>> As C++ devs, I think
https://github.com/NixOS/nix/pull/31 may be relevant.
On 2015-12-28 11:10, Daniel Peebles wrote:
> A few days ago, I proposed importing from a derivation [1] to save us
> from having to manually manage autogenerated firefox/thunderbird
> fixed-output derivaiton hash files and junk up the nixpkgs
I have no opinion on this feature specifically, but re #3: avoiding a feature
in order to keep things in a poor enough state so that users care about the
issues you think they should care about is highly patronizing and a terrible
way for developers to relate to users. It is incidentally
Can you resend with paths appropriate to the nix repo? There is no nix/
directory there.
~Shea
On 2015-12-02 12:03, Ludovic Courtès wrote:
> * nix/libstore/worker-protocol.hh (PROTOCOL_VERSION): Bump to 0x10f.
> * nix/libstore/remote-store.cc (RemoteStore::buildPaths): Send the
> BUILDMODE when
Hi all,
I've just added [1] rudimentary support for building Idris packages and
composing the packages with the compiler to nixpkgs. Details can be
found in the idris-modules directory [2], including potential future
work [3].
Idris's lack of any mechanism to have multiple library paths is
No opinion on the specifics of colors/categories, but +1 for the
general idea.
On 2015-11-21 19:59, Nicolas Pierron wrote:
> Hi everybody,
>
> I spent a day doing triage of newly created bugs and I think the
> labels [1] of our repository are currently a big mess. I think the
> meaning of our
Hi Arseniy,
The ordering of the concatenation is by default unspecified. You can
put constraints on it with 'mkOrder', see
https://github.com/NixOS/nixpkgs/blob/a2aab3a224939cc7c24e88984c5f5ab169aee271/lib/modules.nix#L464-L470
for the details. So you can for example have the line that sets
The problem with doing this with import-from-derivation is we still
need the hashes of every tarball ahead of time (though that's much
smaller than all of hackage, and we really just need the hash of the
file that contains all the hashes in nixpkgs itself). If we have that,
then we don't need
Any update on this?
On 2015-10-19 07:33, Shea Levy wrote:
> Sure, but having stdenv for darwin rely on someone's dropbox is a bad
> situation regardless, right?
>
> On 2015-10-19 07:30, Eelco Dolstra wrote:
>> Hi,
>>
>> On 19/10/15 13:25, Shea Levy wrote:
>>
&
The issue in master is unrelated; It's a networking issue that can only
be fixed by Eelco or Rob (see my email to the ml on Monday). The issue
in staging is due to a bad nix.conf on the darwin box, which again only
Eelco or Rob can fix (its allowed-impure-host-deps field needs to
include
Hi all,
Now that pure-darwin is in master, can we move the binaries to
tarballs.nixos.org? We're currently trying to fetch them from a dropbox
[1], and that is failing on hydra [2] (though it seems to work for me
locally with curl).
Thanks,
Shea
[1]:
Hi Tyson,
Looks like a good start! I’ve left some comments on the commits.
~Shea
On May 15, 2015, at 5:39 PM, Tyson Whitehead twhiteh...@gmail.com wrote:
On April 29, 2015 14:03:08 Tyson Whitehead wrote:
I'm looking to setup a shared nix store for our HPC clusters. Googling for
a shared
Hi all,
Do we still have users running 32-bit machines? It would reduce the load on
hydra significantly if we could drop support for i686, though of course if
people are still relying on it we shouldn't make the change yet.
~Shea
___
nix-dev mailing
Hello,
On Apr 30, 2015, at 4:45 PM, Terrance Kennedy terrancerkenn...@gmail.com
wrote:
Hi,
I'm working on a Python project to convert Python built-in types to Nix
built-in types and it raised some quesions on the limitations of built-in Nix
types. I've been able to gather some
Applied in 71910be9ea225895e36f60ed23a1bdce402b3088, thanks!
On Apr 27, 2015, at 10:16 PM, Jookia 166...@gmail.com wrote:
Passing the chroot flag to nixos-install without arguments should now give
you a
Bash shell as intended rather than try an empty path.
This was masked by the user's
Applied in 7b37a5f168706db5efa33599354f5c1967ac4c51, thanks!
On Apr 27, 2015, at 10:16 PM, Jookia 166...@gmail.com wrote:
When bootstrapping from other distributions, nixos-install is unable to find
various tools in the chroot since their paths aren't aware of NixOS
conventions.
This
As long as I’ve been around we’ve also accepted patches via ML, why not?
On Apr 28, 2015, at 2:34 AM, Wout Mertens wout.mert...@gmail.com wrote:
These patches look useful, but normally we work via github...
On Tue, Apr 28, 2015, 4:17 AM Jookia 166...@gmail.com wrote:
When bootstrapping
Applied in 98d77cd1a57f3ff71d6ef36e727e339dd9cae233
On Apr 16, 2015, at 5:32 PM, Jookia 166...@gmail.com wrote:
When building kernels outputting a zImage, the zImage wasn't correctly copied
in
to the installation. This broke the build process entirely, at least on my ARM
machine.
---
IMO (and this is not limited to Haskell) we should either always use the latest
or, if the latest tends to provide a significantly different experience than
the previous version, not have a default at all and require users to request a
specific version. We do this for mysql in NixOS for
Merged.
On Mar 19, 2015, at 5:55 AM, Shea Levy s...@shealevy.com wrote:
Hi all,
The latest staging evaluation (http://hydra.nixos.org/eval/1176429
http://hydra.nixos.org/eval/1176429) is nearly complete, barring any
objection I will merge that in to master tomorrow morning.
~Shea
Hi all,
The latest staging evaluation (http://hydra.nixos.org/eval/1176429
http://hydra.nixos.org/eval/1176429) is nearly complete, barring any
objection I will merge that in to master tomorrow morning.
~Shea___
nix-dev mailing list
You can already do this. “import foo” will build any derivations that “foo”
depends on at evaluation time.
Note though that really “build at evaluation time” is for several reasons
inferior to “evaluate at build time”, i.e. recursive nix. I have an
implementation for that but it doesn’t look
I don’t think we need 24 hour windows or anything. Don’t revert something that
is just broken for trivial concerns if the other dev is actively responding,
but don’t wait if something is fundamentally broken. My workflow here would be
“see bad commit, revert, open discussion on the revert
For my own use cases at least, I’ve found that when the generic config is not
good enough it’s better to just generate a config on my own the traditional way
(via make nconfig or similar) and pass it to manual-config.
On Feb 10, 2015, at 1:56 PM, Matthias Beyer m...@beyermatthias.de wrote:
Hi all,
For a while now, there has been a lot of work to improve darwin support on the
master branch of joelteon’s nixpkgs fork. With the latest staging merge, the
core of that work is now on upstream master. The rest of the changes available
on joelteon’s fork are very disparate, and it is
wrote:
I see that the darwin machine butters is online (and idle) in Hydra, does
that mean the zalora cache is no longer needed for nixpkgs on Darwin?
On Tue Feb 03 2015 at 3:51:47 PM Domen Kožar do...@dev.si
mailto:do...@dev.si wrote:
:beers:
On Tue, Feb 3, 2015 at 3:40 PM, Shea Levy s
should fast-track the pure-darwin builds. It works swimmingly on
my system, and looks like the current Darwin situation is not tenable. So
anything in pure-darwin that breaks Linux would be good to find early.
On Tue Feb 03 2015 at 4:00:48 PM Shea Levy s...@shealevy.com
mailto:s
specifics? I need people to help break out individual
parts (e.g., clang)
Thanks,
Dan
On Feb 3, 2015, at 10:13, Shea Levy s...@shealevy.com
mailto:s...@shealevy.com wrote:
As far as I know, there is still a lot of churn on pure darwin.
Dan, if we wanted to merge pure darwin soon (say
Yes, I’m planning to work on multiple outputs for ghc soon :)
On Jan 31, 2015, at 3:55 PM, Daniel Peebles pumpkin...@gmail.com wrote:
Yeah, was kidding around!
On Jan 31, 2015, at 10:47, Ertugrul Söylemez ert...@gmx.de wrote:
If only we had a way to produce multiple outputs from a
OK, I’ll take a look at this then, thanks!
On Jan 28, 2015, at 11:08 AM, Peter Simons sim...@cryp.to wrote:
Hi Shea,
Have you looked into how we could make haskell closures smaller with
multiple outputs?
I briefly thought about it, but I haven't put any actual effort into the
subject
Hi all,
There are some important changes on staging that would help make the darwin
stdenv much more usable on master, but hydra is pretty far behind. Can we have
a brief freeze on non-bugfix changes to staging until it’s caught up and merged?
Thanks,
Shea
Hi Peter,
Have you looked into how we could make haskell closures smaller with multiple
outputs? At the very least separating ghc’s shared libs from the compiler
should be a big win, but ideally we would also separate bin and lib for haskell
packages as well.
~Shea
My only interest in this is ensuring that there’s a single switch to be able to
say “install whatever I ask for”, in general though this sounds like a good
idea.
On Jan 21, 2015, at 8:15 PM, Matthias Beyer m...@beyermatthias.de wrote:
On 21-01-2015 21:08:14, Jascha Geerds wrote:
Hi,
On
My prediction: This will cause more headaches than it will save.
On Jan 14, 2015, at 10:17 PM, Marc Weber marco-owe...@gmx.de wrote:
If you use multiple apaches/nginx/mysql/postgresql/whatever instances
its likely to miss adjusting the port or whatsoever. Therefore I'd like
to implement a
If icc has the same command line interface as gcc, in principle it should work.
On Jan 14, 2015, at 6:40 PM, Ben Darwin bcdar...@gmail.com wrote:
We could try to compile with ICC instead if that would be the only
thing we'd have to cp/patchelf. Is it likely we could re-use library
Hi Paul,
With the current haskell infrastructure, it is difficult-to-impossible to
properly override a core package, and due to the transformers dependency
updating mtl amounts to doing just that. However, there has been recent work on
haskellng, which is a new haskell infrastructure that,
if there is a lot of repeated work ?
Aloha,
RK.
On Thu, Jan 8, 2015 at 11:59 PM, Shea Levy s...@shealevy.com
mailto:s...@shealevy.com wrote:
Ah, actually I see Peter already brought haskell-ng into master via the
haskellngPackages attribute. So I’ll just backport that, as it won’t touch
any existing
Hi all,
I’d like to make a case for backporting Peter’s haskell-ng work to 14.12 once
it’s merged into master. If I understand correctly, then if a haskell package’s
version (and the versions of its dependency closure) stay the same, the
haskell-ng branch will result in what is effectively the
Ah, actually I see Peter already brought haskell-ng into master via the
haskellngPackages attribute. So I’ll just backport that, as it won’t touch any
existing haskellPackages stuff. Never mind!
On Jan 8, 2015, at 1:07 PM, Shea Levy s...@shealevy.com wrote:
Hi all,
I’d like to make
Definitely a good idea.
On Jan 7, 2015, at 4:19 AM, Martin Bravenboer martin.bravenb...@gmail.com
wrote:
Hi all,
Would it be a good idea to create a mailing list for announcements only?
It would be nice if people who want to follow releases or major events can
sign up for an email
For dirty dirty hacks, you can set __noChroot = true and get access to the
network.
On Jan 2, 2015, at 1:09 PM, Georges Dubus georges.du...@gmail.com wrote:
Hello everyone
I would like to propose compromise in the purity rules of non-fixed-output
derivations, and hear what you think
This PR should make this problem better (though it won’t handle the ‘rev
changed but url didn’t’ case) https://github.com/NixOS/nixpkgs/pull/5521
https://github.com/NixOS/nixpkgs/pull/5521
On Jan 1, 2015, at 1:27 PM, Shea Levy s...@shealevy.com wrote:
On Jan 1, 2015, at 1:22 PM, Bjørn
On Jan 1, 2015, at 1:22 PM, Bjørn Forsman bjorn.fors...@gmail.com wrote:
On 31 December 2014 at 17:50, Rico Huijbers rix0...@gmail.com wrote:
Hi,
When I copy/paste a fetchgit block from another file, and change the URL and
rev without changing the hash, I expect the download to fail
Hi all,
At Zalora, we are gradually switching to using defnix
https://github.com/zalora/defnix. It is still very much under active
development (read: may change at any time), and the underlying implementation
does use systemd, but the service/functionality interface (check out the
defnixos
301 - 400 of 898 matches
Mail list logo