should not require that .dsc files be signed by an active key
Bug #439012 reported by
LaMont Jones
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I have developed a habit of only signing the .changes file when I sponsor an upload, and letting the sponsoree have the signature on the .dsc. In debian, this has always worked, and provides me with some level of being able to say "I sponsored _his_ upload", rather than claiming that I was responsible for the source code.
When I did that with an upload today, I got:
Rejected:
File limesurvey_
On the same upload that is currently sitting in debian's NEW queue, and will (eventually) be synced into ubuntu from sid, complete with the deactivated key's signature on the .dsc....
maybe we could let it come through when the source.changes file is signed by an active key???
lamont
Revision history for this message
| Celso Providelo (cprov) wrote | #1 |
| tags: | added: soyuz-upload |
| Changed in soyuz: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
To post a comment you must log in.
For the record, the deactivated key belongs to https:/
And I think your suggestion is reasonable, DSCs signed by keys deactivated in LP will cause no harm and we will continue to be able to link them to their signers.