Hello,
we've been trying to update an old nixos with upstart (glibc 2.13) to master,
and it's our ldap server.
Some weird pieces were crashing (nscd, sshd, samba), while all work fine in the
old system.
I've seen nss_ldap is pretty old (2009 latest, 2008 that of nixpkgs), and redhad
has some fix
Can we talk about the details - how to actually name branches?
I propose having the names:
- "next" receiving tested breaking updates (thus is what is master now)
- "stable" receiving non breaking updates only - this will be aliased to 2013-Q2
- 2013-Q1 receiving non breaking update only
older sta
Looking at the end of your stage-4 log we see that a build failed because
containers-0.4.2.1-75f143aa39a3e77a1ce2300025bdd8ce is missing. That is part
of ghc, and the nix hash of your ghc-wrapper is
vlx3ikjjxlfvqjjlx74cg07p79y43mdq, which agrees with the Hydra trunk:
http://hydra.nixos.org/bu
On 05/16/2013 12:31 PM, Peter Simons wrote:
Now, steps (1) and (2) are easy.
Step (3) is hard, because it's an on-going effort that someone needs to
pay attention to constantly. Also, propagating changes from master into
the release branch can be difficult, because the commits in question may
de
Hi Eelco,
> It would be good to have stable releases that get bug fixes for a
> certain amount of time. For instance, we could make a stable release
> every 3 months or so, named (Ubuntu-style) ., e.g. 13.06,
> 13.09, and so on.
let me try to translate this goal into actions that need to be t
Hrm,
That proves to be harder than I hoped.
I got it to build, but it won't start yet (but gives no errors/warnings).
So I will have to dig deeper.
On Wed, May 15, 2013 at 3:05 PM, Eelco Dolstra
wrote:
> Hi,
>
> On 15/05/13 13:55, Mathijs Kwik wrote:
>
>> Our current expression for firefox [1]
