@r0lf I always wonder what it is that makes people suddenly find the
time to close tickets like this.
Almost 7 years after they have been reported.
Of course it's no longer relevant. The bloddy package has even been
removed over a year ago.
Thanks for the update though :) I hope it was a side e
Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as "Won't Fix".
** Changed in: slocate (Ubuntu Hardy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
This package has been removed from Ubuntu. Closing all related bugs.
** Changed in: slocate (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/189462
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: slocate (Ubuntu Hardy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/189462
Title:
** Changed in: slocate (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/189462
Title:
slocate cron job fails if /etc/updatedb.conf not found
To manage notif
My apologies that the Ubuntu team has taken so long to get around to
dealing with this bug.
Matt LaPlante: Thanks for your patch! My feeling is that causing
slocate to own /etc/updatedb.conf is probably not actually the best
approach here. Doing that introduces questions of upgrade handling (as
** Also affects: slocate (Ubuntu Hardy)
Importance: Undecided
Status: New
--
slocate cron job fails if /etc/updatedb.conf not found
https://bugs.launchpad.net/bugs/189462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
This bug is still open in Hardy, which is LTS.
** Changed in: slocate (Ubuntu)
Status: Invalid => Confirmed
--
slocate cron job fails if /etc/updatedb.conf not found
https://bugs.launchpad.net/bugs/189462
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: patch
--
slocate cron job fails if /etc/updatedb.conf not found
https://bugs.launchpad.net/bugs/189462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
I'm closing this bug because there is no slocate package in Karmic as
commented in comment 7.
** Changed in: slocate (Ubuntu)
Status: Confirmed => Invalid
--
slocate cron job fails if /etc/updatedb.conf not found
https://bugs.launchpad.net/bugs/189462
You received this bug notification be
papukaija wrote:
> Do we need to keep this bug open?
>
>
Not according to me. This was an upgrade issue for me (breaking my
scripts because of unannounced swtich from slocate to mlocate, breaking
slocate install as well).
There has been another distrelease since so
Seth
--
slocate cron j
Do we need to keep this bug open?
--
slocate cron job fails if /etc/updatedb.conf not found
https://bugs.launchpad.net/bugs/189462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
So should this bug marked as fix released/committed?
--
slocate cron job fails if /etc/updatedb.conf not found
https://bugs.launchpad.net/bugs/189462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Is this bug fixed in Karmic? Should this bug be included in "One Hundred
Paper Cuts" ?
--
slocate cron job fails if /etc/updatedb.conf not found
https://bugs.launchpad.net/bugs/189462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
Matt, I tried the package from your PPA on my Hardy server, it worked
perfectly well!
I had:
slocate:
Installé : 3.1-1.1ubuntu3
and now:
slocate:
Installé : 3.1-1.1ubuntu4~4
And here's some proofs (sorry for the French, dpkg went perfectly fine):
$ sudo dpkg -i slocate_3.1-1.1ubuntu4~4_amd64
To summarize the situation:
The README.debian in slocate claims that "Secure Locate uses
/etc/updatedb.conf which is packaged in 'findutils'. This file is not
packaged with Secure Locate." That's all well and good, except evidence
indicates that findutils no longer supplies /etc/updatedb.conf. F
Still seems to be an issue with a fresh install of Hardy with all updates
applied.
Using just slocate on my server gives this error when cron task is run.
Workaround via:
touch /etc/updatedb.conf
--
slocate cron job fails if /etc/updatedb.conf not found
https://bugs.launchpad.net/bugs/189462
You
It also affects updatedb , because updatedb and slocate -u have the same
behavior.
An interesting thing to notice, however, is that even if a so-called fatal
error is raised, the [ms]?locate database is still updated:
> locate bochs
> sudo updatedb
[sudo] password for [snip]:
updatedb: fatal er
Christoph Lechleitner wrote:
> Abel Cheung wrote:
>
>> For those who need command line access, change your habit is the way to go.
>>
> This ignorance against command line users is annoying, at best!
>
> Matt Zimmerman wrote in that link mailing list message:
>
>> Today, at least, it doe
Abel Cheung wrote:
>For those who need command line access, change your habit is the way to go.
This ignorance against command line users is annoying, at best!
Matt Zimmerman wrote in that link mailing list message:
>Today, at least, it doesn't seem to be used, and more featureful indexed
>searchi
Matt, i can see how you are trying to simplify the matter, and I
appreciate it, because it *is* helping me understand what happens.
However, as a distro I think there is also the goal of not 'surprising'
your users. Both me and Akkana have been raising (imho) very valid
points where, from a usage
I don't know what thread you were reading, but I didn't see anywhere in
the conversation that you linked that slocate would be removed. The
conversation focused mainly on the possibility of not shipping it by
default in desktop installs. It didn't really even address server
installations, nor did
It has been said very clearly that https://lists.ubuntu.com/archives/ubuntu-
devel/2008-February/025065.html">slocate would be removed. Don't
expect anything to be 'fixed' if the intention is to drop it completely.
Though I have not much idea why the final result is to add mlocate
instead. For tho
I hit the problem too. I upgraded to hardy, reviewed the packages
'deinstalled' (get-selections) and thought: hey, don't junk slocate, I
use that!
So I apt-get install slocate, but it won't fly:
[EMAIL PROTECTED]:/etc/alternatives$ sudo updatedb
[EMAIL PROTECTED]:/etc/alternatives$ slocate bla
sl
@Akkana: The slocate package should not depend on mlocate. mlocate was
written after slocate, and designed to function identically (with the
exception of the update algorithm used by updatedb) to it. Hence, they
both use the same /etc/updatedb.conf file. The mlocate package is
"complete" and inc
I hit this too: the slocate package installs a cron.daily script that
fails (and sends error mail) unless mlocate is also installed. So
shouldn't slocate have a package dependency on mlocate? Or should they
be mutually exclusive?
--
slocate cron job fails if /etc/updatedb.conf not found
https://b
Regardless of mlocate, this problem exists on servers as well. It also
doesn't excuse shipping broken packages, whether they're the default or
not.
--
slocate cron job fails if /etc/updatedb.conf not found
https://bugs.launchpad.net/bugs/189462
You received this bug notification because you are
8.04 uses mlocate instead of slocate on desktops now, so if you have an
upgraded hardy you probably should change this too, if it is not done
automatically.
http://ubuntuforums.org/archive/index.php/t-705205.html
--
slocate cron job fails if /etc/updatedb.conf not found
https://bugs.launchpad.ne
** Changed in: slocate (Debian)
Status: Unknown => New
--
slocate cron job fails if /etc/updatedb.conf not found
https://bugs.launchpad.net/bugs/189462
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
** Bug watch added: Debian Bug tracker #457084
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457084
** Also affects: slocate (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457084
Importance: Unknown
Status: Unknown
** Changed in: slocate (Ubuntu)
Importance: U
30 matches
Mail list logo
