| 1 |
Mick <michaelkintzios@×××××.com> wrote: |
| 2 |
|
| 3 |
>On 21/04/06, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 4 |
>> On Fri, 21 Apr 2006 11:24:11 -0700, Richard Fish wrote: |
| 5 |
>> |
| 6 |
>> > > su -c "ebuild /path/to/slocate-2.7-r8.ebuild digest;emerge --verbose |
| 7 |
>> > > --ask slocate" |
| 8 |
>> |
| 9 |
>> or even "emerge --verbose --ask --digest slocate" |
| 10 |
>> |
| 11 |
>> > But do an emerge --sync first. The most likely cause of this is that |
| 12 |
>> > your last sync was done while the server was being updated, and you |
| 13 |
>> > got the updated manifest but not the ebuild. These kinds of problems |
| 14 |
>> > are almost always fixed by a new sync. Using the digest command is |
| 15 |
>> > overkill. |
| 16 |
>> |
| 17 |
>> Not to mention potentially dangerous. If the digest mismatch is a fault |
| 18 |
>> in portage, a sync will usually fix it. But if it is due to a compromised |
| 19 |
>> archive, redigesting removes that safety check. |
| 20 |
> |
| 21 |
>I don't think this is related, but this is what I got in the last |
| 22 |
>update to sys-apps/slocate-2.7-r8: |
| 23 |
>=================================== |
| 24 |
> The 'slocate' group has been renamed to 'locate'. |
| 25 |
> You seem to already have a 'slocate' group. |
| 26 |
> Please rename it: |
| 27 |
> groupmod -n locate slocate |
| 28 |
>=================================== |
| 29 |
>Renaming it allows the ebuild to complete as suggested. |
| 30 |
|
| 31 |
I got that same error when I did the upgrade. Once I renamed it also, |
| 32 |
the ebuild completed fine. |
| 33 |
|
| 34 |
Jeff |
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-user@g.o mailing list |
Archives