We've just QA'd and shipped another round of updates. If you're using any of these localizations, you should be able to get your update now.
ast-ES, cs-CZ, da-DK, en-GB, he-IL, ko-KR, nb-NO, pt-BR, sl-SI, sv-SE, tr-TR, zh-CN, zh-TW
I've posted a revised version of the update instructions so if you'd like to the howto before attempting the update, you can find it here
update: I didn't mean to suggest those were the only localized build updates. That's just the latest batch. The full list looks like this, I believe.
af-ZA, ast-ES, ca-AD, cs-CZ, da-DK, de-DE, el-GR, en-GB, en-US, es-AR, fi-FI, fr-FR, ga-IE, he-IL, hu-HU, it-IT, ko-KR, nb-NO, nl-NL, pl-PL, pt-BR, pt-PT, ro-RO, ru-RU, sl-SI, sv-SE, tr-TR, zh-CN, zh-TW
We'll be adding es-ES to that shortly which leaves ja-JP the only remaining 1.0 localization to not yet have a 1.0.1. The Mozilla Japan folks wanted to spend more time on QA for that build so it's delayed until they give me the go-ahead.
OK, now we've got es-ES for Windows and Linux up so we're just waiting on Mac.
Posted by asa at March 3, 2005 07:48 PMWeirdness here.
I tried updating my en-GB to 1.0.1; and it failed with an error, "Not a valid ins...".
On a second try, the download part took longer, and then the installation worked perfectly.
Could this be a problem with the localised builds not having rippled through to the mirrors yet?
Posted by: Mark Tyndall on March 4, 2005 12:47 AMI've now seen two people using Firefox and not noticing the red update error nor the pop-up telling them about updates. There should definetly be another approach to forcing people into updating when a security update appears.
The updating being a full installation is annoying, but I'm sure you're working on making this as smooth as extension updates.
Furthermore, the installer asking to close firefox always appears twice to me (even on different pcs) for years now ( https://bugzilla.mozilla.org/show_bug.cgi?id=151144 )