Closed Bug 615135 Opened 15 years ago Closed 15 years ago

SVN write access for the @localizers group to /projects/sumo/locales

Categories

(mozilla.org :: Repository Account Requests, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: tim.babych, Assigned: arzhel)

Details

Hello. I am having trouble committing my changes to SUMO l10n svn: https://svn.mozilla.org/projects/sumo/locales/uk svn ci -m "some msg" Sending LC_MESSAGES/messages.po svn: Commit failed (details follow): svn: Server sent unexpected return value (403 Forbidden) in response to CHECKOUT request for '/!svn/ver/78102/projects/sumo/locales/uk/LC_MESSAGES/messages.po' Please take a look.
Commit to mozilla.com repo works fine.
is https://svn.mozilla.org/projects/sumo/locales/ accessible to committers in the @localizers group for svn? If not, it would explain why Tim can't commit there while he can commit on other repos accessible to localizers.
CCIng Kadir
Actually I don't know, cc'ing Stas and Gandalf
I don't believe we ever set this up. I've only found a bug about giving the write access to Verbatim. Morphing this bug into a server operations one. CC'ing James, too. James, are you fine with that? (IT: please wait for James' approval.)
Assignee: marcia → server-ops
Component: Repository Account Requests → Server Operations
QA Contact: repo-acct-req → mrz
Summary: Need access to SUMO L10n → SVN write access for the @localizers group to /projects/sumo/locales
Assignee: server-ops → ayounsi
Component: Server Operations → Repository Account Requests
I had same trouble to access SUMO locale and look in Bug 587913. Please solve this issue for localizer.
Is is not solved yet? New localizer is hard to input, review and confirm large strings in Verbatim. Please add us soon!
(In reply to comment #5) > CC'ing James, too. James, are you fine with that? (IT: please wait for James' > approval.) James, are you fine with that?
Oh yeah, sorry for the delay. a=me.
Access granted to @localizers
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Thank you, James and Arzhel.
You need to log in before you can comment on or make changes to this bug.