From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: grub-0.97-r16 and profile 17.0 change
Date: Sat, 2 Dec 2017 20:14:52 -0500 [thread overview]
Message-ID: <98a28150-b609-19d9-04cb-2943ce870217@gentoo.org> (raw)
In-Reply-To: <20171203020757.3ac1810f@lexx>
On 12/02/2017 08:07 PM, Heiko Baums wrote:
> Am Sat, 2 Dec 2017 18:33:09 -0500
> schrieb Michael Orlitzky <mjo@gentoo.org>:
>
>> You're seeing a lot of reports because there is a news item telling
>> people to switch to the new profile and run "emerge -e @world".
>
> Does this mean that "emerge -e @world" should be run or that the news
> item is wrong in this point?
You do need to run "emerge -e @world", unless you happened to be using a
hardened toolchain already.
So the news item is correct, but having everyone build test the whole
tree at once is unearthing some latent build system bugs.
next prev parent reply other threads:[~2017-12-03 1:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 12:30 [gentoo-user] grub-0.97-r16 and profile 17.0 change Mick
2017-12-02 21:28 ` [gentoo-user] " Ian Zimmerman
2017-12-02 23:28 ` Mick
2017-12-03 2:11 ` Adam Carter
2017-12-02 23:33 ` Michael Orlitzky
2017-12-03 1:07 ` Heiko Baums
2017-12-03 1:14 ` Michael Orlitzky [this message]
2017-12-03 2:18 ` Ian Zimmerman
2017-12-03 2:27 ` Michael Orlitzky
2017-12-03 10:57 ` [gentoo-user] " Peter Humphrey
2017-12-03 15:12 ` Mick
2017-12-05 1:54 ` Daniel Frey
2017-12-05 2:13 ` Daniel Frey
2017-12-05 2:15 ` Michael Orlitzky
2017-12-05 3:39 ` Daniel Frey
2017-12-05 10:15 ` Peter Humphrey
2017-12-05 10:44 ` Tom H
2017-12-05 7:06 ` [gentoo-user] " Ian Zimmerman
2017-12-05 2:20 ` [gentoo-user] " wabe
2017-12-05 10:11 ` Mick
2017-12-05 10:21 ` Raffaele Belardi
2017-12-05 12:48 ` Mick
2017-12-06 1:58 ` wabe
2017-12-06 12:28 ` Peter Humphrey
2017-12-07 12:04 ` Kai Peter
2017-12-07 14:22 ` Peter Humphrey
2017-12-07 15:06 ` Helmut Jarausch
2017-12-07 16:51 ` Kai Peter
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=98a28150-b609-19d9-04cb-2943ce870217@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-user@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