Bugzilla Bug 130435

This is what dispatch-conf shows after upgrading slocate 2.7-r8 to 3.1

--- /etc/cron.daily/slocate     2006-04-17 20:16:22.000000000 +0200
+++ /etc/cron.daily/._cfg0000_slocate   2006-04-19 09:29:57.000000000 +0200
@@ -1,6 +1,6 @@
 #! /bin/sh

-if [ -x /usr/bin/updatedb ]
+if [ -x /usr/bin/slocate ]
 then
        if [ -f /etc/updatedb.conf ]
        then
@@ -8,4 +8,5 @@
        else
                nice /usr/bin/updatedb -f proc
        fi
+       chown root.slocate /var/lib/slocate/slocate.db
 fi

But I had version 2.7-r8 which told me to change the group name and I followed,
so:

$ grep locate /etc/group
locate:x:245:

After manually deleting slocate.db and running updatedb, it's owned by
root.locate, so I guess the whole chown line is not needed?

The question also is, what woul happen when going to 3.1 from <2.7-r8 - would
it also rename the group to "locate", as 2.7-r8 does, or is 3.1 expecting
"slocate" not just in cron script?
Also wondering that 3.1 went directly to stable, after the long stabilisation
of 2.7-r8...

*** Bug 130449 has been marked as a duplicate of this bug. ***

(In reply to comment #1)
> The question also is, what woul happen when going to 3.1 from <2.7-r8 - would
> it also rename the group to "locate", as 2.7-r8 does, or is 3.1 expecting
> "slocate" not just in cron script?
> Also wondering that 3.1 went directly to stable, after the long stabilisation
> of 2.7-r8...
> 

It's also a question to be answered, that which kind of new behaviour
introduced by this new version creates the need for this new line, if the
pervious ones were functioning correctly without it.
I have RBAC system installed, and I like to give a process only the resonable
rights.

Regards,
Dw.

I just upgraded to 3.1 and I was asked to make 'groupmod -n locate slocate'. So
I renamed the group. The owner of /var/lib/slocate/slocate.db is now
root.locate (group number stayed the same, only the name changed).

Fix the cron script, please. It should use root.locate, not root.slocate.

OK it's no longer stable at least, see bug 130562

slocate-3.1 updates ok for me using the cron script from 2.7-r8 and the name of
group 245 set to 'locate' in arch x86.

/var/lib/slocate/slocate.db ends up with ownership root.locate and it can be
read by /usr/bin/locate as installed by 3.1.

fixed in 3.1-r1