From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge --update : how to keep it going?
Date: Fri, 30 Nov 2012 11:44:30 -0500 [thread overview]
Message-ID: <50B8E26E.6020907@orlitzky.com> (raw)
In-Reply-To: <1775646.4xJNIhJhce@atom>
On 11/30/12 08:05, 2sb7vwu@gmail.com wrote:
>
>> Hi,
>> this is nuissance all the time.
>>
>> Updating a machine which hasn't been updated for a long(er) time I try
>>
>> emerge -vup --changed-use --deep --tree --with-bdeps y @system
>> @world >/root/UPD
>>
>> But many times this stops prematurely with messages like
>>
>> emerge: there are no ebuilds to satisfy
>> ">=app-text/poppler-bindings-0.5.0"
>>
>> How can I keep emerge going and tell me these message all at once in
>> the end?
>
> Get
> ANGRY
> and
> --keep-going
> :)
Now all we need is,
emerge --i-dont-care
for when you have 100 packages ready to be updated and one stupid ruby
package has conflicting dependencies.
next prev parent reply other threads:[~2012-11-30 16:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 12:26 [gentoo-user] emerge --update : how to keep it going? Helmut Jarausch
2012-11-30 12:42 ` Francisco Ares
2012-11-30 12:43 ` Michael Mol
2012-11-30 12:46 ` Dale
2012-11-30 12:52 ` Yohan Pereira
2012-11-30 13:05 ` 2sb7vwu
2012-11-30 16:44 ` Michael Orlitzky [this message]
2012-12-01 13:02 ` 2sb7vwu
2012-12-01 18:56 ` Volker Armin Hemmann
2012-12-01 19:58 ` Graham Murray
2012-12-01 20:19 ` Mark Knecht
2012-12-01 20:30 ` Volker Armin Hemmann
2012-12-02 14:12 ` Alan McKinnon
2012-12-02 14:58 ` kwkhui
2012-11-30 17:53 ` Keith Dart
2012-11-30 18:01 ` Helmut Jarausch
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=50B8E26E.6020907@orlitzky.com \
--to=michael@orlitzky.com \
--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