Closed Bug 818461 Opened 12 years ago Closed 12 years ago

bad permissions for releases/mozilla-beta/oc

Categories

(Developer Services :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Assigned: bkero)

References

Details

Just rant into one of our permission problems again for the beta occitan repo:

(cl)wokbok:oc axelhecht$ hg push
Übertrage nach ssh://hg.mozilla.org/releases/l10n/mozilla-beta/oc/
Suche nach Änderungen
Entfernt: Füge Änderungssätze hinzu
Entfernt: Füge Manifeste hinzu
Entfernt: Füge Dateiänderungen hinzu
Entfernt: Fügte 11 Änderungssätze mit 729 Änderungen an 522 Dateien hinzu
Entfernt: Fehler: Hook changegroup.z_loghistory löste eine Ausnahme aus: attempt to write a readonly database
(cl)wokbok:oc axelhecht$ hg push
Übertrage nach ssh://hg.mozilla.org/releases/l10n/mozilla-beta/oc/
Suche nach Änderungen
Keine Änderungen gefunden

Can we fix that? Probably fine to even reset the repo, there wasn't a push to it since we originally created it.

Also, can we assert that the other repos work in mozilla-beta?

Also 2, check the mozilla-release/oc repo as well.

If you reset the beta repo, you could reset it with the changesets in the release repo, that's having the same set of changesets beta had before I pushed.

Did some quick check on my database, here's the beta repos with less than 10 pushes, name and no. of pushes:

releases/l10n/mozilla-beta/ka 0
releases/l10n/mozilla-beta/ms 0
releases/l10n/mozilla-beta/ne-NP 0
releases/l10n/mozilla-beta/nr 0
releases/l10n/mozilla-beta/oc 0
releases/l10n/mozilla-beta/rw 0
releases/l10n/mozilla-beta/ss 0
releases/l10n/mozilla-beta/st 0
releases/l10n/mozilla-beta/tn 0
releases/l10n/mozilla-beta/ts 0
releases/l10n/mozilla-beta/ve 0
releases/l10n/mozilla-beta/x-testing 0
releases/l10n/mozilla-beta/xh 0
releases/l10n/mozilla-beta/my 0
releases/l10n/mozilla-beta/wo 1
releases/l10n/mozilla-beta/an 0
releases/l10n/mozilla-beta/sah 0
releases/l10n/mozilla-beta/ur 0


an, sah, ur are new, but many of those are old.
... and stas just hit

master ☀ bn-IN hg push                                    16:06:50
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
master ☀ bn-IN

not sure if related.
The problems in comment #1 and comment #2 were related to file ownership.

In comment #1 the 'hgrc' file was owned by user 'root', which was not trusted. This was corrected with 'chown -R */.hg/hgrc'.

In comment #0 the group for the pushlog2.db files was 'hg', which was incorrect. The l10n files should have been group-owned by 'scm_l10n'. This has also been corrected with a nice 'chgrp -R scm_l10n *'.

Please let me know if this is still affecting you.
Assignee: server-ops-devservices → bkero
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
There was one repo (wo) that had a single change. I've moved this to 'wo-backup' so you can retrieve the one changeset and push it into the newly created 'wo' repository such that the pushlog can get correctly updated.

When you've done that please let me know and I can delete the 'wo-backup' repository.
(In reply to Ben Kero [:bkero] from comment #2)
> In comment #1 the 'hgrc' file was owned by user 'root', which was not
> trusted. This was corrected with 'chown -R */.hg/hgrc'.
> 
> Please let me know if this is still affecting you.

Thanks for looking into this, Ben.  I don't want to reopen this bug but I commented in bug 814812 -- I still can't push.
I've modified the repositories to have group write permissions, which should permit you to push to them. Let me know if you have any more problems or if this does not work for you.
Blocks: 825880
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.