FTBFS during archive rebuild due to lack of singing tarballs
Bug #1966422 reported by
Dimitri John Ledkov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-signed-aws (Ubuntu) |
Triaged
|
Undecided
|
Unassigned | ||
linux-signed-azure (Ubuntu) |
Triaged
|
Undecided
|
Unassigned | ||
linux-signed-gcp (Ubuntu) |
Triaged
|
Undecided
|
Unassigned | ||
linux-signed-kvm (Ubuntu) |
Triaged
|
Undecided
|
Unassigned | ||
linux-signed-lowlatency (Ubuntu) |
Triaged
|
Undecided
|
Unassigned | ||
linux-signed-oracle (Ubuntu) |
Triaged
|
Undecided
|
Unassigned |
Bug Description
We have stopped accepting singing tarballs into the archive, because we don't want to use wrong signing keys or produce duplicate/
This results in inability to rebuild linux-signed-* packages during full archive rebuilds.
Opening this bug report to highlight this fact.
Changed in linux-signed-aws (Ubuntu): | |
status: | New → Triaged |
Changed in linux-signed-azure (Ubuntu): | |
status: | New → Triaged |
Changed in linux-signed-gcp (Ubuntu): | |
status: | New → Triaged |
Changed in linux-signed-kvm (Ubuntu): | |
status: | New → Triaged |
Changed in linux-signed-lowlatency (Ubuntu): | |
status: | New → Triaged |
Changed in linux-signed-oracle (Ubuntu): | |
status: | New → Triaged |
To post a comment you must log in.