PPA doesn't allow signed contributed builds
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
Only standard architectures are currently supported in the PPA.
Case 1: A package maintainer may point users to the project's PPA for apt access to the latest builds only on standard architectures (currently i386, amd64, and lpia). It would simplify the user interaction for those with other architectures (powerpc, sparc, etc.) if they could use the same sources.list line and possibly a different key to access the latest builds for their architectures.
If members of the project's team, which have upload rights for signed binary packages in the project's download area, could put those same signed binary packages in the PPA and have the uploader's identity and key-link associated, this would seem to simplify supporting other architectures while preserving some security and traceability.
Example: bazaar project download area for release 1.15.1 - powerpc build I contributed (just as version 1.15.1 was superseded by 1.16)
https:/
PPA for the bazaar project lives at https:/
Discussion thread on bazaar development mailing list:
https:/
Discussion thread on launchpad-users mailing list:
https:/
Case 2: Programmer fixes a bug in a package that is only demonstrated on a community-supported (port) architecture and wants to distribute the result to interested parties for testing with the minimal amount of pain to the tester. He creates a new signed source package and uploads it to his PPA. How can he provide the binary package to testers on the affected community-supported architecture? As an individual he doesn't have a download area. There is no way to request that his PPA build for a community-supported architecture. He could also benefit from the ability to upload a signed binary package to his PPA.
Example: f-spot - bug in v0.4.3.1 shipped in Hardy LTS crashes the program on powerpc architecture when a digital camera import starts
Launchpad bug report to which I attached the fixed powerpc binary package:
https:/
My PPA containing patched source:
https:/
affects: | launchpad → soyuz |
tags: | added: ppa soyuz-upload |
Changed in soyuz: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: feature |
Further discussion thread on launchpad-users@ starts here:
https:/ /lists. launchpad. net/launchpad- users/msg05207. html