On Fri, 2006-04-21 at 11:24 -0700, Richard Fish wrote:
On 4/21/06, Johám-Luís Miguéns Vila [EMAIL PROTECTED] wrote:
On 09:09 Fri 21 Apr , Jules Colding wrote:
emerge (1 of 1) sys-apps/slocate-2.7-r8 to /
!!! Files listed in the manifest do not exist!
slocate-3.1.ebuild
On 22:27 Fri 21 Apr , Neil Bothwick wrote:
On Fri, 21 Apr 2006 11:24:11 -0700, Richard Fish wrote:
su -c ebuild /path/to/slocate-2.7-r8.ebuild digest;emerge --verbose
--ask slocate
or even emerge --verbose --ask --digest slocate
Didn't know about '--digest' switch... As I'm
On 21/04/06, Neil Bothwick [EMAIL PROTECTED] wrote:
On Fri, 21 Apr 2006 11:24:11 -0700, Richard Fish wrote:
su -c ebuild /path/to/slocate-2.7-r8.ebuild digest;emerge --verbose
--ask slocate
or even emerge --verbose --ask --digest slocate
But do an emerge --sync first. The most likely
Hi,
A few moments ago I tried to emerge slocate but got:
#
omc-2 ~ # emerge -va sys-apps/slocate
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N] sys-apps/slocate-2.7-r8 0 kB
Total size of downloads: 0 kB
Do you
I know it's not quite the answer you asked for, but might I suggest rlocate.
rlocate uses a kernel module to do real-time updates of the locate
database (uses very little cpu time), which as well as providing
instant indexing of new files reduces the complete hard drive trawl
from once a day to
On 09:09 Fri 21 Apr , Jules Colding wrote:
Hi,
A few moments ago I tried to emerge slocate but got:
#
omc-2 ~ # emerge -va sys-apps/slocate
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N]
On 4/21/06, Johám-Luís Miguéns Vila [EMAIL PROTECTED] wrote:
On 09:09 Fri 21 Apr , Jules Colding wrote:
emerge (1 of 1) sys-apps/slocate-2.7-r8 to /
!!! Files listed in the manifest do not exist!
slocate-3.1.ebuild
files/digest-slocate-3.1
omc-2 ~ #
su -c ebuild
On 11:24 Fri 21 Apr , Richard Fish wrote:
But do an emerge --sync first. The most likely cause of this is that
your last sync was done while the server was being updated, and you
got the updated manifest but not the ebuild. These kinds of problems
are almost always fixed by a new sync.
On Fri, 21 Apr 2006 11:24:11 -0700, Richard Fish wrote:
su -c ebuild /path/to/slocate-2.7-r8.ebuild digest;emerge --verbose
--ask slocate
or even emerge --verbose --ask --digest slocate
But do an emerge --sync first. The most likely cause of this is that
your last sync was done while the
9 matches
Mail list logo