Bug#345646: slocate: Please provide a NEWS file announcing important changes

On 2006-01-06 09:35:49 -0800, Kevin Lindsay wrote: > Ok, thanks. The fix will be in the next upload, which should be > today sometime. There are still problems (worse?). I've just reported a new bug. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% accessible validated

Bug#345646: slocate: Please provide a NEWS file announcing important changes

On Fri, Jan 06, 2006 at 09:49:39AM +0100, Vincent Lefevre wrote: > On a non-Debian machine: > > tate:~> slocate --version > Secure Locate 2.7 - Released January 24, 2003 > tate:~> echo $LOCATE_PATH > /users/spaces/vlefevre/private/locate/home.db:/users/spaces/vlefevre/private/locate/logiciels.db

Bug#345646: slocate: Please provide a NEWS file announcing important changes

On 2006-01-05 21:08:20 -0800, Kevin Lindsay wrote: > oops, juse to be more clear, anything in the environment var LOCATE_PATH > will always be searched regardless. ie, > > This will search both db1.db and db2.db, but not the default database: > LOCATE_PATH=db1.db > slocate -d db2.db foo > > This

Bug#345646: slocate: Please provide a NEWS file announcing important changes

On Fri, Jan 06, 2006 at 04:53:09AM +0100, Vincent Lefevre wrote: > When LOCATE_PATH is defined, the databases in $LOCATE_PATH are > searched instead of the default one. > > Before the change, I was using > * "slocate" to search the default database. > * "slocate -d $LOCATE_PATH" to search th

Bug#345646: slocate: Please provide a NEWS file announcing important changes

On Fri, Jan 06, 2006 at 04:53:09AM +0100, Vincent Lefevre wrote: > When LOCATE_PATH is defined, the databases in $LOCATE_PATH are > searched instead of the default one. > > Before the change, I was using > * "slocate" to search the default database. > * "slocate -d $LOCATE_PATH" to search th

Bug#345646: slocate: Please provide a NEWS file announcing important changes

On 2006-01-05 16:06:30 -0800, Kevin Lindsay wrote: > There shouldn't have been a change, and this is a bug. What problem > have you specifically experienced? When LOCATE_PATH is defined, the databases in $LOCATE_PATH are searched instead of the default one. Before the change, I was using * "slo

Bug#345646: slocate: Please provide a NEWS file announcing important changes

There shouldn't have been a change, and this is a bug. What problem have you specifically experienced? Kevin- On Mon, Jan 02, 2006 at 03:34:57PM +0100, Vincent Lefevre wrote: > Package: slocate > Version: 3.0.beta.r1-1 > Severity: wishlist > > There has been an incompatible change concerning the

Bug#345646: slocate: Please provide a NEWS file announcing important changes

Package: slocate Version: 3.0.beta.r1-1 Severity: wishlist There has been an incompatible change concerning the LOCATE_PATH environment variable making slocate no longer work here; until I found this problem, I was wondering why. This kind of things should have been announced in a NEWS file (which