gutsy to hardy slocate dist-upgrade error

[marcobra (Marco Braida)]

Binary package hint: slocate

Dist upgrading Gutsy to Hardy give me this error:

Mi preparo a sostituire slocate 3.1-1ubuntu3 (con .../slocate_3.1-1.1ubuntu1_i386.deb) ...
===============================================
===Error. The following diversions still exist:
diversion of /usr/bin/locate to /usr/bin/locate.notslocate by slocate
diversion of /usr/bin/updatedb to /usr/bin/updatedb.notslocate by slocate
diversion of /usr/share/man/man1/locate.1.gz to /usr/share/man/man1/locate.notslocate.1.gz by slocate
diversion of /usr/share/man/man1/updatedb.1.gz to /usr/share/man/man1/updatedb.notslocate.1.gz by slocate
===============================================
dpkg: errore processando /var/cache/apt/archives/slocate_3.1-1.1ubuntu1_i386.deb (--unpack):
 il sottoprocesso pre-installation script ha restituito un codice di errore 1
Sono occorsi degli errori processando:
 /var/cache/apt/archives/slocate_3.1-1.1ubuntu1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

As a workaround i remove and purge slocate, then the dist-upgrade goes fine.
apt-get --purge remove slocate

HTH

[Anton Kraus (done)]

Got the same error message when installing last week's worth of Hardy packages.

Purging slocate and reinstalling it worked fine.

[Oz123 (nahumoz)]

Got the same error when upgrading today.
And solved by the above fix. However after reinstalling got the following warning:
Unpacking slocate (from .../slocate_3.1-1.1ubuntu1_i386.deb) ...
Adding `diversion of /usr/bin/locate to /usr/bin/locate.notslocate by slocate'
Adding `diversion of /usr/bin/updatedb to /usr/bin/updatedb.notslocate by slocate'
Adding `diversion of /usr/share/man/man1/locate.1.gz to /usr/share/man/man1/locate.notslocate.1.gz by slocate'
Adding `diversion of /usr/share/man/man1/updatedb.1.gz to /usr/share/man/man1/updatedb.notslocate.1.gz by slocate'
Adding `diversion of /etc/cron.daily/find to /etc/cron.daily/find.notslocate by slocate'
Setting up slocate (3.1-1.1ubuntu1) ...
Adding group `slocate' (GID 119) ...
Done.

WARNING: You should run '/etc/cron.daily/slocate' as root. locate will not work
properly until you do or until it is run by cron (it is daily).

[Christopher Blay (blayde)]

Oz123:
That just means you can't use 'locate' to find files until the database is rebuilt by cron (which would happen automatically within the next day).
If you want to use locate sooner than that, run 'sudo /etc/cron.daily/slocate' and it will work.