[Bug 1973733] Re: no change rebuild to get security update out on riscv64

2022-06-01 Thread Dimitri John Ledkov
There was another security upload on 27th of may which is built on all arches, thus this rebuild is no longer needed. please reject cups from focal unapproved. ** Changed in: cups (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: cups (Ubuntu Focal) Status: Fix

[Bug 1973733] Re: no change rebuild to get security update out on riscv64

2022-06-01 Thread Dimitri John Ledkov
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

[Bug 1973733] Re: no change rebuild to get security update out on riscv64

2022-05-18 Thread Robie Basak
Ah - is it that the same version is now built and published in Groovy and we can't safely copy the binary backwards? If so, then my second question of why this isn't going in via focal-security still stands. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1973733] Re: no change rebuild to get security update out on riscv64

2022-05-18 Thread Robie Basak
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