From: Mike Kazantsev <mk.fraggod@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage Patch failed to apply - System will no longer upgrade
Date: Mon, 8 Jun 2009 15:01:49 +0600 [thread overview]
Message-ID: <20090608150149.2c34724d@coercion> (raw)
In-Reply-To: <cKHMl-4O4-7@gated-at.bofh.it>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On Mon, 08 Jun 2009 09:50:09 +0200
Rod <Rod@Rods.id.au> wrote:
> For this package and everything else I wish to apply, this is
> locking my system in time so I can no longer upgrade any software ;o(
You can use "emerge --keep-going" flag for portage-2.2 or
"emerge --resume --skip-first" for earlier versions to update
everything else.
There's also some simple sh-scripts for emulating "--keep-going"
functionality for earlier portage versions. I can't remember any
specific names, but I'm sure google should be able to help here.
If the problem is specific to this exact version of package (gmp
usually builds, but 4.3.1 fails) and the update itself is not critical
to you (like when you don't even know what it'll bring) then you can
just ignore it altogether - there's a good chance 4.3.2 or 4.4.0 or
whatever-next-version-is will compile cleanly.
--
Mike Kazantsev // fraggod.net
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next parent reply other threads:[~2009-06-08 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cKHMl-4O4-7@gated-at.bofh.it>
2009-06-08 9:01 ` Mike Kazantsev [this message]
2009-06-07 17:02 [gentoo-user] Portage Patch failed to apply - System will no longer upgrade Rod
2009-06-08 8:10 ` Alan McKinnon
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=20090608150149.2c34724d@coercion \
--to=mk.fraggod@gmail.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