350184 - l10n repository out of synch on cvs-mirror

Status: RESOLVED FIXED

(mozilla.org :: CVS: Administration, task)

Description

[Axel Hecht [:Pike]]

Not exactly sure how and why, but this is what I see inside my check-out of l10n with my ssh-account, I'm in l10n/de/browser/chrome/browser/safebrowsing:

$ cvs -d:pserver:[e-mail]:/l10n status eula.dtd 
cvs status: eula.dtd is no longer in the repository
===================================================================
File: eula.dtd          Status: Entry Invalid

   Working revision:    1.1.2.1
   Repository revision: No revision control file
   Sticky Tag:          MOZILLA_1_8_BRANCH - MISSING from RCS file!
   Sticky Date:         (none)
   Sticky Options:      (none)


Axel@Mojo /cygdrive/c/Sources/MOZILLA_1_8_BRANCH/l10n/de/browser/chrome/browser/safebrowsing
$ cvs status eula.dtd 
===================================================================
File: eula.dtd          Status: Up-to-date

   Working revision:    1.1.2.1
   Repository revision: 1.1.2.1 /l10n/l10n/de/browser/chrome/browser/safebrowsing/Attic/eula.dtd,v
   Sticky Tag:          MOZILLA_1_8_BRANCH (branch: 1.1.2)
   Sticky Date:         (none)
   Sticky Options:      (none)


That file got initally added on the trunk on 2006/08/24 17:40:04.

Comment 1

[Axel Hecht [:Pike]]

To make this more precise, this does not only affect a single file, and blocks my l10n test automation as my anonymous checkout doesn't get a current state of the tree.

Comment 2

[Reed Loden [:reed]]

justdave: I'll try to ping you on IRC about this, as it seems you haven't seen it in your bugmail.

Comment 3

[Dave Miller [:justdave]]

-rw-r--r--    1 root     root            0 Aug 23 11:40 rsync-l10n.lock

yippee, a stale lock :/

And based on the 2633 messages in the mail queue deferred because the connection to 10.251.0.12 timed out, I'd say the email to tell us about it never made it through because vegas thought it was still in meer for some reason.

Looks like there was a mailertable entry in sendmail hardcoding 10.251.0.12 as the destination for mozilla.org mail on vegas.  Must have been trying to avoid the MX records pointing it at OSUOSL or something (which are no longer present on the internal DNS).  Nuked that mailertable entry and now the mail goes out.  Also nuked the lock so the l10n rsyncs should be back in motion.

Based on how long it's been down, I'd give it 45 minutes to an hour to catch up.