On 03/02/2015 10:46 AM, Eelco Dolstra wrote:
A few days passed. I merged staging from the libsigsegv change. I didn't know
next commits, so I thought better not to merge them.
That kind of defeats the purpose of the staging branch, which is to combine
mass rebuild changes. See here:
Why
Hi,
On 01/03/15 22:15, Lluís Batlle i Rossell wrote:
If that commit could be merged into master, it would be nice. I'd be able to
commit to master instead.
We'd better wait a few days for Hydra to catch up a bit:
http://hydra.nixos.org/eval/1173079
A few days passed. I merged staging
On Fri, Feb 20, 2015 at 11:45:01AM +0100, Vladimír Čunát wrote:
On 02/20/2015 11:36 AM, Lluís Batlle i Rossell wrote:
If that commit could be merged into master, it would be nice. I'd be able to
commit to master instead.
We'd better wait a few days for Hydra to catch up a bit:
On Fri, Feb 20, 2015 at 11:33:40AM +0100, Vladimír Čunát wrote:
On 02/20/2015 09:29 AM, Lluís Batlle i Rossell wrote:
a trivial work-around for the libsigsegv issue is now in staging:
This is not yet in 'master', right? What are we waiting to have it in
'master'?
Hydra?
Yes, ATM it's
On 02/20/2015 11:36 AM, Lluís Batlle i Rossell wrote:
If that commit could be merged into master, it would be nice. I'd be able to
commit to master instead.
We'd better wait a few days for Hydra to catch up a bit:
http://hydra.nixos.org/eval/1173079
Vladimir
smime.p7s
Description: S/MIME
On 02/20/2015 09:29 AM, Lluís Batlle i Rossell wrote:
a trivial work-around for the libsigsegv issue is now in staging:
This is not yet in 'master', right? What are we waiting to have it in 'master'?
Hydra?
Yes, ATM it's the only commit in master..staging.
Vladimir
smime.p7s
On Tue, Feb 17, 2015 at 11:56:00PM +0100, Lluís Batlle i Rossell wrote:
On Tue, Feb 17, 2015 at 11:45:28PM +0100, Peter Simons wrote:
Hi guys,
a trivial work-around for the libsigsegv issue is now in staging:
On Tue, Feb 17, 2015 at 11:45:28PM +0100, Peter Simons wrote:
Hi guys,
a trivial work-around for the libsigsegv issue is now in staging:
https://github.com/NixOS/nixpkgs/commit/953466fcbaea0f7c4d48b5a6e3905d4e07b9a79d
I'll merge it to master within a couple of days, once Hydra has
Hi guys,
a trivial work-around for the libsigsegv issue is now in staging:
https://github.com/NixOS/nixpkgs/commit/953466fcbaea0f7c4d48b5a6e3905d4e07b9a79d
I'll merge it to master within a couple of days, once Hydra has built
binaries for the new stdenv version. If anyone is aware of a
About sigsegv, what is the recommended procedure?
2015-02-14 12:45 GMT-02:00 Anderson Torres torres.anderson...@gmail.com:
2015-02-13 20:31 GMT-02:00 Lluís Batlle i Rossell vi...@viric.name:
On Fri, Feb 13, 2015 at 11:29:03PM +0100, Bjørn Forsman wrote:
On 13 February 2015 at 23:26, James Cook
The repository masters are silent about it. Niksut? Dr Pepper? Peti?
I guess they don't experience the problem, so they are ready to wait to new
kernels arrive. That's all guessing; I haven't seen any formal position. That's
why I asked at the time staging was merged.
An easier way would have
2015-02-13 20:31 GMT-02:00 Lluís Batlle i Rossell vi...@viric.name:
On Fri, Feb 13, 2015 at 11:29:03PM +0100, Bjørn Forsman wrote:
On 13 February 2015 at 23:26, James Cook jc...@cs.berkeley.edu wrote:
https://github.com/NixOS/nixpkgs/issues/6028#issuecomment-72952987
The error is caused by
On Fri, Feb 13, 2015 at 11:07:27PM +0100, Bjørn Forsman wrote:
On 13 February 2015 at 22:20, Lluís Batlle i Rossell vi...@viric.name wrote:
Thank you! Is the plan for failing libsigsegv to wait for
kernel.org fixes?
What's the connection between libsigsegv and kernel.org? I noticed
On 13 February 2015 at 23:26, James Cook jc...@cs.berkeley.edu wrote:
https://github.com/NixOS/nixpkgs/issues/6028#issuecomment-72952987
The error is caused by an impurity, so bisecting might just reveal which
version you had in the store before you switched to a newer kernel.
Ah, right.
https://github.com/NixOS/nixpkgs/issues/6028#issuecomment-72952987
The error is caused by an impurity, so bisecting might just reveal which
version you had in the store before you switched to a newer kernel.
On 13 February 2015 at 14:12, Lluís Batlle i Rossell vi...@viric.name
wrote:
On Fri,
On Fri, Feb 13, 2015 at 11:29:03PM +0100, Bjørn Forsman wrote:
On 13 February 2015 at 23:26, James Cook jc...@cs.berkeley.edu wrote:
https://github.com/NixOS/nixpkgs/issues/6028#issuecomment-72952987
The error is caused by an impurity, so bisecting might just reveal which
version you had
Thank you! Is the plan for failing libsigsegv to wait for
kernel.org fixes?
Regards,
Lluís.
On Fri, Feb 13, 2015 at 10:16:24PM +0100, Peter Simons wrote:
'staging' has been merged to 'master' in 54ce1a1.
___
nix-dev mailing list
'staging' has been merged to 'master' in 54ce1a1.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
On 13 February 2015 at 22:20, Lluís Batlle i Rossell vi...@viric.name wrote:
Thank you! Is the plan for failing libsigsegv to wait for
kernel.org fixes?
What's the connection between libsigsegv and kernel.org? I noticed
libsigsegv test failures the other day (I was playing with armv7
Hi Georges,
There's a curl update PR (https://github.com/NixOS/nixpkgs/pull/6171).
Can it board that train, or should it wait for the next?
IMHO, it looks innocent enough to be included: 7fc94dd3.
Best regards,
Peter
___
nix-dev mailing list
There's a curl update PR (https://github.com/NixOS/nixpkgs/pull/6171). Can
it board that train, or should it wait for the next?
Georges Dubus
2015-02-09 17:08 GMT+01:00 Peter Simons sim...@cryp.to:
Hi guys,
I would like to merge the staging branch back into master as soon as
21 matches
Mail list logo
