[Bug 1973733] Re: no change rebuild to get security update out on riscv64
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 Released => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973733] Re: no change rebuild to get security update out on riscv64
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973733] Re: no change rebuild to get security update out on riscv64
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973733] Re: no change rebuild to get security update out on riscv64
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? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
