Signed PPA instructions need improvement
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
The follow message displayed on a signed PPA page is not correct English - the sentence structure requires the definite article 'the':
This repository is signed with 1024R/249AD24C OpenPGP key.
A better phrase would be:
This repository is signed with the OpenPGP key 1024R/249AD24C
As the major use of the key id at the moment is to cut and paste into a terminal window, I would further suggest that the following be used (space before and after the '/' seperator, and the hyperlink removed from the keyid onto 'lookup'):
This repository is signed with the OpenPGP key 1024R / 249AD24C (lookup)
The second sentence highlights the other problem:
Follow these instructions for installing packages from this PPA
The instructions are not for installing packages from *this* PPA - this is a lengthy document describing PPAs in general, and doesn't mention *this* PPA at all. The 'Follow these instructions' link should popup instructions for adding *this* PPA to your apt configuration with the bare minimal disclaimers we need, and a hyperlink to the 'for more information' page on the wiki. The popup providing instructions for adding this PPA to the users apt configuration should be short - I imagine no more than 5 or 6 lines long, containing text that can be easily cut and paste into a terminal window including the correct key id for *this* archive:
"""
The packages in this archive are not supported by Launchpad or Canonical. By installing packages from this archive you are placing your trust entirely on the package providers. If you feel they are a trustworthy source of software, you can continue by issuing the following command in a terminal window:
gpg --keyserver keyserver.
For further information, please see our [PPA documentation].
"""
| Stuart Bishop (stub) wrote | #1 |
| Changed in soyuz: | |
| status: | New → Triaged |
| Julian Edwards (julian-edwards) wrote | #2 |
| Changed in soyuz: | |
| importance: | Undecided → Medium |
| milestone: | none → pending |
| Julian Edwards (julian-edwards) wrote | #3 |
| Changed in soyuz: | |
| milestone: | pending → none |
| status: | Triaged → Incomplete |
| Stuart Bishop (stub) wrote | #4 |
| Changed in soyuz: | |
| status: | Incomplete → Triaged |
| Michael Nelson (michael.nelson) wrote | #5 |
| Changed in launchpad: | |
| importance: | Medium → Low |
Of course, the command line should work which demonstrates why a cheat sheet is necessary with current Ubuntu releases. I once forgot the key id and managed to import my entire keyring with apt-key...
gpg --keyserver keyserver.
gpg --armor --export DEADBEEF | sudo apt-key add -
(or a one liner that doesn't leave the key in the users main keyring if a sane one exists).