www-client/chromium: Kerberos testers wanted

I changed the way Kerberos works in >=www-client/chromium-15.0.865.0.

If you're interested in testing, please emerge that version with USE="kerberos" and see if the Kerberos support works as intended. It'd also be nice to test with various Kerberos implementations (MIT vs Heimdal).

Even if you're not using Kerberos, if something is broken in that version please also file bugs.

The changes implemented in that version should make it work better with revdep-rebuild (the browser binary now explicitly links with Kerberos libraries instead of using dlopen, and it uses system headers instead of some modified bundled copy; this way breakages should be fixable by revdep-rebuild and not silent).

www-client/chromium: experimental support for ChromeDriver

Due to popular demand, I've added experimental support for ChromeDriver to the latest dev channel release of www-client/chromium. It is controlled by USE="chromedriver".

Please report any issues, even minor ones, with this flag. This should work "out of the box", without any additional downloads or setup. If it doesn't, I'd like to fix it.

By the way, that dev channel release also has optional support for PulseAudio. It is controlled by USE="pulseaudio".

And there are only 4 open bug reports assigned to the Gentoo Chromium Team!

How to file a good bug about FTP-related bugs in Chrome

I have just done a little clean-up of the bugtracker and closed old FTP bugs which don't have enough information to fix them. Of course those bugs can still be re-opened after reporters respond on them.

One of the most important rules for bugs is: please submit information you're asked to submit. If you're unable to follow-up, it's very likely your problem can't be fixed because of missing info.

Generally when filing an FTP-related bug, you should provide:

• version number of Chrome
• URL that causes the problem
• detailed description of the issue (steps to reproduce, expected result, actual result, etc).

Furthermore, if the FTP site is not public, just the URL or description is usually not enough to fix any problem. What's needed is either:

• raw directory listing (if you see anything like that in the error message, it should be obvious what to do), or
• Wireshark/other sniffer's dump of network traffic.

If you're unable to provide that info, but are able to identify the name of the FTP server software serving the site, there is still a chance that the problem can be reproduced by installing that FTP software on developer's machine.

Finally, when submitting the raw directory listing, please don't just copy-paste it, because that results in implicit character set conversions. Use the browser's "Save As" command to save the raw listing to disk, and then attach that file to your bug report.

www-client/chromium-14.0.835.15 dev channel release

Last dev channel release of www-client/chromium was really non-trivial to package. Here are the bugs that I had to fix:

• bug #375759 by Mathieu Zhang
• bug #375827 by fkhp
• bug #376301 by Julien Sanchez
• bug #376499 and bug #376501 by Mike Gilbert
• NaCl didn't work (missing IRT in the tarballs)
• system libvpx didn't work, had to switch back to bundled one
• WebRTC requires PulseAudio to compile

Now before you start worrying about PulseAudio (which I know many people don't want on their systems), let me remind you that this is still a hard masked ebuild, and I'll ensure that our dependency on PulseAudio becomes optional. I'm working closely with the upstream to make that possible, so please stay tuned. Feel free to add yourself to the CC list of bug #377847.

Enjoy your updates!