| 1 |
José Fonseca wrote: |
| 2 |
> On Tue, Nov 12, 2002 at 12:42:41AM +0100, Johannes Ball? wrote: |
| 3 |
> |
| 4 |
>>Am Monday 11 November 2002 21:38 schrieb José Fonseca: |
| 5 |
>> |
| 6 |
|
| 7 |
>> |
| 8 |
>>sed: can't read /usr/portage/metadata/cache/sys-kernel/linux-headers-2.4.19: |
| 9 |
>>No such file or directory |
| 10 |
> |
| 11 |
> [...] |
| 12 |
> |
| 13 |
> These are packages which were installed from your '/usr/local/portage' |
| 14 |
> or were removed from portage. |
| 15 |
|
| 16 |
I ran "emerge linux-headers" |
| 17 |
emerge (1 of 1) sys-kernel/linux-headers-2.4.19 |
| 18 |
|
| 19 |
/var/db/pkg/sys-kernel/linux-headers-2.4.19 exists |
| 20 |
/usr/portage/metadata/cache/sys-kernel/linux-headers-2.4.19 does not exist |
| 21 |
|
| 22 |
/var/db/pkg/sys-kernel/linux-headers-2.4.18 does not exist |
| 23 |
/usr/portage/metadata/cache/sys-kernel/linux-headers-2.4.18 exists |
| 24 |
|
| 25 |
it seems strange to me. the cache is not up to date. |
| 26 |
Is there a way to force the ebuild of the cache ? |
| 27 |
|
| 28 |
> I could write a variation of the script without these shortcomings - |
| 29 |
> that actually read the installed ebuilds which is *much* slower. I |
| 30 |
> personally don't need it as I only have little stuff in |
| 31 |
> /usr/local/portage |
| 32 |
> |
| 33 |
> If there is enough interest I'll add a couple of operation modes to the |
| 34 |
> script: "dummy", and "safe"; to make a dry-run and/or a safe evaluation |
| 35 |
> of the installed packages repectively. |
| 36 |
|
| 37 |
I'd have enough interest :-) . I never do an emerge whatever without "-p" |
| 38 |
first. even if this data is not lost forever I have the habit of |
| 39 |
checking first. |
| 40 |
|
| 41 |
Marko |
| 42 |
|
| 43 |
|
| 44 |
-- |
| 45 |
gentoo-dev@g.o mailing list |
Archives