Closed
Bug 845247
Opened 12 years ago
Closed 12 years ago
No builds for latest nightly localization of Firefox for win32
Categories
(Firefox Build System :: General, defect)
Tracking
(firefox22+ verified)
VERIFIED
FIXED
mozilla22
People
(Reporter: piecu, Assigned: jimm)
References
Details
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
There are no latest localization builds for Firefox for win32 on FTP: ftp://ftp.mozilla.org/pub/firefox/nightly/latest-mozilla-central-l10n/
Comment 1•12 years ago
|
||
According to our buildbot database, we have not had a green build of 'Firefox mozilla-central win32 l10n nightly' since Feb. 13.
From some logs still available under ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013/02/:
2013-02-20-03-11-26-mozilla-central-l10n:
checking for Windows SDK being recent enough... no
configure: error: You are targeting Windows version 0x06020000, but your SDK only supports up to version 0x06010000. Install and use an updated SDK, or target a lower version using --with-windows-version. Alternatively, try running the Windows SDK Configuration Tool and selecting a newer SDK. See https://developer.mozilla.org/En/Windows_SDK_versions for more details on fixing this.
program finished with exit code 1
2013-02-21-03-09-52-mozilla-central-l10n:
checking for Windows SDK being recent enough... no
configure: error: You are targeting Windows version 0x06020000, but your SDK only supports up to version 0x06010000. Install and use an updated SDK, or
target a lower version using --with-windows-version. Alternatively, try running the Windows SDK Configuration Tool and selecting a newer SDK. See http
s://developer.mozilla.org/En/Windows_SDK_versions for more details on fixing this.
program finished with exit code 1
2013-02-22-03-11-33-mozilla-central-l10n:
checking for Windows SDK being recent enough... no
configure: error: You are targeting Windows version 0x06020000, but your SDK only supports up to version 0x06010000. Install and use an updated SDK, or
target a lower version using --with-windows-version. Alternatively, try running the Windows SDK Configuration Tool and selecting a newer SDK. See http
s://developer.mozilla.org/En/Windows_SDK_versions for more details on fixing this.
program finished with exit code 1
2013-02-23-03-11-57-mozilla-central-l10n:
e:/builds/moz2_slave/m-cen-w32-l10n-ntly-0000000000/build/mozilla-central/_virtualenv/Scripts/python.exe /e/builds/moz2_slave/m-cen-w32-l10n-ntly-00000
00000/build/mozilla-central/browser/locales/../../config/nsinstall.py -t -m 644 /e/builds/moz2_slave/m-cen-w32-l10n-ntly-0000000000/build/l10n-central/
de/browser/crashreporter/crashreporter-override.ini ../../dist/xpi-stage/locale-de/browser
make[1]: Leaving directory `/e/builds/moz2_slave/m-cen-w32-l10n-ntly-0000000000/build/mozilla-central/browser/locales'
make[1]: Entering directory `/e/builds/moz2_slave/m-cen-w32-l10n-ntly-0000000000/build/mozilla-central/browser/metro/locales'
make[1]: Leaving directory `/e/builds/moz2_slave/m-cen-w32-l10n-ntly-0000000000/build/mozilla-central/browser/metro/locales'
make[1]: *** No targets specified and no makefile found. Stop.
make: *** [libs-de] Error 2
2013-02-26-03-10-02-mozilla-central-l10n:
e:/builds/moz2_slave/m-cen-w32-l10n-ntly-0000000000/build/mozilla-central/_virtualenv/Scripts/python.exe /e/builds/moz2_slave/m-cen-w32-l10n-ntly-0000000000/build/mozilla-central/browser/locales/../../config/nsinstall.py -t -m 644 /e/builds/moz2_slave/m-cen-w32-l10n-ntly-0000000000/build/l10n-central/de/browser/crashreporter/crashreporter-override.ini ../../dist/xpi-stage/locale-de/browser
make[1]: Leaving directory `/e/builds/moz2_slave/m-cen-w32-l10n-ntly-0000000000/build/mozilla-central/browser/locales'
make[1]: Entering directory `/e/builds/moz2_slave/m-cen-w32-l10n-ntly-0000000000/build/mozilla-central/browser/metro/locales'
make[1]: Leaving directory `/e/builds/moz2_slave/m-cen-w32-l10n-ntly-0000000000/build/mozilla-central/browser/metro/locales'
make[1]: *** No targets specified and no makefile found. Stop.
make: *** [libs-de] Error 2
program finished with exit code 2
Comment 2•12 years ago
|
||
So this looks like "metro" bustage somehow (I theorize fallout from Bug 844068 - but don't have time to test/investigate) but it may have been present for longer and just not exposed until the earlier l10n issue was fixed.
tracking-firefox22:
--- → ?
Comment 3•12 years ago
|
||
My 'drop metro l10n' doesn't have anything to do with this.
browser/metro/locales and friends are not part of browser/makefiles.sh, thus, if you try to make in that dir without coming out of browser/ itself, Makefiles aren't generated.
Component: Release Engineering: Automation (General) → Build Config
Product: mozilla.org → Firefox for Metro
QA Contact: catlee
Version: other → Trunk
Comment 4•12 years ago
|
||
I bet on this:
diff --git a/browser/makefiles.sh b/browser/makefiles.sh
--- a/browser/makefiles.sh
+++ b/browser/makefiles.sh
@@ -60,16 +60,22 @@ browser/themes/Makefile
toolkit/locales/Makefile
extensions/spellcheck/locales/Makefile
intl/locales/Makefile
netwerk/locales/Makefile
dom/locales/Makefile
security/manager/locales/Makefile
"
+if [ "$MOZ_METRO" ]; then
+ add_makefiles "
+ browser/metro/locales/Makefile
+ "
+fi
+
if [ "$MOZ_SAFE_BROWSING" ]; then
add_makefiles "
browser/components/safebrowsing/Makefile
"
fi
if [ "$MAKENSISU" ]; then
add_makefiles "
Theoretically, all Makefiles under browser/metro should be listed there.
Note bug 784841 will remove this makefiles.sh file, fixing the problem as a collateral.
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•12 years ago
|
Summary: No builds for latest nigthly localization of Firefox for win32 → No builds for latest nightly localization of Firefox for win32
Comment 6•12 years ago
|
||
Jim/Brian - can you help investigate and resolve as soon as possible? We've had no visibility into nightly l10n for the past two weeks, and verification of localizations is also blocked.
Assignee | ||
Comment 7•12 years ago
|
||
I followed the steps tinderbox takes on these builds and was able to reproduce. The metro folder was indeed missing. So I put this together based on glandium's comments below. It got me past the step that's currently broken on the l10n builders.
Attachment #719214 -
Flags: review?(mh+mozilla)
Assignee | ||
Comment 8•12 years ago
|
||
FWIW, we did test l10n repacks before we landed. I think the mistake I made was that I built the l10n-obj dir fully before following the steps on the repack wiki page. My guess is I would have seen this had I not done this. Although the steps tb takes and the steps on the wiki are somewhat different, I don't think that pkays into this.
Comment 9•12 years ago
|
||
Comment on attachment 719214 [details] [diff] [review]
potential fix v.1
bug 784841 is going to land today, removing this file, and it should fix the issue too.
Attachment #719214 -
Flags: review?(mh+mozilla)
Comment 10•12 years ago
|
||
Looks like problem is fixed, builds are present on server.
Reporter | ||
Comment 11•12 years ago
|
||
Still no windows build in ftp://ftp.mozilla.org/pub/firefox/nightly/latest-mozilla-central-l10n/
Comment 12•12 years ago
|
||
Are you sure?
firefox-22.0a1.pl.win32.checksums 28/02/13 22:03:00
firefox-22.0a1.pl.win32.checksums.asc 28/02/13 22:03:00
firefox-22.0a1.pl.win32.complete.mar 28/02/13 22:03:00
firefox-22.0a1.pl.win32.installer-stub.exe 28/02/13 22:03:00
firefox-22.0a1.pl.win32.installer.exe 28/02/13 22:03:00
firefox-22.0a1.pl.win32.zip 28/02/13 22:03:00
BTW my nightly had an automatic update this morning, maybe this bug should be closed as fixed
Reporter | ||
Comment 13•12 years ago
|
||
It looks like the page cached in my browser, after manual refresh everything is fine. Sorry for the mess and I think it's fixed.
Comment 14•12 years ago
|
||
Fixed by bug 784841.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
status-firefox22:
--- → fixed
Depends on: 784841
OS: Windows 8 → Windows 7
Product: Firefox for Metro → Firefox
Hardware: x86_64 → x86
Target Milestone: --- → Firefox 22
Assignee | ||
Comment 15•12 years ago
|
||
Have we considered adding the whole l10n build process to try and inbound/mc checkins? This and some of the other l10n issues could have been avoided if we had had visibility into what we do for l10n on try.
Comment 16•12 years ago
|
||
It was mentioned in discussions. File a bug on it? Probably suffices to repack one or two locales like french and italian.
Comment 17•12 years ago
|
||
Try should be enough.
Comment 18•11 years ago
|
||
Looks like there aren't win32 l10n builds for all languages. Languages as DE, FR or IT does not have win32 l10n builds. Is this expected?
Comment 19•11 years ago
|
||
URL for latest nightly (2013-05-16)
ftp://ftp.mozilla.org/pub/firefox/nightly/2013/05/2013-05-16-03-10-04-mozilla-central-l10n/
Reporter | ||
Comment 20•11 years ago
|
||
(In reply to MarioMi (:MarioMi) from comment #18)
> Looks like there aren't win32 l10n builds for all languages. Languages as
> DE, FR or IT does not have win32 l10n builds. Is this expected?
The files are available at ftp://ftp.mozilla.org/pub/firefox/nightly/latest-mozilla-central-l10n/
Comment 21•11 years ago
|
||
(In reply to Bartosz Piec from comment #20)
> The files are available at
> ftp://ftp.mozilla.org/pub/firefox/nightly/latest-mozilla-central-l10n/
I confirm they are present at the URL mentioned in Comment 20. Based on this I can also confirm the fix is verified.
Status: RESOLVED → VERIFIED
Updated•6 years ago
|
Component: Build Config → General
Product: Firefox → Firefox Build System
Updated•6 years ago
|
Target Milestone: Firefox 22 → mozilla22
You need to log in
before you can comment on or make changes to this bug.
Description
•