ports/135952: gnupg-2.0.12 breaks gnome2/seahorse-agent

[Giorgos Keramidas]

>Number: 135952
>Category: ports
>Synopsis: gnupg-2.0.12 breaks gnome2/seahorse-agent
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Jun 23 07:10:03 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Giorgos Keramidas
>Release: FreeBSD 8.0-CURRENT i386
>Organization:
>Environment:

System: FreeBSD kobe 8.0-CURRENT FreeBSD 8.0-CURRENT #0 hg@fcf8b8801d8a: \
Sun Jun 21 04:32:08 EEST 2009 build@kobe:/usr/obj/usr/src/sys/KOBE i386

>Description:

The GnuPG team has chosen a minor-minor release (2.0.12) to introduce a
completely incompatible agent protocol change, namely the new "GETINFO"
command. Putting aside the silliness of completely breaking the wire
protocol in a minor-minor release, this is causing problems with Gnome 2.X
programs because how the seahorse-agent cannot respond to key requests.

Since the update to 2.0.12 my seahorse-agent fails for all agent requests
with the following in /var/log/messages:

Jun 23 09:15:42 kobe seahorse-agent[65601]: unrecognized command: GETINFO

>How-To-Repeat:
>Fix:

Not sure. I don't see any changes in the Subversion repository of seahorse
that would fix this:

http://svn.gnome.org/viewvc/seahorse/

The last commit in that repository is 2 months old, so it may take some
time before the "GETINFO" command of the new gnupg-2.0.12 is supported.

As a workaround, I've downgraded the port to 2.0.10 locally, but this may
not be a very good idea in the long run :-/

>Release-Note:
>Audit-Trail:
>Unformatted:
_______________________________________________
freebsd-p...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs
To unsubscribe, send any mail to "freebsd-ports-b...@freebsd.org"