Re: [Nix-dev] 16.03 in gcc5.3, master in gcc 4.9?

[Domen Kožar]

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 
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

Re: [Nix-dev] 16.03 in gcc5.3, master in gcc 4.9?

[Lluís Batlle i Rossell]

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

Re: [Nix-dev] 16.03 in gcc5.3, master in gcc 4.9?

[joachifm]

On Tue, Mar 22, 2016, at 01:59 PM, Lluís Batlle i Rossell wrote:
> On Tue, Mar 22, 2016 at 01:23:39PM +0100, Vladimír Čunát wrote:
> > On 03/22/2016 10:22 AM, Lluís Batlle i Rossell wrote:
> > > I think that someone merged into 16.03 instead of into master unwillingly.
> > > An error. But did this pass unnoticed by the maintainers for more than 15
> > > days?
> > 
> > No, according to some chats the inclusion in 16.03 is intentional. The
> > changes for master are in staging, but there's also mass darwin breakage
> > which noone addresses, so that's why it isn't merged to master yet.
> > https://github.com/NixOS/nixpkgs/commit/dd53c65dccb6#commitcomment-16668634
> > 
> > It's possible the darwin breakage is on 16.03 as well, as Hydra has no
> > darwin jobs for releases AFAIK.
> 
> 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.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 16.03 in gcc5.3, master in gcc 4.9?

[Vladimír Čunát]

On 03/22/2016 10:22 AM, Lluís Batlle i Rossell wrote:
> I think that someone merged into 16.03 instead of into master unwillingly.
> An error. But did this pass unnoticed by the maintainers for more than 15
> days?

No, according to some chats the inclusion in 16.03 is intentional. The
changes for master are in staging, but there's also mass darwin breakage
which noone addresses, so that's why it isn't merged to master yet.
https://github.com/NixOS/nixpkgs/commit/dd53c65dccb6#commitcomment-16668634

It's possible the darwin breakage is on 16.03 as well, as Hydra has no
darwin jobs for releases AFAIK.

--Vladimir




smime.p7s
Description: S/MIME Cryptographic Signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 16.03 in gcc5.3, master in gcc 4.9?

[Lluís Batlle i Rossell]

On Tue, Mar 22, 2016 at 10:12:39AM +0100, Pascal Wittmann wrote:
> On 03/22/2016 09:56 AM, Lluís Batlle i Rossell wrote:
> > why is release-16.03 in gcc 5.3 (hardening+staging merged in), and master
> > in gcc 4.9?
> > 
> > I don't understand. Should we put fixes for gcc5 builds into 16.03 and not
> > master?
> 
> I noticed that too when fixing some builds on release-16.03, but haven't
> got around to write a mail. I'll second that.

I think that someone merged into 16.03 instead of into master unwillingly.
An error. But did this pass unnoticed by the maintainers for more than 15
days?

It sounds strange to me.

The sooner we fix this, the better. :)

-- 
(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

Re: [Nix-dev] 16.03 in gcc5.3, master in gcc 4.9?

[Pascal Wittmann]

On 03/22/2016 09:56 AM, Lluís Batlle i Rossell wrote:
> why is release-16.03 in gcc 5.3 (hardening+staging merged in), and master
> in gcc 4.9?
> 
> I don't understand. Should we put fixes for gcc5 builds into 16.03 and not
> master?

I noticed that too when fixing some builds on release-16.03, but haven't
got around to write a mail. I'll second that.



signature.asc
Description: OpenPGP digital signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] 16.03 in gcc5.3, master in gcc 4.9?

[Lluís Batlle i Rossell]

Hello,

why is release-16.03 in gcc 5.3 (hardening+staging merged in), and master
in gcc 4.9?

I don't understand. Should we put fixes for gcc5 builds into 16.03 and not
master?

-- 
(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