Hi Lisandro, On December 20, 2015 01:18:31 PM Lisandro Damián Nicanor Pérez Meyer wrote: > On Saturday 19 December 2015 23:58:34 Steve M. Robbins wrote:
> > I found the config file (commit-access-control.cfg). Who is able to edit > > this for me? > > I have just added you, just ping me if you still get problems. I see your change to svn+ssh://s...@svn.debian.org/svn/pkg-kde/scripts/svn- hooks/commit-access-control.cfg. However, the change didn't get propagated to the copy in the actual hooks directory on alioth (/svn/pkg-kde/hooks). I suspect this was supposed to be automatic, but it's possible a manual step was required. The permissions on files in the hooks directory are a bit odd; most are owned by root, but some have different owners. I suspect someone may have edited files directly in the past rather than relying on committing to "pkg- kde/scripts". In this specific instance, the file is not writeable by the group, which may be why your update was missed: smr@moszumanska:/svn/pkg-kde/hooks$ ls -l total 100 -rw-r--r--+ 1 pusling-guest scm_pkg-kde 4584 Nov 9 2014 commit-access- control.cfg -rwxrwxr-x+ 1 root scm_pkg-kde 11293 Oct 31 2003 commit-access- control.pl I took the liberty of updating the file manually using the filesystem -- so now it's owned by me :-( . However, I did set the group write bit; so hopefully can be maintained as normal in future. After that change, I was able to update digikam. Thanks for your help! -Steve
signature.asc
Description: This is a digitally signed message part.
-- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
