no change rebuild to get security update out on riscv64
Bug #1973733 reported by
Dimitri John Ledkov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned |
Bug Description
no change rebuild to get riscv64 build out
[Impact]
* riscv64 build of cups security update failed, and then succeeded in groovy. See https:/
* it means that focal-updates & focal-security are lacking a security update of cups on riscv64
* do a no change rebuild of cups as an SRU to get updated cups package out on focal
[Test Plan]
* autopkgtests pass
* riscv64 build is successful
[Where problems could occur]
* As usual, no change rebuilds of packages may introduce miss builds.
[Other Info]
* currently snap review tooling reports that cups has CVEs on riscv64 when one builds base:core20 snaps for riscv64.
summary: |
- no change rebuild to get riscv64 build out + no change rebuild to get security update out on riscv64 |
Changed in cups (Ubuntu): | |
status: | New → Fix Released |
description: | updated |
Changed in cups (Ubuntu Focal): | |
status: | New → In Progress |
To post a comment you must log in.
I'm not sure I follow. I see a retry button for the failed riscv64 build. Can't we just hit that?
If there's some reason that won't work, then why is this not going through the security sponsorship queue? If we do it as an SRU, then it'll hit focal-updates only, and focal-security will be left behind. What's the plan for that?