Hi Peter,
No, I'm running NixOS, and yes, I don't use chroot bulids.
I'm rebuilding everything twice currently to show you the logs.
It's going to take till evening or even tomorrow I think.
Cheers,
Jan Malakhovski
On Tue, 14 May 2013 21:57:18 +0200
Peter Simons wrote:
> Hi Karn,
>
> > Yes
Why not make a Nix friendly solution to NixOS stable?
1] Make a reference to a particular git branch/commit in the nix store.
2] Retrieve the reference;
3] Build the system off of the nix expressions in the reference.
Currently, Nix lacks a way to uniquely reference the complete Nix
expression fr
Hi Karn,
> Yes, I meant the ABI hashes (visible in the GHC package database).
ah, okay, that makes sense.
Personally, I'm having trouble believing that this particular feature of
GHC is causing those build errors, though, because I've run thousands of
Haskell builds with Nix, and I've not run i
Hi,
On 14/05/13 15:51, Marc Weber wrote:
> b) keeping a roadmap (what changed in topic branches or trunk) is a
> great idea - so people know more easily which version to run - and
> release messages are easy to write
>
> How to do it? I'd prefer not use github pages - while it would work
> I'd l
Hi,
On 14/05/13 17:44, Mathijs Kwik wrote:
>> But the risk with this approach is that people will be tempted to squeeze in
>> wildly destabilizing changes at the last moment :-) I don't think this
>> needs a
>> lot of bureaucracy or rules though, just some good sense not to (say) merge a
>> maj
On Tue, May 14, 2013 at 05:44:43PM +0200, Mathijs Kwik wrote:
> On Tue, May 14, 2013 at 5:33 PM, Eelco Dolstra
> wrote:
> > On 14/05/13 14:25, Mathijs Kwik wrote:
> > But the risk with this approach is that people will be tempted to squeeze in
> > wildly destabilizing changes at the last moment :-
On Tue, May 14, 2013 at 5:33 PM, Eelco Dolstra
wrote:
> Hi,
>
> On 14/05/13 14:25, Mathijs Kwik wrote:
>
>> I would prefer a 3 months cycle.
>> 6 months is quite long, making upgrades (possibly) harder to do.
>
> Agree. OTOH, there is the question of how long release branches are
> maintained.
>
Hi,
On 14/05/13 15:18, Alessio Igor Bogani wrote:
> On 14/05/2013 13:26, Eelco Dolstra wrote:
>> I would like to propose making periodic stable releases of NixOS. Currently
>> we
> [...]
>
> Personally I would be very happy to have a stable NixOS system but I
> wouldn't want to quit from the r
Hi Peter,
> He means GHC's ABI hashes. GHC itself is known to be non-deterministic
> in certain cases. However, most of these issues have been fixed over
> the years, and in the context of Nix, I've never suffered from this
> issue in practice. So it would be interesting to verify if that's
> rea
Hi,
On 14/05/13 14:25, Mathijs Kwik wrote:
> I would prefer a 3 months cycle.
> 6 months is quite long, making upgrades (possibly) harder to do.
Agree. OTOH, there is the question of how long release branches are maintained.
For now I'd say that a release branch should be maintained until the
On Вторник 14 мая 2013 17:02:17 Marc Weber wrote:
> @phreedom
> Do you still remember what exactly broke for new users?
No. This is hearsay as in users complain about livecd failures and that's all
what I know.
> By accident I went offlist (sorry), copy pasting the text here:
>
> Marc Weber
>
@phreedom
Do you still remember what exactly broke for new users?
By accident I went offlist (sorry), copy pasting the text here:
Marc Weber
So again: the real problem is nixos-install not allowing to use
different revision. If new users trying to build "games" they may run
into tro
On Вторник 14 мая 2013 15:54:04 Marc Weber wrote:
> Excerpts from phreedom's message of Tue May 14 15:44:24 +0200 2013:
> > It isn't only about production. I'm sure that we managed to scare away
> > some
> > newbie users with a temporarily broken master branch.
>
> I don't understand why, because
On Tue, May 14, 2013 at 3:54 PM, Marc Weber wrote:
> Excerpts from phreedom's message of Tue May 14 15:44:24 +0200 2013:
>> It isn't only about production. I'm sure that we managed to scare away some
>> newbie users with a temporarily broken master branch.
> I don't understand why, because nixos i
Excerpts from phreedom's message of Tue May 14 15:44:24 +0200 2013:
> It isn't only about production. I'm sure that we managed to scare away some
> newbie users with a temporarily broken master branch.
I don't understand why, because nixos is the *only* distribution you can
just use older revision
a) We should document what "stable" releases lack compared with trunk,
especially security fixes which are applied to trunk, but not to stable
b) keeping a roadmap (what changed in topic branches or trunk) is a
great idea - so people know more easily which version to run - and
release messages are
On Вторник 14 мая 2013 14:25:46 Mathijs Kwik wrote:
> Wow, (y)our little distro is growing up so fast :')
> Congrats on reaching the point where the user base has become large enough
> and is running serious production stuff on it, mandating a stable
> channel.
It isn't only about production. I'm
Hi,
Sorry for my very bad English. I'll hope that you understand my thoughts
anyway.
On 14/05/2013 13:26, Eelco Dolstra wrote:
> I would like to propose making periodic stable releases of NixOS. Currently
> we
[...]
Personally I would be very happy to have a stable NixOS system but I
wouldn't
Eelco Dolstra writes:
> Hi all,
>
> I would like to propose making periodic stable releases of NixOS. Currently
> we
> only have an "unstable" channel that tracks the master branches of NixOS and
> Nixpkgs. The fact that these branches receive potentially major changes at
> indeterminate times
Hi Peter.
> what exactly are you referring to when you say "package hashes"? Do you
> mean the hashes in GHC's package database, or do you refer to the hash
> of a package in the Nix store?
He means GHC's ABI hashes. GHC itself is known to be non-deterministic
in certain cases. However, most of t
Hi Karn,
> I think this is the nondeterministic compilation of GHC. The same
> inputs can lead to different package hashes, which makes it possible
> that the binary cache and your locally built results are
> incompatible.
what exactly are you referring to when you say "package hashes"? Do yo
Hi all,
I would like to propose making periodic stable releases of NixOS. Currently we
only have an "unstable" channel that tracks the master branches of NixOS and
Nixpkgs. The fact that these branches receive potentially major changes at
indeterminate times can make upgrading NixOS somewhat adv
Hi Jan,
> E.g. when building git-annex locally with nix with MissingH package
> installed from the binary cache it reported some wild errors about not
> finding some functions that were supposed to be in MissingH.
could you please post those error messages? I'm afraid it's impossible
to say wh
I think this is the nondeterministic compilation of GHC. The same inputs can
lead to different package hashes, which makes it possible that the binary
cache and your locally built results are incompatible. It is a quite annoying
property of GHC in the context of Nix.
_
24 matches
Mail list logo
