Closed Bug 1066520 Opened 5 years ago Closed 5 years ago

make installers-{locale_name} fails with localized Chatzilla

Categories

(SeaMonkey :: Build Config, defect)

SeaMonkey 2.31 Branch
All
Linux
defect
Not set

Tracking

(seamonkey2.30 fixed, seamonkey2.31 fixed, seamonkey2.32 fixed)

RESOLVED WORKSFORME
seamonkey2.32
Tracking Status
seamonkey2.30 --- fixed
seamonkey2.31 --- fixed
seamonkey2.32 --- fixed

People

(Reporter: adriank, Unassigned)

Details

Attachments

(1 file)

Attached file make installers-pl log
On current Aurora (2.31a2) and Central (2.32a1) when trying to do "make installers-{locale_name}", e.g. "make installers-pl", with a locale that has Chatzilla L10n enabled and has Chatzilla fully localized, it will fail with:

rm -f -rf /home/mozilla/jenkins/workspace/seamonkey-central_linux32/objdir/dist/l10n-stage/seamonkey/extensions/langpack-pl@chatzilla.mozilla.org
mkdir /home/mozilla/jenkins/workspace/seamonkey-central_linux32/objdir/dist/l10n-stage/seamonkey/extensions/langpack-pl@chatzilla.mozilla.org
mkdir: cannot create directory `/home/mozilla/jenkins/workspace/seamonkey-central_linux32/objdir/dist/l10n-stage/seamonkey/extensions/langpack-pl@chatzilla.mozilla.org': No such file or directory

(see the attached log for the full log)
Yes, I guess we need to update this to the distribution/extensions/ directory that those are living in now.
Fix bad merge @ d36ec78a2714
http://hg.mozilla.org/releases/comm-aurora/rev/e95a749f6006
Fix bad merge @ 0e090c9f14d4
http://hg.mozilla.org/comm-central/rev/ef6c43405ced
Status: NEW → ASSIGNED
Just tested it with
https://hg.mozilla.org/comm-central/rev/ef6c43405ced on central
and
https://hg.mozilla.org/releases/comm-aurora/rev/e95a749f6006 on aurora


and... it still fails on "make installers-{locale_name}"...

Unfortunately, I don't have the log to see, if this is exactly the same error or a new one...
This seems to have been fixed since the October, 25th (the build from Oct, 24th was still affected).
(In reply to Adrian Kalla [:adriank] from comment #5)
> This seems to have been fixed since the October, 25th (the build from Oct,
> 24th was still affected).

Forgot to close the bug then...
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.