Intltool: A story on how a bug in one piece of software can kill all the others

0.40.6 version of intltool has a nasty bug in handling of LINGUAS variable. It causes localization (i.e .mo files) not to be built if your LINGUAS environment variable is set (I have it set to “tr”). At first, the issue popped up in GNOME packages (nautilus, seahorse and probably quite more that was fixed before I noticed) And now it started hitting other applications with tarballs generated using broken intltool. I first noticed it in Liferea, and then came Geany.

So users, upstream developers and downstream maintainers; if you notice or you’re reported of a package that appears untranslated even though the package has translations (langcode.po) please report it (for users), fix your tarball for the next release (upstream), fix your package (downstream)

Libnotify Java bindings – Adding actions

Java-Gnome bindings doesn’t support callbacks at the moment. It can generate code for signals only. To add action callbacks, I reimplemented it as action signal. Here’s an example code to show how to add signals:

notification.addAction("a", "Action 1.a", new Notification.Action() {

    public void onAction(Notification source, String action) {


The implementation currently has one drawback. Signals are not disconnected properly. This causes two issues. One, signals aren’t disconnected if actions are removed with clearActions(). Two, if actions with same actionIDs are added signals for all are triggered. Andrew will be adding support for signal disconnection to java-gnome and I’ll be using it in libnotify branch.

Bringing Libnotify to Java

I’ve been contributing to java-gnome for sometime. It was generally build system and test improvements with little bits of coverage addition that was merged to mainline for now. Although I began libnotify branch later than other two (libsexy and vte) the branch improved way faster than the others. The Bazaar branch has nearly full coverage of the underlying API.

The example included shows a critical low-battery warning with gnome-power-manager icon sitting in the notification area (Assuming you have it installed).


I’ll be implementing the missing action covarage now and try to make it to our next release 4.0.12. And of course thanks goes to our lead Andrew Cowie for his help in development and Guillaume Mazoyer for testing it and providing feedback.

Hello World

After more than 2 years of blogging in Turkish, here’s my “Hello World” post in English.

StatCVS and StatSVN

Here are 2 tools for generating repository statistics for source trees controlled with CVS and SVN. Both tools can generate stats for subtrees. Here’s how to generate stats for a CVS checkout:

  • cd to module root or a subdirectory which the stats will be generated for.
  • Create the cvs log by executing
    cvs log > logfile.log
  • Execute
    statcvs logfile.log . -o -output-dir /path/to/stats

    to generate stats.

and for SVN:

  • cd to module root or a subdirectory which the stats will be generated for.
  • Create the svn log by executing
    svn log -v --xml > logfile.log
  • Execute
    statsvn logfile.log . -output-dir /path/to/stats

    to generate stats.

Now you can browse, upload, do whatever you want with generated stats. I generated stats for our java-config-2 project. The sample StatSVN output can be viewed at Also Jeremy generated CVS stats for gentoo-x86/sys-apps which can be viewed at

Further Reading: You can read the following manuals for detailed information.

WARNING: Please do not run cvs log on Use rsync to mirror the portage tree from AnonCVS provided by infra and run cvs log on the local mirror.

Sandbox violations due to regeneration of Python bytecode

Due to a bug in script distributed with Python pyc/pyo files’ modification times are earlier than tat of py files. If any Python packages (such as java-config which is used for all Java packages) are used during compile phase the bytecode is regeneretad and sandbox-1.3.3 started catching that as a violation. Sandbx version 1.3.4 and above ignores this problem as a workaround. So if you hit any issues similar to bug 256953 or its duplicates, please update your sanbox. I thank Martin von Gagern for working on fixing the issue and taking it to upstream.

java-dep-check-0.3 and weird bugs it discovered

The tool Betelgeuse wrote was scanning Java packages for unneeded dependencies. It was scanning the registered jar’s for any referenced classes and generated a list of classes in dependent packages/jars to see if any of them are redundant. Back on December I came up with an idea to use that information to dig out for an opposite fact. Packages that reference classes which are not provided by it’s dependencies not itself. It was bug #252249 which inspired me. The initial ebuild was definitely missing a dev-java/sun-jai-bin .dependency which I wanted to verify. The intention was to discover missing dependencies. of binary Java packages.

After I got it working without (hopefully) false positives it was then time to see the results. I first ran it in over the packages installed on my system. Thanks to Diego who kindly ran it in his tinderbox which had most of the Java packages in portage installed and posted the output. I was surprised about the outcome. There were many source based packages that it reported to depend on missing classes. Roughly examining the list I saw that some packages installing ant tasks were missing an ant core dependency and fixed a few. Another set of packages seem to package its unit tests (see java-wakeonlan for example) Digging out others I figured out a third kind of problem. Packages missing already generated jars or classes in the final package.env entry. Those (openoffice,xulrunner,java-access-bridge) reported missing classes that was already provided by themselves. They either didn’t install the jar at all or installed but not registered them (we have java-pkg_regjar provided by java-utils-2 eclass which registers an already installed jar). But java-access-bridge had an interesting bug which was there for ages. The generated jar misses already compiled classes due to wildcards not being expanded recursively during make and reported the bug to upstream. Mindterm exibits a similar bug. Classes were missed out in jars because they weren’t in the hardcoded list of classes to package.

As a final word, I’ll be taking next days investigating output generated in Diego’s tinderbox, and fixing the packages.

Addition: Add note about net-misc/mindterm bug.