Ubuntu
gpgme1.0 package

saucy dist-upgrade: Pulls in old GTK2 pinentry stuff

Bug #1194164 reported by Martin Pitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gpgme1.0 (Ubuntu)
Fix Released
High
Canonical Desktop Team

Bug Description

The recent gpgme versions changed to gnupg2, which pulls in a lot of new stuff:

$ LANG= sudo apt-get dist-upgrade
[...]
The following NEW packages will be installed:
  gnupg-agent gnupg2 libassuan0 libgcr-base-3-1 libgcr-ui-3-1 libksba8 pinentry-gtk2 python-secretstorage

We really don't want the pinentry-gtk2 stuff, as we already have gnome-keyring and don't want to add new GTK2 dependencies.

Martin Pitt (pitti)
Changed in gpgme1.0 (Ubuntu):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
summary: - Pulls in old GTK2 pinentry stuff
+ saucy dist-upgrade: Pulls in old GTK2 pinentry stuff
Sebastien Bacher (seb128)
Changed in gpgme1.0 (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Sebastien Bacher (seb128)
Changed in gpgme1.0 (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Iain Lane (laney) wrote : Re: [Bug 1194164] Re: saucy dist-upgrade: Pulls in old GTK2 pinentry stuff

As discussed on IRC last friday (21st June), this is because libgpgme11
switched Depends from gnupg to gnupg2. The latter has Depends:
gnupg-agent which has Depends: pinentry-gtk2 | pinentry-curses |
pinentry. Some possible solutions in no particular order are

  - Switch libgpgme11 back to gnupg
  - gnome-keyring Provides: pinentry (not sure that would be correct)
  - Define a new virtual package which gnome-keyring and gnupg-agent can
    Provide and have gnupg2 Depend on that instead.
  - Drop Depends from gnupg2 to gnupg-agent — gnupg doesn't have
    anything like that.

Hmm?

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

Revision history for this message
Iain Lane (laney) wrote :

On Mon, Jun 24, 2013 at 03:44:10PM -0000, Sebastien Bacher wrote:
> ** Changed in: gpgme1.0 (Ubuntu)
> Status: Confirmed => Fix Committed

Looks like Seb went for "Switch libgpgme11 back to gnupg" (ish) ;-)

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gpgme1.0 - 1.4.2-0.1ubuntu2

---------------
gpgme1.0 (1.4.2-0.1ubuntu2) saucy; urgency=low

  * debian/control: Depends on "gnupg | gnupg2" rather than gnupg2,
    default to the old version since the new one depends on gpg-agent,
    pinentry-gtk2, and a bunch of other packages we don't need/want in the
    default installation (lp: #1194164)
 -- Sebastien Bacher <email address hidden> Mon, 24 Jun 2013 17:39:29 +0200

Changed in gpgme1.0 (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.