| 1 |
On 05/09/2010 11:54 AM, Volker Armin Hemmann wrote: |
| 2 |
|
| 3 |
> and walt: |
| 4 |
> preserved libs. Look into it. |
| 5 |
|
| 6 |
A long time ago, maybe one or two years ago, an occasional package |
| 7 |
would suggest that I should run emerge @preserved-rebuild to rebuild |
| 8 |
packages that are linked to obsolete libraries. |
| 9 |
|
| 10 |
This worked very well for a few months, and then those suggestions |
| 11 |
suddenly stopped coming. |
| 12 |
|
| 13 |
Since then, emerge @preserved-rebuild (or @preserved-libs) says this: |
| 14 |
|
| 15 |
#emerge @preserved-rebuild |
| 16 |
!!! '@preserved-rebuild' is not a valid package atom. |
| 17 |
!!! Please check ebuild(5) for full details. |
| 18 |
|
| 19 |
I get the same error on my x86 and ~amd64 machines, i.e. with either |
| 20 |
baselayout-1 or baselayout-2. The man pages for ebuild, emerge, |
| 21 |
portage, and make.conf say nothing about 'preserved'. |
| 22 |
|
| 23 |
Anyone have an idea what changed, or what I'm doing wrong? |
Archives