Closed Bug 753829 Opened 13 years ago Closed 13 years ago

nightly.mozilla.org and http://www.mozilla.org/en-US/mobile/aurora/ need to change their android links

Categories

(Websites :: Other, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mozilla, Unassigned)

References

Details

It currently points at http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android/fennec-15.0a1.en-US.android-arm.apk . We've enabled multilocale builds for Fennec Native, which means we the en-US build is now in an en-US subdir, and there's a multi apk as well. http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android/ I'm not entirely sure which we want to point to off nightly.m.o, but the link will break when ftp.m.o's caching clears.
CC'ing in rnyman who reported this in #it and tofumatt who might know who could update http://www.mozilla.org/en-US/mobile/aurora/
Aurora's link will change once I fix bug 753488 (today?)
Depends on: 753488
Summary: nightly.mozilla.org needs to change its android link → nightly.mozilla.org and http://www.mozilla.org/en-US/mobile/aurora/ need to change their android links
this is urgent - there is a huge push to get Aurora tested and right now users are not able to download.
Priority: -- → P1
I softlinked the aurora build on ftp.m.o, should work until I reconfig for bug 753488.
Thanks!
Ali: Is this resolved for now?
I think this bug is resolved from my perspective; both nightly.m.o and the aurora download page are pointing at the new location. I'm in the middle of reconfiging for bug 753488, and will kick off a new Aurora nightly when that's finished. The new links will point to the new builds as is.
Priority: P1 → --
New aurora build is up: http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-aurora-android/en-US/ I'm going to mark RESO FIXED; please reopen or file new if there are further issues.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.