502902 - Fix SVN write hooks

Status: RESOLVED FIXED

(Webtools Graveyard :: Verbatim, defect)

Description

[Fred Wenzel [:wenzel]]

Verbatim used to be capable to write localizers' changes back to SVN. Wil wrote a hook script for that (on sm-cms01, /home/verbatim/scripts). It likely still works. Need to get it up and running again and tracked in SVN (make sure it's free of sensitive data).

Please note the useful explanations Wil provided in bug 502217. The hook (and SVN) won't enforce write rights, that needs to happen in Pootle before.

Comment 1

[Fred Wenzel [:wenzel]]

After fixing an SVN conflict in de/messages.po, I was able to commit successfully: r30143.

Wil, Gandalf: We'll need to make sure conflicts (local changes vs. SVN changes) are handled properly when switching to the regular format. I hope this is handled properly in Pootle already, but it is also possible that Pootle assumes no-one besides itself changes the .po files on SVN.

Comment 2

[Dwayne Bailey]

Pootle is actually built to assume that someone will change a PO files in VC.  Thus when it checks in it actually makes sure the file is up-to-date and then merges any Pootle changes in.  The drawback is its slower, the advantage is that someone can edit files in VC as needed, e.g. quickly fixing a build bug.

I assume that the reason it couldn't commit was that the conflict blocked proper operation.  Being able to tell the site admin about these issues would be helpful