From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What's the best way to force a particular version of a dependency
Date: Sun, 7 Jun 2020 17:20:18 -0400 [thread overview]
Message-ID: <CAGfcS_k0=mqjJsDrVev9WX-_cKUiV0xp7yPH_74af3f2n7OgOQ@mail.gmail.com> (raw)
In-Reply-To: <f77d4dec-3f29-4dd2-5d57-fd990e664957@gmail.com>
On Sun, Jun 7, 2020 at 5:07 PM Dale <rdalek1967@gmail.com> wrote:
>
>
> Unless you have a really good reason to do so, you shouldn't try to update system by itself. It limits emerge and can lead to issues.
He's just following my earlier advice. While what you say is true in
general, the problem is that he is trying to update a system that
hasn't been updated in ages, and so he probably needs to adjust dozens
of USE flags/etc or make other tweaks to fix things. Using @system
reduces the scope of the update to try to at least get the core system
updated, but you're right that this might need to be augmented with
other packages.
Really though part of the problem here is that each time there is a
problem I'm seeing about 10 lines of portage output, when I probably
need 500 lines to figure out what is likely going on. Half the battle
of the bug wranglers is getting people to just post all the stuff that
the new bug form asks you to attach - we don't ask for thousands of
lines of logs because we have nothing better to read... :)
--
Rich
next prev parent reply other threads:[~2020-06-07 21:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 18:16 [gentoo-user] What's the best way to force a particular version of a dependency n952162
2020-06-07 18:33 ` Rich Freeman
2020-06-07 18:56 ` n952162
2020-06-07 19:30 ` Rich Freeman
2020-06-07 19:38 ` n952162
2020-06-07 21:03 ` Mark Knecht
2020-06-07 21:15 ` n952162
2020-06-07 21:20 ` Mark Knecht
2020-06-07 21:16 ` Rich Freeman
2020-06-08 9:12 ` Peter Humphrey
2020-06-08 9:18 ` Neil Bothwick
2020-06-08 9:34 ` Peter Humphrey
2020-06-07 20:12 ` n952162
2020-06-07 21:07 ` Dale
2020-06-07 21:20 ` Rich Freeman [this message]
2020-06-07 21:33 ` Dale
2020-06-07 21:30 ` J. Roeleveld
2020-06-07 21:37 ` Dale
2020-06-07 21:45 ` n952162
2020-06-07 22:22 ` Dale
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='CAGfcS_k0=mqjJsDrVev9WX-_cKUiV0xp7yPH_74af3f2n7OgOQ@mail.gmail.com' \
--to=rich0@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