[gentoo-user] What do I do about slocate 3.1/2.7 ?

[gentoo-user] What do I do about slocate 3.1/2.7 ?

[Jules Colding]

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 want me to merge these packages? [Yes/No] yes
>>> 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 ~ #
#########################


How do I fix that one?

Thanks,
  jules


############## emerge --info #################
omc-2 ~ # emerge --info
Portage 2.0.54 (default-linux/amd64/2006.0, gcc-3.4.5, glibc-2.3.5-r2, 2.6.15-gentoo-r7 x86_64)
=================================================================
System uname: 2.6.15-gentoo-r7 x86_64 AMD Opteron(tm) Processor 252
Gentoo Base System version 1.6.14
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=k8 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://pandemonium.tiscali.de/pub/gentoo/ ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo http://mirror.gentoo.no/ http://gentoo.prz.rzeszow.pl http://ftp.du.se/pub/os/gentoo ftp://mirror.pudas.net/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="amd64 X aac aalib alsa apache2 audiofile avi berkdb bitmap-fonts browserplugin bzip2 cdr cli crypt cups curl dri dvd dvdr dvdread eds emacs emboss encode esd exif expat fam fbcon foomaticdb fortran gd gdbm gif glut gnome gpm gstreamer gtk gtk2 gtkhtml hal iconv idn imlib ipv6 isdnlog java jpeg lcms ldap libwww lua lzw lzw-tiff mad mng motif mozilla mp3 mpeg ncurses nls nptl nptlonly nsplugin nvidia ogg opengl oss pam pcre pdflib perl png pppd python quicktime readline recode reflection sdl session slang spell spl ssl tcltk tcpd tetex theora tiff truetype truetype-fonts type1-fonts udev unicode usb vorbis wma xine xml2 xmms xpm xv xvid zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] What do I do about slocate 3.1/2.7 ?

[Thomas Kear]

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 once a month.

http://rlocate.sf.net

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] What do I do about slocate 3.1/2.7 ?

[Johám-Luís Miguéns Vila]

[-- Attachment #1: Type: text/plain, Size: 893 bytes --]

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    ] sys-apps/slocate-2.7-r8  0 kB
> 
> Total size of downloads: 0 kB
> 
> Do you want me to merge these packages? [Yes/No] yes
> >>> 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 ~ #
> #########################
> 
> 
> How do I fix that one?
> 
> Thanks,
>   jules
> 


su -c "ebuild /path/to/slocate-2.7-r8.ebuild digest;emerge --verbose
--ask slocate"

Hope that works. Cheers.
-- 
A ouvir (mpd): Sonic Youth - Free City Rhymes
 - GPG KeyID:0x9D2FD6C8

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] What do I do about slocate 3.1/2.7 ?

[Richard Fish]

On 4/21/06, Johám-Luís Miguéns Vila <galiza.ceive@gmail.com> 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 /path/to/slocate-2.7-r8.ebuild digest;emerge --verbose
> --ask slocate"
>

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.  Using the digest command is
overkill.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] What do I do about slocate 3.1/2.7 ?

[Johám-Luís Miguéns Vila]

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

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.  Using the digest command is
> overkill.
> 
> -Richard
> 
> -- 
> gentoo-user@gentoo.org mailing list
> 

You are right.

Cheers.
-- 
A ouvir (mpd): Moby - Move The Colors (From The Br..
 - GPG KeyID:0x9D2FD6C8

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] What do I do about slocate 3.1/2.7 ?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 796 bytes --]

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 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.  Using the digest command is
> overkill.

Not to mention potentially dangerous. If the digest mismatch is a fault
in portage, a sync will usually fix it. But if it is due to a compromised
archive, redigesting removes that safety check.


-- 
Neil Bothwick

If your VCR still flashes 12:00 - then Linux is not for you.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] What do I do about slocate 3.1/2.7 ?

[Johám-Luís Miguéns Vila]

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

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 playing with some CVS/SVN
overlays it's really useful for me.

> > 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.  Using the digest command is
> > overkill.
> 
> Not to mention potentially dangerous. If the digest mismatch is a fault
> in portage, a sync will usually fix it. But if it is due to a compromised
> archive, redigesting removes that safety check.
> 

Yes, It was definitely a bad bad answer by me. The "Files listed in the
manifest do not exist" claims for a resync and not for a redigest.
I rarely has sync issues . Whenever I had digest issues they were related to SVN/CVS overlays,
so redigesting is safe there, AFAIK.
My apologies to thread starter.

Cheers.
-- 
A ouvir (mpd): Dirty Three - Jim's Dog
 - GPG KeyID:0x9D2FD6C8

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] What do I do about slocate 3.1/2.7 ?

[Mick]

On 21/04/06, Neil Bothwick <neil@digimed.co.uk> 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 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.  Using the digest command is
> > overkill.
>
> Not to mention potentially dangerous. If the digest mismatch is a fault
> in portage, a sync will usually fix it. But if it is due to a compromised
> archive, redigesting removes that safety check.

I don't think this is related, but this is what I got in the last
update to sys-apps/slocate-2.7-r8:
===================================
 The 'slocate' group has been renamed to 'locate'.
 You seem to already have a 'slocate' group.
 Please rename it:
 groupmod -n locate slocate
===================================
Renaming it allows the ebuild to complete as suggested.

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: What do I do about slocate 3.1/2.7 ?

[Jeff Grossman]

Mick <michaelkintzios@gmail.com> wrote:

>On 21/04/06, Neil Bothwick <neil@digimed.co.uk> 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 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.  Using the digest command is
>> > overkill.
>>
>> Not to mention potentially dangerous. If the digest mismatch is a fault
>> in portage, a sync will usually fix it. But if it is due to a compromised
>> archive, redigesting removes that safety check.
>
>I don't think this is related, but this is what I got in the last
>update to sys-apps/slocate-2.7-r8:
>===================================
> The 'slocate' group has been renamed to 'locate'.
> You seem to already have a 'slocate' group.
> Please rename it:
> groupmod -n locate slocate
>===================================
>Renaming it allows the ebuild to complete as suggested.

I got that same error when I did the upgrade.  Once I renamed it also,
the ebuild completed fine.

Jeff

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] What do I do about slocate 3.1/2.7 ?

[Jules Colding]

On Fri, 2006-04-21 at 11:24 -0700, Richard Fish wrote:
> On 4/21/06, Johám-Luís Miguéns Vila <galiza.ceive@gmail.com> 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 /path/to/slocate-2.7-r8.ebuild digest;emerge --verbose
> > --ask slocate"
> >
> 
> 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.  

Yes, it was. I sync'ed a few hours later and the problem went away.

Thanks,
  jules



-- 
gentoo-user@gentoo.org mailing list