Archive for the 'mozilla' Category

squeeze向けの3.5バージョンの準備がまだ出来ていないので、experimentalへ3.6のアップロードはまだまだです。だが今日はMozillaがセキュリティアップデートを発表しました。Iceweasel 3.6のプレビューパッケージを使ってる皆さんは安全のために下記のパッケージをダウンロードして下さい。xulrunnerのソースコードで修正されたのでxulrunnerのパッケージしかアップデートしていません。

• i386用：
  • xulrunner
  • libmozjs
• amd64用：
  • xulrunner
  • libmozjs

申し訳ありませんがこのバージョンでリグレッションが導入されてしまいました：右上にある検索バーのアイコンが表示しない場合があります。
アップデート：実はこのリグレッションが存在していません。

ハ〜〜、日本語で書くのがこんなに難しかったっけ？

While the package is not ready yet for experimental, mostly because there are pending changes in the 3.5 branch, Mozilla released a security update today. So, here are the packages you need to be safe security-wise with Iceweasel 3.6. Please note only xulrunner packages have been updated, as the security fix lies in the xulrunner code.

• for i386:
  • xulrunner
  • libmozjs
• for amd64:
  • xulrunner
  • libmozjs

A known regression of this version is that the icons in the search box on the top right don't show up.
Update: This regression actually doesn't exist.

Iceweasel 3.6の開発が終わりそうですが3.6も3.5もバグが残っています。experimentalへアップロードする前にはそのバグを解決したいと思います。

その間に下記のパッケージを試してみて頂けたら幸いです：

• i386用：
  • iceweasel
  • xulrunner
  • libmozjs
• amd64用：
  • iceweasel
  • xulrunner
  • libmozjs

amd64のバイナリパッケージはJITコンパイラが有効にされています。（Firefoxの場合は無効。他のLinuxディストリビューションもそうだと思います）そのせいでバグが現れた場合はabout:configでjavascript.options.jit.contentを無効にして下さい。amd64のJITはテストスイートを成功しているので安定したのを期待しています。

Work on Iceweasel 3.6 is approaching an end, but there are still issues with it and with 3.5 that I want to tackle before officially pushing to experimental.

In the meanwhile, you can already try a preview package:

• for i386:
  • iceweasel
  • xulrunner
  • libmozjs
• for amd64:
  • iceweasel
  • xulrunner
  • libmozjs

The amd64 binary has the JIT compiler enabled by default (contrary to upstream default, and I guess most if not all other distros), so if you have issues with it, you'll need to disable javascript.options.jit.content from about:config. It passes the testsuite, so I expect it to be fairly stable.

After realizing Iceweasel wasn't working properly on various Debian architectures, and spending time fixing that, this week a new cairo version triggered a longstanding bug which would kill Iceweasel when closing a tab. I think I got it fixed now, but what next ?

The Firefox logo, the very reason why Iceweasel exists, is now free as in speech. Its use is still limited by trademarks, but it is free.

The news is not entirely official, but apparently the change has occurred a year ago, and the license text for the branding hasn't been changed accordingly.

Waw.

Update: Now official.

This is it! xulrunner now builds and successfully runs the checks and xpcshell-tests on all release architectures, including arm, mips, powerpc and sparc, that were all failing 2 weeks ago. 2 patch pulled from upstream, 5 patches written and sent upstream, and several more as not quite successful attempts.

What puzzles me is that e.g. the arm issue in the test suite has been known upstream for a year, yet Firefox was released on maemo (arm) without it being fixed. I mean, it only took me a few hours (if you don't count the time lost waiting for the builds to end), starting with no specific knowledge of arm, and even less of jit compilers.

Anyways, this all means work on 1.9.2 can go on.

This is what would have happened if I had waited before uploading 2.0.3-2. Courtesy of dh_install --fail-missing and its non-handling of arch:any only builds.

In there, a lot are due to dh_auto_configure not doing the right thing for autoconf 2.13 generated configure files, others are due to make setting MAKEFLAGS to "w", which prevents make -s to do what I expected it to do, armel has yet another crasher in the test suite (*sigh*), and I broke mipsel with the mips patch.

1.9.1.8-2 should fix the first two, and allow me to debug the armel issue (I disabled the test suite to be able to have the buildds generate the binaries, as they are much faster than the porterbox). Mipsel will have to wait for 1.9.1.8-3.

This also means 1.9.2 is delayed. Again. (and upstream releasing Firefox 3.5.8 one day later than scheduled didn't help either)

Update: I stand corrected, the one responsible for MAKEFLAGS setting to "w" seems to be make itself, not dh.

(maybe)

After the two updates in the previous post, I got further and eventually fixed the root of the remaining problems on ARM.

It appears I got on the wrong track at the very beginning of the investigation. My first test was to disable the JIT compiler during the tests, and it didn't affect the result. I assumed from there that the JIT compiler was doing fine and wasn't involved. Which led me to believe the alignment of the stack at 32-bits word boundary instead of 64-bits was a standard behaviour. I turns out my first test itself was wrong, because I hadn't disabled the JIT compiler at all. You need to modify the runxpcshelltests.py script to disable the JIT, and not fiddle with the javascript.options.jit.chrome preference.

The JIT compiler was misaligning the stack, and disassembling the generated code leading to broken behaviour revealed that it was doing so when setting up arguments on the stack for function calls. While I was afraid this would be difficult to fix without changing a lot of code, and first only disabled the JIT compiler, it turns out the way nanojit works by compiling the last instructions first did make it straightforward to fix.

But ARM was not the only RC buggy architecture left after sparc and powerpc were fixed. MIPS remained. Alpha fails, too, but it is not a release architecture. Update: It appears hurd fails too, but like Alpha, it is not a release architecture.

So, while I didn't want to wait 50 hours for a build, I managed to execute a failing test with the last xulrunner-1.9.1 packages that got built (before I enabled the test suite) under qemu. And I was able to track down the origin of the bug: the xpcom layer that translate function calls between languages doesn't fill arguments correctly when they are smaller than 32 bits. While the code is adapted to the mipsel case, which is little endian, it doesn't work on mips, which is big endian. I came up with a patch that should work, and which I hope won't break mipsel as a consequence. All that is left to do is to build and test the fix. I hope someone else will be able to do that for me.

All in all except a 1.9.1.8 release this week with a lot less red on the buildd status page.