| 1 |
On Mon, 08 Jun 2009 09:50:09 +0200 |
| 2 |
Rod <Rod@×××××××.au> wrote: |
| 3 |
|
| 4 |
> For this package and everything else I wish to apply, this is |
| 5 |
> locking my system in time so I can no longer upgrade any software ;o( |
| 6 |
|
| 7 |
You can use "emerge --keep-going" flag for portage-2.2 or |
| 8 |
"emerge --resume --skip-first" for earlier versions to update |
| 9 |
everything else. |
| 10 |
There's also some simple sh-scripts for emulating "--keep-going" |
| 11 |
functionality for earlier portage versions. I can't remember any |
| 12 |
specific names, but I'm sure google should be able to help here. |
| 13 |
|
| 14 |
If the problem is specific to this exact version of package (gmp |
| 15 |
usually builds, but 4.3.1 fails) and the update itself is not critical |
| 16 |
to you (like when you don't even know what it'll bring) then you can |
| 17 |
just ignore it altogether - there's a good chance 4.3.2 or 4.4.0 or |
| 18 |
whatever-next-version-is will compile cleanly. |
| 19 |
|
| 20 |
-- |
| 21 |
Mike Kazantsev // fraggod.net |
Archives