From: "Jörg Schaible" <joerg.schaible@bpm-inspire.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: stable gcc 5.4.0 ??
Date: Tue, 18 Apr 2017 15:12:13 +0200 [thread overview]
Message-ID: <od53hf$510$1@blaine.gmane.org> (raw)
In-Reply-To: CAG6MAzQoNpv38jwQmEqtjd60R3=wN1nnfRFN7oF-c7KnR2F9eQ@mail.gmail.com
Tomas Mozes wrote:
[snip]
> As mentioned by others, bugs on packages.gentoo.org will not affect your
> 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 of
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örg
next prev parent reply other threads:[~2017-04-18 13:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 8:15 [gentoo-dev] stable gcc 5.4.0 ?? Jörg Schaible
2017-04-18 8:37 ` Tomas Mozes
2017-04-18 9:16 ` [gentoo-dev] " Jörg Schaible
2017-04-18 9:44 ` Mart Raudsepp
2017-04-18 11:07 ` M. J. Everitt
2017-04-18 12:44 ` Tomas Mozes
2017-04-18 13:12 ` Jörg Schaible [this message]
2017-04-18 13:27 ` [gentoo-dev] " James Le Cuirot
2017-04-18 13:38 ` Aaron W. Swenson
2017-04-18 14:12 ` [gentoo-dev] " Jörg Schaible
2017-04-18 14:40 ` [gentoo-dev] " Tomas Mozes
2017-04-18 14:41 ` [gentoo-dev] " Tomas Mozes
2017-04-19 7:31 ` [gentoo-dev] " Jörg Schaible
2017-04-19 9:22 ` Tomas Mozes
2017-04-19 18:25 ` Walter Dnes
2017-04-20 5:36 ` Tomas Mozes
2017-04-20 22:17 ` Walter Dnes
2017-04-20 22:51 ` Mart Raudsepp
2017-04-20 22:52 ` Matthias Maier
2017-04-21 1:44 ` Walter Dnes
2017-04-21 16:21 ` [gentoo-dev] " Jörg Schaible
2017-04-21 19:29 ` Francesco Riosa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='od53hf$510$1@blaine.gmane.org' \
--to=joerg.schaible@bpm-inspire.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox