Please report any other irregularities here.
In Bug 730618 Comment 30 Alexander L. Slovesnik wrote: FWIW, I still can not auto-update my Linux x86 build. https://aus3.mozilla.org/update/3/Firefox/13.0a1/20120224031039/Linux_x86-gcc3/ru/nightly/Linux%203.0.0-16-generic%20%28GTK%202.24.6%29/default/default/update.xml?force=1 doesn't contain link to update.
Same for me (French build)
fwiw, en-US serves <updates><update type="minor" version="13.0a1" extensionVersion="13.0a1" buildID="20120301031135"><patch type="complete" URL="http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2012/03/2012-03-01-03-11-35-mozilla-central/firefox-13.0a1.en-US.linux-i686.complete.mar" hashFunction="sha512" hashValue="49a706d902deffaa4ec7e7a6f3c50bd3d6ee5ea901b7401ba3c47dc3756b2531ed37214e5c3a38fb49a00ece0ffa80cc5b6f55ec9ff12b737d527a5fd8a5e125" size="18335843"/></update></updates> as in, a complete update.
Stupid AUS...I'll look into this.
Armen and Coop both think this should work itself out...I manually triggered an ru build, which fixed that locale. I triggered an entire new set of Linux nightlies, too, to try and get this figured out today instead of waiting for tomorrow. The en-US build is still going, I'm keeping a close eye on it though.
OK, I was watching https://aus3.mozilla.org/update/3/Firefox/13.0a1/20120224031039/Linux_x86-gcc3/pl/nightly/Linux%203.0.0-16-generic%20%28GTK%202.24.6%29/default/default/update.xml?force=1 before and after the l10n build ran. It was empty before, now it's not. I'm 99% sure this means that all platforms + locales will be OK tomorrow. Leaving this bug open until tomorrow to verify.
FWIW, I did get an update on mac de. The mac nightly did get a respin throughout through.
Component: Release Engineering → Release Engineering: Automation
QA Contact: release → catlee
OK, as far as I can tell everyone is receiving nightly updates again.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.