The default bug view has changed. See this FAQ.

Create locale repositories in /gaia-l10n: bn-IN gu km ne-NP si th vi

RESOLVED FIXED

Status

Developer Services
General
RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: stas, Assigned: bkero)

Tracking

Details

(Reporter)

Description

4 years ago
Please create the following repositories under hg.mozilla.org/gaia-l10n:

bn-IN
gu
km
ne-NP
si
th
vi

The repos should have the common l10n permissions and hooks, both python:mozhghooks.pushlog and python:mozhghooks.single_head_per_branch.hook.

The permissions should be scm_l10n, not level_1.

Thank you.
(Reporter)

Updated

4 years ago
Summary: Create locale repositories in /gaia-l10n → Create locale repositories in /gaia-l10n: bn-IN gu km ne-NP si th vi

Comment 1

4 years ago
Per https://wiki.mozilla.org/ReleaseEngineering/RepositoryCreationRequest, we should make this start out in releng.

Hal passes it to IT then.
Assignee: server-ops-devservices → nobody
Component: Server Operations: Developer Services → Release Engineering: Developer Tools
QA Contact: shyam → hwine
(Reporter)

Comment 2

4 years ago
I see these repos created in https://hg.mozilla.org/gaia-l10n/.  Are they now ready to be used?
Sorry I missed this earlier.

(In reply to Staś Małolepszy :stas (traveling until Dec 4) from comment #2)
> I see these repos created in https://hg.mozilla.org/gaia-l10n/.  Are they
> now ready to be used?

I don't know - it seems odd that they would have been created but this bug not closed.

Reassigning to Developer Services for a definitive answer and resolution
Assignee: nobody → server-ops-devservices
Component: Release Engineering: Developer Tools → Server Operations: Developer Services
Flags: needinfo?(server-ops-devservices)
QA Contact: hwine → shyam
(In reply to Axel Hecht [:Pike] from comment #1)
> Per https://wiki.mozilla.org/ReleaseEngineering/RepositoryCreationRequest,
> we should make this start out in releng.

True & thanks! 

Are you going to update https://wiki.mozilla.org/L10n:Bugogram#hg_repo for the b2g case. I _think_ the only difference is only one repo per locale is used. (And maybe the blocking alias)
I don't know either. I don't remember doing this. Ben?
(Assignee)

Comment 6

4 years ago
Yes, I did this but forgot to update the bug.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Assignee)

Updated

4 years ago
Flags: needinfo?(server-ops-devservices)

Updated

4 years ago
Assignee: server-ops-devservices → bkero
(Reporter)

Comment 7

4 years ago
I'm getting the following error when trying to push:

pushing to ssh://hg.mozilla.org/gaia-l10n/bn-IN
searching for changes
remote: Not trusting file /repo/hg/mozilla/gaia-l10n/bn-IN/.hg/hgrc from untrusted user root, group scm_l10n
remote: Not trusting file /repo/hg/mozilla/gaia-l10n/bn-IN/.hg/hgrc from untrusted user root, group scm_l10n
remote: abort: could not lock repository /repo/hg/mozilla/gaia-l10n/bn-IN: Permission denied
abort: unexpected response: empty string

Reopening, sorry :(  Do you know what's causing this?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Reporter)

Comment 8

4 years ago
Ben,  the changes from bug 818461 comment 2 fixed part of the problem, but I still can't push:

master ☀ bn-IN hg push                                                                             21:20:24
pushing to ssh://hg.mozilla.org/gaia-l10n/bn-IN
searching for changes
remote: abort: could not lock repository /repo/hg/mozilla/gaia-l10n/bn-IN: Permission denied
abort: unexpected response: empty string
master ☀ bn-IN
(Assignee)

Comment 9

4 years ago
I saw the problem and corrected it (group permissions). Please try again.
(Reporter)

Comment 10

4 years ago
Both https://hg.mozilla.org/gaia-l10n/bn-IN & https://hg.mozilla.org/gaia-l10n/bn-IN/pushloghtml show my push, thanks a lot, Ben!
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in before you can comment on or make changes to this bug.