494531 - updater.ini borked for mac/linux l10n builds

Status: RESOLVED DUPLICATE of bug 488936

(Firefox Build System :: General, defect)

Description

[Axel Hecht [:Pike]]

Looking at the builds logs for mac and linux repacks, updater.ini is broken on non-windows platforms.

http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-l10n-oc/1243018580.1243018647.17183.gz&fulltext=1 and http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-l10n-oc/1243018580.1243018651.17191.gz&fulltext=1 are examples, this is not tied to a particular locale, though.

It seems that somehow the pipe doesn't make it into the build, no idea what's going on.

Rob, hg blame has you on that, can you look at that?

Smells like an obvious 3.5 blocker to me, I didn't dive into actual builds to see what they have in there.

Comment 1

[Axel Hecht [:Pike]]

FWIW, the culprit in the log is

cat /builds/moz2_slave/mozilla-1.9.1-linux-l10n-nightly/build/releases/l10n-mozilla-1.9.1/oc/browser/updater/updater.ini \
	  sed -e "s/^InfoText=/Info=/" -e "s/^TitleText=/Title=/" | \
	  sed -e "s/%MOZ_APP_DISPLAYNAME%/Shiretoko/" > \
	  ../../dist/xpi-stage/locale-oc/updater.ini
cat: sed: No such file or directory
cat: s/^InfoText=/Info=/: No such file or directory
cat: s/^TitleText=/Title=/: No such file or directory


The updater.ini in the occitan linux build is

; This file is in the UTF-8 encoding$
[Strings]$
TitleText=Mesa a jorn de Shiretoko$
InfoText=Shiretoko es a installar vM-CM-2stras mesas a jorn e aviarM-CM-  dins un momentonM-bM-^@M-&$


which in no way resembles what's in the repository,

; This file is in the UTF-8 encoding
[Strings]
TitleText=Mesa a jorn de %MOZ_APP_DISPLAYNAME%
InfoText=%MOZ_APP_DISPLAYNAME% es a installar vòstras mesas a jorn e aviarà dins un momenton…

Comment 2

[Robert Strong (they/them - no direct email)]

This should be fixed by
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/ae314e1051b6

I verified that it is on a Linux Tinderbox build and locally on Mac OS X.

Since the patch that fixed this is in Bug 488936 resolving this bug as a dupe of it.

Comment 3

[Robert Strong (they/them - no direct email)]

fyi: I also just re-verified that it is fixed