On Tuesday, May 12, 2015 05:09:17 Arseniy Seroka wrote:
Is there a way to force nix re-download cache (or sources) of derivation
and it's dependencies?
nix-store --repair-path? it doesn't touch dependencies though
___
nix-dev mailing list
I'm on x86_64 and use some of those for running games (mostly what the steam
package already pulls in, plus a few more that were needed for specific games).
The idea to only build them after x86_64 sounds pretty good. Actually, are all
packages build together with the tests or only after they
I'm still using i686 on my Atom based NAS.
It would be okay for me if only nixos-minimal was build for i686.
Nathan.
On Tue, May 12, 2015 at 8:34 AM Tomasz Kontusz tomasz.kont...@gmail.com
wrote:
I'm on x86_64 and use some of those for running games (mostly what the
steam package already
Oops, replied to the wrong address.
Wiadomość oryginalna
Od: Tomasz Kontusz tomasz.kont...@gmail.com
Wysłane: Tue May 12 10:25:21 CEST 2015
Do: Anand Patil anand.prabhakar.pa...@gmail.com
Temat: Re: [Nix-dev] Possible bug in ssh key module
It would still be nice if the middle
Hi,
correct me if I’m wrong but SSH keys do not have a strong syntax, and aside
from “there’s less than ssh-rsa…spacesomethingnonspace there isn’t much
you can check for.
Specifically as the comment field can contain pretty much anything and you
can’t check the key data for validity on a
Hi
Peter Simons simons at cryp.to writes:
When diagrams was updated to 1.3 recently, IHaskell was broken
because it depends on 1.2.
From the sound of it, the best thing you can do is learn how to fix
Haskell build errors in Nixpkgs so that you can remedy those issues when
you encounter
Hi Charles,
Charles cooper.charles.m at gmail.com writes:
There is clearly a huge gap in my understanding. How do I get ghc in my
config, and how do I install standard haskell packages? Thanks in advance
for any and all help.
Currently the haskell infrastructure is being transitioned to a new
That's really a question about Unix in general, not just NixOS.
Basically, there are several (a lot) of input methods, but you can cover a
lot of them by setting up ~/.inputrc and xkb.
See:
- http://www.gnu.org/software/bash/manual/html_node/Sample-Init-File.html
-
Yeah, Charles seems to be AWOL for a bit, it would be nice if he merged my
PR... Charles?
Wout.
On Tue, May 12, 2015 at 4:30 PM Christian Theune c...@flyingcircus.io wrote:
On 12 May 2015, at 16:19, Christian Theune c...@flyingcircus.io wrote:
On 12 May 2015, at 16:11, Christian Theune
The build could run a quick check to see if ssh-keygen can read the
file? `ssh-keygen
-l -f filename` will return an error if it can't read a key in the file (it
only checks the first key)
On Tue, May 12, 2015 at 10:33 AM Christian Theune c...@flyingcircus.io
wrote:
Hi,
correct me if I’m
Hi Nikita
I have not looked precisely on using the gold linker yet, but I guess
this might be similar to what I have done with overriding the default
compiler in stdenv [1]. You might want to have a look around the
stdenvAdapters.
[1]
Quoting Linus Arver (2015-05-11 00:52:38)
Hello,
I am still very new to Nix and NixOS so please bear with me.
I followed the instructions in the Nixpkgs manual[1] as well as the
original announcement[2] to create a regular Nix package, which I could
install by putting
minitest =
My experience is equal with Marco, about memory and my usage of i686. i686
is important for me too.
On Tue, May 12, 2015 at 11:43:47AM +0200, Marco Maggesi wrote:
I use 32 bit a lot.
First of all, I use it on some old machines with 32bit hardware.
But, more importantly, I use it regularly on
+1
This seems like a good idea.
On 12 May 2015 at 06:45, William Kennington will...@wkennington.com wrote:
Maybe it would make more sense to only build the i686 builds if our tested
set of x86_64 binaries build correctly. We would still release with both
but it would cut down on a lot of
Hi,
same here.
Many interpreted languages (like Python) are affected by this as they tend to
be quite pointer-happy. As pointer-size doubles from 32bit to 64bit we find
that in most applications we have about 70% increase when moving to 64-bit
ending up with 1.7 as much memory as before. So
Hi Peter,
Peter Simons simons at cryp.to writes:
Hi Miguel,
package binary-0.7.4.0 is broken due to missing package
array-0.5.0.0-470385a50d2b78598af85cfe9d988e1b,
base-4.7.0.2-bfd89587617e381ae01b8dd7b6c7f1c1,
bytestring-0.10.4.0-d6f1d17d717e8652498cab8269a0acd5,
...
I use 32 bit a lot.
First of all, I use it on some old machines with 32bit hardware.
But, more importantly, I use it regularly on virtuabox and xen virtual
machines.
In my experience, for most of my use cases the 32bit require less memory
(which is often not abundant on virtual instances) and it
That's what I need. Thank you!
2015-05-12 9:28 GMT+03:00 phree...@yandex.ru:
On Tuesday, May 12, 2015 05:09:17 Arseniy Seroka wrote:
Is there a way to force nix re-download cache (or sources) of derivation
and it's dependencies?
nix-store --repair-path? it doesn't touch dependencies though
By amd32 do you mean amd64 with 32 bit pointers?
Lluís Batlle i Rossell vi...@viric.name napisał:
amd32 should be ready in the kernel and gcc/glibc. We just need someone
to
prepare nix/nixpgks/nixos for this. :)
On Tue, May 12, 2015 at 12:05:29PM +0200, Christian Theune wrote:
Hi,
same here.
Hi Miguel,
Ok, because of this I have decided to not use binary cache in case I
have to build packages locally later.
that's an unusual strategy, IMHO. It's fine to use a binary cache, you
should just avoid using more than one.
It seems to me that the haskell packages are now essentially
On Tue, May 12, 2015 at 01:21:59PM +0200, Eelco Dolstra wrote:
On 12/05/15 12:49, Lluís Batlle i Rossell wrote:
Yes. Maybe it got renamed... It used to be named 'amd32'.
It's called x32:
http://en.wikipedia.org/wiki/X32_ABI
Thank you!
So this thread could end up in an extra nixos
Hi Tomas,
thank you for the explanation. I'm not familiar at all with the C world
as you just saw.
Regards
Eike
Tomas Hlavaty tomas.hlav...@knowledgetools.de writes:
Hi Eike,
I just found out that this is the strip utility from binutils and I'm
wondering how it can do such a harm…
strip
Hi.
On 05/12/2015 12:45 AM, William Kennington wrote:
Maybe it would make more sense to only build the i686 builds if our
tested set of x86_64 binaries build correctly.
This seems the best suggestion I know of now. It shouldn't be difficult
to implement, and it also makes important x86_64
Yes. Maybe it got renamed... It used to be named 'amd32'.
On Tue, May 12, 2015 at 12:45:36PM +0200, Tomasz Kontusz wrote:
By amd32 do you mean amd64 with 32 bit pointers?
Lluís Batlle i Rossell vi...@viric.name napisał:
amd32 should be ready in the kernel and gcc/glibc. We just need someone
Hi,
I contacted a few people and got zimbatm to react. I’m trying to get his 14.12
branch working. I’ll also have a look at the one from cstrahan.
Additionally I created the wiki page in case someone would like to join me in
the effort:
https://nixos.org/wiki/Vagrant_boxes
On 12 May 2015, at 16:19, Christian Theune c...@flyingcircus.io wrote:
On 12 May 2015, at 16:11, Christian Theune c...@flyingcircus.io wrote:
Hi,
I contacted a few people and got zimbatm to react. I’m trying to get his
14.12 branch working. I’ll also have a look at the one from
Hey, just pulled those PRs. (If GitHub has a way to see pending PRs for
all of one's repos, I'm not aware of it...)
-Charles
On Tue, May 12, 2015, at 03:33 PM, Wout Mertens wrote:
Yeah, Charles seems to be AWOL for a bit, it would be nice if he
merged my PR... Charles?
Wout.
On Tue, May
Hi Peter,
Peter Simons simons at cryp.to writes:
Ok, because of this I have decided to not use binary cache in case I
have to build packages locally later.
that's an unusual strategy, IMHO. It's fine to use a binary cache, you
should just avoid using more than one.
Isn't the issue in
amd32 should be ready in the kernel and gcc/glibc. We just need someone to
prepare nix/nixpgks/nixos for this. :)
On Tue, May 12, 2015 at 12:05:29PM +0200, Christian Theune wrote:
Hi,
same here.
Many interpreted languages (like Python) are affected by this as they tend to
be quite
On 12/05/15 12:49, Lluís Batlle i Rossell wrote:
Yes. Maybe it got renamed... It used to be named 'amd32'.
It's called x32:
http://en.wikipedia.org/wiki/X32_ABI
--
Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/
___
nix-dev mailing list
30 matches
Mail list logo
