Comments on: Almanah 0.5.0

By: Neil Williams

Neil Williams — Mon, 17 Nov 2008 00:14:32 +0000

That pc.in file in SVN is misleading - it is for 2.24 branch support, there is no pkg-config for libcryptui.so in the released seahorse 2.22 (either Debian or Ubuntu Intrepid). Debian is now frozen but seahorse 2.24 is not in experimental either. So, to answer my own question, yes, almanah must require seahorse >= 2.24 to build, as well as the Gtk+ version bump. libcryptui0 does not exist outside Ubuntu Jaunty - and Debian is currently frozen.

By: Philip Withnall

Philip Withnall — Sun, 16 Nov 2008 23:12:18 +0000

On Ubuntu at least, there is a libcryptui0 package. libcryptui is part of the Seahorse SVN, and even in the 2.22 branch there is a pkgconfig file in SVN: http://svn.gnome.org/viewvc/seahorse/branches/gnome-2-22/libcryptui/

Are you sure you've got the appropriate seahorse package installed (perhaps libcryptui0, if you're on Ubuntu or Debian)?

There's no mention of cryptui in version 0.4's configure.ac because the key selection combobox (provided by libcryptui) is new to version 0.5.

By: Neil Williams

Neil Williams — Sun, 16 Nov 2008 22:44:53 +0000

In which case, something is wrong with the check because I use seahorse but the build for 0.5 still failed, looking for cryptui via pkg-config. seahorse 2.22.3-2 does not provide any pkg-config data - does the prog need a later version?
checking for ENCRYPTION... configure: error: Package requirements (cryptui-0.0).
There's no mention of cryptui in the configure.ac of v0.4. (Feel free to file a bug in seahorse - and gpgme - upstreams asking for pkg-config support!)

By: Philip Withnall

Philip Withnall — Sun, 16 Nov 2008 18:52:04 +0000

There aren't "two methods of encryption". libcryptui is (as its name suggests) used for encryption widgets (specifically, the encryption key selector), while gpgme is used for the encryption process itself. Both are required if encryption is to be enabled.
libcryptui is provided by Seahorse.

By: Philip Withnall

Philip Withnall — Sun, 16 Nov 2008 18:50:18 +0000

I've changed the links in the post to be more intuitive.

I've no idea why those files are executable, but I'll fix that in trunk, thanks.

By: Neil Williams

Neil Williams — Sun, 16 Nov 2008 18:33:09 +0000

Further, there appears to be a problem with the two methods of encryption - crytpui is not available, gpgme should be used instead. However, the pkg-check-modules line (which appears to be new in 0.5) prevents ./autogen.sh getting as far as even looking for gpgme. It looks to me like --enable-encryption needs to be split into --enable-cryptui and --enable-gpgme (these can be mutually exclusive if you want). Otherwise, encryption would simply have to be completely disabled for 0.5.

By: Neil Williams

Neil Williams — Sun, 16 Nov 2008 18:04:47 +0000

To my surprise, clicking on the link in your blog post led to a download, instead of the homepage. I took a look and a few problems appear from the start - files like ChangeLog should not be executable, nor Makefile.am or README. Other files in src/ and data/ are executable too. It would save some hassle for the Debian maintainer if these files could be reset to 0644 as normal. This version cannot be uploaded to Debian yet anyway - gtk+2.0 2.14 isn't available in unstable due to the Lenny freeze (2.14 is in experimental).