Closed Bug 668365 Opened 13 years ago Closed 13 years ago

No langpacks built after June 27

Categories

(SeaMonkey :: Release Engineering, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 668586

People

(Reporter: tonymec, Unassigned)

Details

Happens every time.

Steps to reproduce (method 1: finer, at the command-line):

1. $ ftp ftp.mozilla.org
2. ftp> cd pub/mozilla.org/seamonkey/latest-comm-central-trunk-l10n
3. ftp> ls *.installer.exe
4. ftp> ls *.zip
5. ftp> ls *.dmg
6. ftp> ls *.bz2
7. ftp> ls *.xpi
8. ftp> bye

where $ and ftp> are the prompts

Actual results:
- At steps 5 and 6, all 2.4a1 builds are dated today
     (OK)
- At step 3 and 4, a few are dated today, most are dated yesterday
     (could be due to temporary orange or red)
- At step 6, all are dated June 27.
     (???)

Expected results:
I would expect langpacks with the same dates as the main builds.

Steps to reproduce (method 2: a little coarser, in a browser)
1. Browse to http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk-l10n/?C=M;O=D  (which sorts "latest first")
2. Search from the top of the page for the string "langpack.xpi" (without the quotes).

Additional info (don't know if relevant):
* In the six "SeaMonkey comm-central-trunk" columns of http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n&hours=36 I see:
- "busted" builds with a D (download) link
- "hourly" builds with a download link to the "nightly" download directory

* In the log from the most recent busted build (on cb-sea-win32-tbox), the abort seems due to a mixup about the .hgtags file for the LDAP SDK: see just above the summary of executed commands in http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-l10n/1309372691.1309372750.25821.gz
-- FWIW, "python client.py checkout" works for me, with "no changes found" in the LDAP SDK repository.
In that case, a simple clobber could help, I'll trigger one right now.
Hm, still looks wrong to me: I see either

seamonkey-2.4a1.<ab-CD>.<platform>.<zipext>
seamonkey-2.4a1.<ab-CD>.win32.installer.exe (Windows only)
seamonkey-2.4a1.<ab-CD>.<platform>.checksums
seamonkey-2.4a1.<ab-CD>.<platform>.complete.mar
comm-central-trunk-<OS>-nightly-<ab-CD>-build<nnnn>.txt.gz

or only the latter (which AFAICT is the logfile) but not a single langpack.xpi later han June 27.
Nowadays langpacks are being put under $platform/xpi (as http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk-l10n/win32/xpi/ for SeaMonkey central)
See Bug 668586 comment 1
In reply to comment #3:
There is no http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk-l10n/linux-x86_64/ directory. Maybe I should use those under linux-i686/xpi/ ?

Why separate directories by platform? Aren't the same English messages translated the same way into Bielorussian or ... or Swedish(Sweden) regardless of whether you're using Windows, 32-bit Linux, 64-bit Linux, or a Mac Universal (Intel 32/64) Binary?
Doesn't matter which platform you use, no. Resolving dupe of bug 668586, though this could just as well be independently worksforme.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.