Re: Getting the svn repo to run the latest tracker service code
On Sat, 2 Jan 2010 10:42:49 -0500 Michael Gilbert wrote:
> Hi all,
>
> As you may have seen, I pushed some updates to the tracker service
> last night. However, as of this morning, the svn repo still appears
> to be running the old code.
>
> For example, adding a line with the new <undetermined> status, I can
> run "make check-syntax" locally and it will succeed (since my code adds
> <undetermined> as a valid status). However, if I try to push these
> changes to the repo, I get the following error:
>
> <stdin>:1509: invalid special version '- qt4-x11 <undetermined> (bug #561760)' in package entry
>
> which is the same error that I would get locally from "make check-styntax"
> before I added the appropriate support. I also tried adding an item
> with an <end-of-life> status (based on Moritz's commit about a week ago),
> and got the same error.
>
> My best guess is that the svn repo is running the old code rather than the
> latest updates. Can someone with the appropriate permissions force the
> repo to start using the new code (or make that automatic)? A culprit
> may be that the new pyc files (for the modified code) need to be
> generated.
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 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)?
Mike
Reply to: