Lars, Further reading, I found this in the pootle.prefs file: # pootle.podirectory # # All projects are stored in this directory in this layout: # $podirectory/$project/$language # Projects can also be stored according to the GNU convention # with one PO file per language, and all files in one directory. podirectory = "/var/lib/pootle/"
The note about the "GNU convention" seems to match the way that the OLPC has decided to work... but couldn't find where it should be flagged... originally I had thought the 'checker style' was the flag (but, afaik, just deals with shortcut conventions and similar). I remember reading in the docs about a self test or something that would determine the layout, and that you could turn it off if it took too long, but can't seem to find the reference now... Any help in getting git+Pootle work together will be greatly appreciated. (btw, the irc#pootle help has been fantastic :) Cheers, Xavier On Friday 19 October 2007 03:18, Xavier Alvarez wrote: XA> Lars, XA> XA> Thanks a lot for your help. XA> XA> After a crash-course in git, diffs, and command line (all XA> things I've happily lived most of my life without :) we XA> managed to get both the diff + traces in our Pootle. And XA> they seem to be be working fine. But... we still have no XA> "commit". XA> XA> According to the log: XA> checking for RCS support: /var/lib/pootle/olpctest/es/ XA> no RCS item: /var/lib/pootle/olpctest/es/ XA> XA> Now the problem is that the directory .../es is actually XA> within pootle (as its path indicates). What is being managed XA> by git are the *symlinks* in the .../es directory. XA> XA> More 'graphically', the situation is: XA> XA> On the Pootle side: XA> XA> /var/lib/pootle XA> /olpctest XA> /es XA> edukt.po (-> symlink es.po) XA> /pt XA> edukt.po (-> symlink pt.po) XA> On the GIT side: XA> XA> /clone/edukt XA> /po XA> edukt.pot XA> es.po XA> pt.po XA> ... XA> XA> So the reason that our Pootle fails to detect the version XA> control system, is that it verifies the directory (in the XA> pootle hierarchy) when it should be checking the file (which XA> is the symlink to the version control). XA> XA> We are looking into the code, to see if the failure is an XA> artifact of the backport, or where it may be tweaked. But XA> would appreciate (a lot :) any guidance. XA> XA> XA> Cheers, XA> Xavier XA> XA> On Thursday 18 October 2007 19:05, you wrote: XA> La> Hi Xavi, XA> La> the attached patch includes all relevant changes to XA> La> versioncontrol.py since 1.0.2. XA> La> XA> La> Afterwards you need to apply the previously sent patch. XA> La> XA> La> Good luck! XA> La> XA> La> Lars XA> La> XA> -- XA ========= Don't Panic! The Answer is 42 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
