Closed
Bug 502896
Opened 15 years ago
Closed 15 years ago
Re-import AMO
Categories
(Webtools Graveyard :: Verbatim, defect)
Webtools Graveyard
Verbatim
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wenzel, Assigned: wenzel)
References
Details
We need to make AMO work with the Verbatim staging instance again. This bug is about getting the import script working again. There are scripts for both AMO and SUMO on sm-cms01 in /home/verbatim/scripts that may just work. They should be dusted off, fixed if necessary, and thrown into SVN (probably as scripts/ under http://svn.mozilla.org/projects/verbatim/trunk/ ?). I'll file another bug on *writing* .po changes made by localizers back to SVN.
Assignee | ||
Comment 2•15 years ago
|
||
I found the existing set of scripts for handling AMO and SUMO on Pootle, and I committed them to our own SVN server in r29584.
Assignee | ||
Comment 3•15 years ago
|
||
I set this up again, and have yet to fix Verbatim's SVN credentials but it is looking promising. I also added logging to the hook script so that we can see what's going on.
Comment 4•15 years ago
|
||
@wenzel: if you see any opportunity for such scripts to be useful to others then it might be worth committing them SF repository. Or simply a README that points to the Mozilla repositories scripts and what they do.
Assignee | ||
Comment 5•15 years ago
|
||
Thanks, Dwayne, that's a good suggestion. Other people may indeed find it helpful to read through these scripts when setting up their own projects.
Assignee | ||
Comment 6•15 years ago
|
||
AMO's initialization and update-from-SVN hooks are working again. Final step for this bug: I am in the process of updating all languages, one by one (cf. bug 504277).
Assignee | ||
Comment 7•15 years ago
|
||
False alarm: While it does not error out anymore, clicking on the "update from version control" button does NOT execute a proper svn up. What's so hard about this, and why it is broken so horribly, I don't know :((
Assignee | ||
Comment 8•15 years ago
|
||
Hm, new day, new luck. I re-updated the languages and it works now. Might have been a caching issue. Calling this fixed!
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•