Ah - is it that the same version is now built and published in Groovy and we can't safely copy the binary backwards? => correct.
I didn't check if we can or cannot safely copy the binary backwards, but imho we should not. This is not going via focal-security, because the security issue has already been fixed on all other arches, and riscv64 currently has best effort security support. I don't want to trigger cups security upgrade for $everyone, just because of the fix missing on riscv64 only. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 Status in cups package in Ubuntu: Fix Released Status in cups source package in Focal: In Progress 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://launchpad.net/ubuntu/+source/cups/2.3.1-9ubuntu1.1 * 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
