From: n952162 <n952162@web.de>
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 22:12:40 +0200 [thread overview]
Message-ID: <67186c99-d5be-ffa1-f280-e40c952e6cb0@web.de> (raw)
In-Reply-To: <CAGfcS_nXe-tprpNCXDJs0ShJ1DfjdJJ3g=Z0jxQVBnwTuxHBiA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
On 2020-06-07 21:30, Rich Freeman wrote:
> On Sun, Jun 7, 2020 at 2:56 PM n952162 <n952162@web.de> wrote:
>
>> The emerge that I used was this:
>>
>> emerge -auDv --verbose-conflicts --changed-use --keep-going --with-bdeps=y --changed-deps --backtrack=100 @system
> Yeah, you might have to include the other packages that need readline
> if portage complains.
>
>
This, indeed, seems to have been the magic.
By specifying *both* @system and @world, two of my machines that I
worried were lost-causes are now updating - hundreds of packages, but
that's okay, I've been pulling my hair out for months.
[-- Attachment #2: Type: text/html, Size: 1253 bytes --]
next prev parent reply other threads:[~2020-06-07 20:17 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 [this message]
2020-06-07 21:07 ` Dale
2020-06-07 21:20 ` Rich Freeman
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=67186c99-d5be-ffa1-f280-e40c952e6cb0@web.de \
--to=n952162@web.de \
--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