Iceweasel 5.0 in experimental
I just pushed Iceweasel 5.0 to Debian experimental. Why not unstable, some will ask? Well, because we still need to give some time after a first notice before breaking plenty of packages (Thanks to Julien Cristau for the MBF, by the way).
I also discontinued the Iceweasel 4.0 backport for Squeeze, as Iceweasel 4.0 won't be receiving security updates. Speaking of security updates, 3.6.18 was also made available on mozilla.debian.net for Wheezy, Squeeze and Lenny. However, I still have to backport the necessary patches to 3.5 in Squeeze and 3.0 in Lenny. My real life schedule wasn't compatible with the security release schedule, so I got late on the security backport train.
In the coming weeks, there will also be some additional changes to the mozilla.debian.net repository, but I'll give more details when that happens.
2011-06-22 02:41:30+0900
You can leave a response, or trackback from your own site.
2011-06-22 12:02:49+0900
when we can expect deb package of icedove 5.0 (beta)? now i’m using thunderbird tar.gz
2011-06-22 14:34:18+0900
Great that you quick to jump on it!
2011-06-22 16:24:05+0900
That was quick. Thank you.
2011-06-23 17:21:10+0900
It’s kinda funny to see such a great response in packaging with how quick they are done, but see sid still contain such old stuff :-)
2011-06-24 04:53:49+0900
Andrew: what part of the first paragraph did you not understand?
2011-06-24 11:15:11+0900
Could you also build the iceweasel-l10n packages for your repository? It’s unfortunate that using these packages means losing translations.
2011-06-24 21:47:19+0900
+1 for adding the iceweasel-l10n packages to the repository.
2011-06-25 17:07:45+0900
I only see 4 in experimental…?
2011-06-26 04:42:24+0900
Looks like 5 is held up in NEW, thats why I didn’t see it.
2011-06-26 11:33:50+0900
[…] to themozilla.debian.net [18] repository, but I'll give more details when that happens". 17 : http://glandium.org/blog/?p=2108 18 : http://mozilla.debian.net/ Further interviews —————— There has been two further […]
2011-06-28 09:30:30+0900
+1 for adding the iceweasel-l10n packages to the repository, many of my familymembers are not fluent in English.
2011-06-29 08:22:32+0900
You can install as an extension language:
for 64-bit
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/5.0/linux-x86_64/xpi/
or
for 32-bit
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/5.0/linux-i686/xpi/
if there is any difference.
2011-06-29 11:19:39+0900
xpi is an OK alternative. But if you have lot’s of users, a deb-package is better. I know how to install xpi as a global extension, but still nothing beats a deb-package.
2011-06-29 11:19:59+0900
oh, and thanks for the link to the xpi files.
2011-07-08 17:10:10+0900
Mike, I understand from this blog post that you’re the one and only person who ports security update to older Debian release.
What are your plan with the new rapid release schedule ?
I see several possibilities :
– it’s not decided yet.
– you will not port fixes anymore, updates to stable debian release will update to the latest stable firefox in debian releases that include a Firefox newer than 3.6
– you keep on porting fixes, so the Firefox release that’s gets integrated inside Debian Stable becomes in effect a LTS version of Firefox. In that last case, I think it would be a big win for you to try to synchronize with some other people who have the same needs to mutualize the effort.
2011-07-08 18:44:41+0900
jmdesp: As far as I know, only RedHat supports older versions, and that’s only for the Gecko 1.8.1 code base. Debian might well be alone supporting 3.0 and 3.5. I will try my best to support them as long as possible and desirable (3.0 is not going to be supported after Lenny EOL).
2026-09-19 08:43:14+0900
The careful move to experimental makes sense, especially with security backports and the risk of breaking packages. The repeated requests for iceweasel-l10n also highlight how important localized releases are. Reference2Video could help create concise visual guides for repository changes, package testing, or language support workflows from screensh
reference to video
2026-09-26 04:47:21+0900
The careful decision to put Iceweasel 5.0 in experimental, while security updates and backports catch up, makes sense—especially with the NEW queue and missing localization packages in the comments. For release notes or repository announcements, PasteFonts could help compare and copy distinctive Unicode headings, though plain text is still best for
copy and paste fonts
2026-10-02 06:08:17+0900
The note about holding Iceweasel 5.0 in experimental until package breakage could be assessed, alongside the delayed security backports, shows how important clear release tracking is. For anyone documenting these changes, an APA generator could quickly format Debian notices and technical sources into a consistent reference list.
apa citation generator
2026-10-04 02:14:18+0900
The explanation for keeping Iceweasel 5.0 in experimental until the first notice had time to land makes sense, especially with so many packages potentially affected. The notes about security backports and the missing localization packages are helpful context for Debian users.
AI virtual try on
2026-10-05 22:36:42+0900
The note about holding Iceweasel 5.0 in experimental until package dependencies could be checked is a good reminder that careful release management matters. For teams preparing physical labels or inventory during software rollouts, FreeBarcodeGen can turn text or CSV/TSV lists into downloadable barcode files without sending the data out of the brow
FreeBarcodeGen
2026-10-09 13:43:22+0900
Thanks for explaining why Iceweasel 5.0 went to experimental first, especially the need to avoid breaking packages and the catch-up work on security backports. The discussion about language packages also shows how much careful packaging matters to everyday users.
Burning Bridges AI video generator
2026-10-10 16:49:36+0900
Sensible move holding Iceweasel 5.0 back in experimental for now. Dealing with mass bug filings and breakages across dependent packages is always messy, so giving maintainers a buffer before pushing to unstable makes a lot of sense.
I ended up trying Veo 3.1 Video Generator this week while putting together a short changelog clip for our team updates. A coworker had forwarded a link discussing veo 3.1 ????????? access, so I tested a basic prompt for a retro terminal boot animation; it took about two minutes to render a clean four-second cut, which saved me from having to piece it together manually.
2026-10-10 21:48:25+0900
The staged move to experimental makes sense given the risk of disrupting packages, and it’s good to see the security backports called out too. The comments about missing localization packages highlight how much packaging details matter for users. Genjutsu AI is a very different tool, but its preset-based motion transfer and object swaps offer a sim
Genjutsu AI
2026-10-11 03:43:02+0900
Pushing to experimental first definitely saves a lot of headaches, especially with how rapid upstream releases can cascade and break desktop dependencies. Giving maintainers time to catch up on the mass bug filing before dumping it into unstable is the sane route.
I take a similar staged approach with my own rendering workflow whenever new updates land. Lately I’ve been running Kling 4.0 for product b-roll tests, and locking in a clean starting reference image with a slow tilt-down prompt has been my go-to sanity check to see if edge lighting stays consistent across the clip.