Ubuntu
aptly package

Aptly 1.2.0 tries to use incompatible GPG2

Bug #1779760 reported by Kyle Edwards
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aptly (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Because Ubuntu Bionic ships with GPG2 as "gpg", Aptly tries to use this instead of "gpg1". However, the command line options for GPG2 are different from GPG1, and Aptly hasn't yet been fully ported to GPG2. The only version they currently officially support is GPG1.

In addition, Aptly's "internal" PGP implementation doesn't seem to properly support subkeys (which we are using), so that won't work for us as a workaround.

This was fixed as of upstream pull request #734. It makes sure "gpg" is the correct version, and if not, it falls back to "gpg1". The simplest fix for this issue would be to backport these commits.

Tags: bionic
Hans Joachim Desserud (hjd)
tags: added: bionic
Revision history for this message
Alexandre Viau (aviau) wrote :

This should be available in 1.3 which is in the archive.

Changed in aptly (Ubuntu):
status: New → Fix Released
Revision history for this message
Kyle Edwards (kylefromkitware) wrote :

1.3.0 is available in Cosmic, but Bionic still has 1.2.0. Therefore, the bug is still not fixed in Bionic (which is a long-term support release.) What is the solution for people who use Bionic and would rather stick with LTS?

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.