Re: Getting the svn repo to run the latest tracker service code
On Sat, 2 Jan 2010 21:34:43 +0100 Thijs Kinkhorst wrote:
> On sneon 2 Jannewaris 2010, Michael Gilbert wrote:
> > I spent some time looking around alioth today to try to figure out this
> > problem. It looks like the syntax checking script executes itself in an
> > old version of the tracker (located at /home/groups/secure-testing/repo),
> > which is why it is not working correctly. The file
> > /home/groups/secure-testing/README.repo describes this repo as used only
> > to run the pre-commit syntax check.
> >
> > I tried to manually update that repo myself, but I can't since certain
> > files are owned by Thijs with 744 permissions.
>
> I have added group write permissions to the entire checkout now (and updated
> it while I was at it).
>
> > I also tried updating
> > /srv/svn.debian.org/svn/secure-testing/hooks/check-file, which is the
> > script that is run on every new commit, to automatically sync to the latest
> > svn, but that also doesn't work due to the permissions on
> > /home/groups/secure-testing/repo. Could we change those to 764 or 760 so
> > that anyone in the secure-testing team can update that repo (and thus
> > the sync can automatically be done on every commit via the check-file
> > script)?
>
> Updating the repo on every commit, I would not be in favour of that. In the
> past years it only has needed to be updated a handfull of times, for which
> logging into alioth seems an acceptable cost. Committing to the repository
> already takes long as it is. If you think automating it is worthwhile, my
> suggestion would be to update in the post-commit only if files in lib and bin
> dirs have been touched in that commit.
That makes a lot of sense. I'll look at adding a post-commit run
when I get a chance. Thanks for the update!
Mike
Reply to: