From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-80307-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by finch.gentoo.org (Postfix) with ESMTPS id 1A983139694
for <garchives@archives.gentoo.org>; Tue, 18 Apr 2017 14:40:11 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 26134E0CCE;
Tue, 18 Apr 2017 14:40:04 +0000 (UTC)
Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::22e])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id C1F51E0CB8
for <gentoo-dev@lists.gentoo.org>; Tue, 18 Apr 2017 14:40:03 +0000 (UTC)
Received: by mail-pf0-x22e.google.com with SMTP id 194so42691907pfv.3
for <gentoo-dev@lists.gentoo.org>; Tue, 18 Apr 2017 07:40:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=vu4IoMr14tm7mmlBjWEUlMI0zKCtKCf+0ELb5s3hWvs=;
b=jt4TCGO8EYHDIUCCaPKRTShc98XEPEjad3m4LAk9s4TNxZHbBsXVi4yoMUUec/3TFS
nqz7sGvXdMI1HXYH7F6ywpg2ydJf3X++uMzTcAGu4ML3itXMPdSkAkCRKn58kxf/1qQN
q9ToIaZYIgA/gTb6gGx2+0tZCs/aYNrcNQp7kvvRsCOZvKgx65Kg8aLtjYlzGK86y8Sp
XJtTGgrIM8IMWRJI1s91mfE8ov+W2Dju06/jSxYf47s+TjdxCgBT8SIMPptFh7qoujMM
QDcvCkL9oVJpUC/U4F/rzLIq9ZxKdm6wtHY3BuL+J8RG3U9Ws4Ju8CUUwiH661wd1kR4
8bvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to;
bh=vu4IoMr14tm7mmlBjWEUlMI0zKCtKCf+0ELb5s3hWvs=;
b=kj+ElxnVot9UV9umRX7aH7RKCKeC6D1uBQ1SlQSF6lCKDDAwzHsie6xhv1NyIk2XK3
3P+Gyxezl3358AEwfDj0kjLj0cvoNSJTCx8myWA48WAASAkSRUdrh6B2KLurrd+lbkpT
k4WyvrnrS/fbYozJTkrbm5BYheo1zyVlD3OdT+bhISHrBX/gP42ail6gfFwQh83Gk2ar
ctsPI/1FXdMqN+eIoyIgqrQDfb8H/TPEsliy1BAf0F3d13U+UUrJPX9/ic9iajNPiwpU
YSvqbZk57B7LSxp15ccczoqaOlFU3/DesspO2ta7YEU8boHDKPS28YzNiq6o9EQW3dLY
h8Iw==
X-Gm-Message-State: AN3rC/7+8KBKAQv9WA9fEPwPuL1YuisFPn2R2v5Cyq+V0T/rjx6fWAZS
4fZCsvSA+zHnAvfwlWI1rmpcW5JWliOR
X-Received: by 10.98.49.70 with SMTP id x67mr17968361pfx.177.1492526402588;
Tue, 18 Apr 2017 07:40:02 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.100.135.8 with HTTP; Tue, 18 Apr 2017 07:40:02 -0700 (PDT)
In-Reply-To: <od53hf$510$1@blaine.gmane.org>
References: <od4i5u$h86$1@blaine.gmane.org> <CAG6MAzSUqBS-qzRmETT3u48B=KXBQ0KjMQPqXLO=JDBmKjiv+g@mail.gmail.com>
<od4ln4$a1r$1@blaine.gmane.org> <CAG6MAzQoNpv38jwQmEqtjd60R3=wN1nnfRFN7oF-c7KnR2F9eQ@mail.gmail.com>
<od53hf$510$1@blaine.gmane.org>
From: Tomas Mozes <hydrapolic@gmail.com>
Date: Tue, 18 Apr 2017 16:40:02 +0200
Message-ID: <CAG6MAzR_oYAc4jFMHCHv5oZYFkBU29OV=E3zxc2SGLa-vrjRDw@mail.gmail.com>
Subject: Re: [gentoo-dev] Re: Re: stable gcc 5.4.0 ??
To: gentoo-dev@lists.gentoo.org
Content-Type: multipart/alternative; boundary=94eb2c12388a0b5534054d71e2c3
X-Archives-Salt: 0dca6e52-4e25-46ec-874b-57bb6b831f94
X-Archives-Hash: 7ed60d97adf6ba8679e094140d1bfa80
--94eb2c12388a0b5534054d71e2c3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Tue, Apr 18, 2017 at 3:12 PM, J=C3=B6rg Schaible <
joerg.schaible@bpm-inspire.com> wrote:
> Tomas Mozes wrote:
>
> [snip]
>
> > As mentioned by others, bugs on packages.gentoo.org will not affect you=
r
> > portage tree. I've just installed gcc 5.4.0-r3 on amd64, so try syncing
> > your portage tree. Don't you have it in your package.mask?
>
> As said, I synced the tree twice this morning (4 hours ago) and the
> KEYWORDS
> in the ebuild do not declare amd64 as stable although it was committed to
> GIT already yesterday. And this is no wonder, because the stable branch o=
f
> the GIT mirror is still not up-to-date:
> https://github.com/gentoo-mirror/gentoo/tree/stable/sys-devel/gcc
>
> gcc-4.5.0-r3 is declared unstable and is not masked.
>
> Cheers,
> J=C3=B6rg
>
>
>
According to git
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3De2be964b72fce0cdb7c1=
6a378b4fa3fa1d37ee38
- the KEYWORDS have amd64 and x86. The github mirror shows the same
https://raw.githubusercontent.com/gentoo-mirror/gentoo/stable/sys-devel/gcc=
/gcc-5.4.0-r3.ebuild.
Syncing the tree shows the same.
And as such, on a stable system:
# emerge -p gcc
[ebuild NS ] sys-devel/gcc-5.4.0-r3:5.4.0::gentoo [4.9.4:4.9.4::gentoo]
USE=3D"cxx fortran (multilib) nptl openmp sanitize vtv (-altivec) (-awt)
-cilk -debug -doc (-fixed-point) -gcj -go -graphite (-hardened) (-jit)
(-libssp) -mpx -nls -nopie -nossp -objc -objc++ -objc-gc -regression-test
-vanilla" 0 KiB
The git message says it's stable, the bug report also, the mirrors too, so
yes, it is stable now. Maybe check another rsync mirror.
--94eb2c12388a0b5534054d71e2c3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Apr 18, 2017 at 3:12 PM, J=C3=B6rg Schaible <span dir=3D"ltr">&=
lt;<a href=3D"mailto:joerg.schaible@bpm-inspire.com" target=3D"_blank">joer=
g.schaible@bpm-inspire.com</a>></span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">Tomas Mozes wrote:<br>
<br>
[snip]<br>
<span class=3D"gmail-"><br>
> As mentioned by others, bugs on <a href=3D"http://packages.gentoo.org"=
rel=3D"noreferrer" target=3D"_blank">packages.gentoo.org</a> will not affe=
ct your<br>
> portage tree. I've just installed gcc 5.4.0-r3 on amd64, so try sy=
ncing<br>
> your portage tree. Don't you have it in your package.mask?<br>
<br>
</span>As said, I synced the tree twice this morning (4 hours ago) and the =
KEYWORDS<br>
in the ebuild do not declare amd64 as stable although it was committed to<b=
r>
GIT already yesterday. And this is no wonder, because the stable branch of<=
br>
the GIT mirror is still not up-to-date:<br>
<a href=3D"https://github.com/gentoo-mirror/gentoo/tree/stable/sys-devel/gc=
c" rel=3D"noreferrer" target=3D"_blank">https://github.com/gentoo-<wbr>mirr=
or/gentoo/tree/stable/sys-<wbr>devel/gcc</a><br>
<br>
gcc-4.5.0-r3 is declared unstable and is not masked.<br>
<br>
Cheers,<br>
J=C3=B6rg<br>
<br>
<br>
</blockquote></div><br></div><div class=3D"gmail_extra">According to git <a=
href=3D"https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3De2be964b72f=
ce0cdb7c16a378b4fa3fa1d37ee38">https://gitweb.gentoo.org/repo/gentoo.git/co=
mmit/?id=3De2be964b72fce0cdb7c16a378b4fa3fa1d37ee38</a> - the KEYWORDS have=
amd64 and x86. The github mirror shows the same <a href=3D"https://raw.git=
hubusercontent.com/gentoo-mirror/gentoo/stable/sys-devel/gcc/gcc-5.4.0-r3.e=
build">https://raw.githubusercontent.com/gentoo-mirror/gentoo/stable/sys-de=
vel/gcc/gcc-5.4.0-r3.ebuild</a>. Syncing the tree shows the same.<br><br></=
div><div class=3D"gmail_extra">And as such, on a stable system:<br><br># em=
erge -p gcc<br>[ebuild=C2=A0 NS=C2=A0=C2=A0=C2=A0 ] sys-devel/gcc-5.4.0-r3:=
5.4.0::gentoo [4.9.4:4.9.4::gentoo] USE=3D"cxx fortran (multilib) nptl=
openmp sanitize vtv (-altivec) (-awt) -cilk -debug -doc (-fixed-point) -gc=
j -go -graphite (-hardened) (-jit) (-libssp) -mpx -nls -nopie -nossp -objc =
-objc++ -objc-gc -regression-test -vanilla" 0 KiB<br><br></div><div cl=
ass=3D"gmail_extra">The git message says it's stable, the bug report al=
so, the mirrors too, so yes, it is stable now. Maybe check another rsync mi=
rror.<br></div></div>
--94eb2c12388a0b5534054d71e2c3--