We rushed binutils/gcc5 into 16.03 to get it there in time. It's far from ideal, but please open issue if something is not working on 16.03.
On Tue, Mar 22, 2016 at 3:07 PM, Lluís Batlle i Rossell <vi...@viric.name> wrote: > On Tue, Mar 22, 2016 at 02:10:44PM +0100, joach...@fastmail.fm wrote: > > On Tue, Mar 22, 2016, at 01:59 PM, Lluís Batlle i Rossell wrote: > > > How weird. Why that was merged into 16.03 and not into master? Why > isn't > > > master the first step to 16.03? > > > > Because releases are linux only and so are unaffected by the darwin > > breakage. This way we get the feature into the release while minimising > > disruption for nixpkgs users. Makes sense to me. > > > > > So, should we push fixes for gcc5 into 16.03? Will that be merged into > > > master? Should these go to staging? > > > > I'd expect that staging ends up being merged into master at some point, > > so putting fixes into staging makes sense to me. > > I really expected 16.03 to be more stabilised than master, when I switched > my 15.09 to 16.03 to help in stabilisation. It seems that it's the other > way round, now. > > Is it just to be able to say 16.03 instead of 16.04? I don't see that a > good enough reason to put 16.03 ahead of master in that way. I had to fix > things that were working on master, and that feels strange. > > -- > (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP) > PGP key D4831A8A - https://emailselfdefense.fsf.org/ > _______________________________________________ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev >
_______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev