Hi Tinu, > > https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/mlocate#n58 > > seems to take care that /var/lib/locate is 750 on line 58, but > > that's `locate', not `mlocate', so perhaps `mlocate' needs a similar > > set up? > > I don't quite see the relation between locate an mlocate here (other > than that they are provided by the same package and are listed next to > each other in the mtree)... Doesn't PKGBUILD explicitly ensuring `locate' is 750, `mlocate's filesystem value, suggest it should do similar for `mlocate' to avoid the mismatch? > The package wants /var/lib/mlocate to have 755, but the directory on > your system has 750. Yes, that's what I understood the warning to say. > I assume this is because the previous version of mlocate (0.26-6) set > the permission that way: > > $ zcat .MTREE | tail -n4 > → /set gid=21 mode=750 > ./var/lib time=1491283536.206666666 mode=755 gid=0 type=dir > ./var/lib/locate time=1491283536.206666666 type=dir > → ./var/lib/mlocate time=1491283536.156666666 type=dir And I think that was correct since the package's `Makefile.am' has dbdir = $(localstatedir)/mlocate ... install-exec-local: $(MKDIR_P) "$(DESTDIR)$(dbdir)" -chgrp $(groupname) "$(DESTDIR)$(dbdir)" 2>/dev/null \ → && chmod g=rx,o= "$(DESTDIR)$(dbdir)" AFAICS that file hasn't changed between git's upstream/0.26 in the Debian repo and mlocate-0.26-14-gc98bf65 in the current one. > I assume pacman never touches permissions on existing directories, I could understand if it doesn't automatically do that, but issue a warning instead, say. > hence the warning. Thus my wondering if the package is faulty for having 755. If not, then presumably a PKGBUILD function gets added to convert existing installations? -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy
