Closed Bug 566932 Opened 15 years ago Closed 15 years ago

maemo5-gtk l10n repacks break on tar

Categories

(Release Engineering :: General, defect, P4)

ARM
Maemo
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mozilla, Assigned: mozilla)

References

Details

(Whiteboard: [fennec][l10n])

Attachments

(1 file, 1 obsolete file)

/home/cltbld/build/gtk-maemo5-mobile-1.9.2-l10n/mozilla-1.9.2/config/nsinstall -D fy-NL/tmp cd ../../dist/xpi-stage/locale-fy-NL && \ tar --exclude=install.rdf --exclude=chrome.manifest --exclude=crashreporter.app -cvhf - * | ( cd /home/cltbld/build/gtk-maemo5-mobile-1.9.2-l10n/mozilla-1.9.2/mobile/locales/data-stage//usr/local/lib/fennec-1.1b2pre && tar -xf - ) /scratchbox/tools/bin/sh: line 2: cd: /home/cltbld/build/gtk-maemo5-mobile-1.9.2-l10n/mozilla-1.9.2/mobile/locales/data-stage//usr/local/lib/fennec-1.1b2pre: No such file or directory chrome/ chrome/fy-NL.jar tar: -: Cannot write: Broken pipe tar: Error is not recoverable: exiting now make[1]: *** [repackage-deb] Error 1 make[1]: Leaving directory `/home/cltbld/build/gtk-maemo5-mobile-1.9.2-l10n/mozilla-1.9.2/mobile/locales' make: *** [deb-fy-NL] Error 2 I'm going to guess that /usr/local/lib/fennec-1.1b2pre is no longer accurate for maemo5-gtk =P
Blocks: 538511
Attached patch use pf.get('enUS_binaryURL',... (obsolete) — Splinter Review
This is already checked into staging. I'd verify again in staging but all envs are taken. This should get maemo5-gtk l10n repacks to at least download the bits from the right directory.
Assignee: nobody → aki
Status: NEW → ASSIGNED
Attachment #447205 - Flags: review?(jhford)
Comment on attachment 447205 [details] [diff] [review] use pf.get('enUS_binaryURL',... Just noticed that this isn't hacking l10nUploadPath. Yay loop + not spelling this stuff out.
Attachment #447205 - Attachment is obsolete: true
Attachment #447205 - Flags: review?(jhford)
Ok. This patch: - removes the unused l10nUploadPath - hacks the baseUploadDir for maemo5 l10n - hacks the enUSBinaryURL for maemo5 l10n (already done in staging) so it should fix where the deb is downloading from (latest-mobile-trunk-maemo5-gtk rather than latest-mobile-trunk) and where it uploads l10n repacks to (latest-mobile-trunk-maemo5-gtk-l10n rather than latest-mobile-trunk-l10n). All the staging envs are taken or sans-slaves, so untested past test-masters.sh/checkconfig. However, all maemo5-gtk repacks are currently busted on production, so up to you if you want to block on that.
Attachment #447224 - Flags: review?(jhford)
Attachment #447224 - Flags: review?(jhford) → review+
Yay! http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mobile-trunk-maemo5-gtk-l10n/ ... I also had to clobber all the linux l10n slaves on pm02 for this to work.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: