Sponsoring for resolute: Uploading libgcrypt20_1.12.0-2ubuntu1.dsc Uploading libgcrypt20_1.12.0.orig.tar.bz2 Uploading libgcrypt20_1.12.0.orig.tar.bz2.asc Uploading libgcrypt20_1.12.0-2ubuntu1.debian.tar.xz Uploading libgcrypt20_1.12.0-2ubuntu1_source.buildinfo Uploading libgcrypt20_1.12.0-2ubuntu1_source.changes
Some tips on the SRU template: * the test plan looks reasonable and (sort of) covers both failure case and success case, which is important to demonstrate that firstly there is a problem, and the patch involved solves it (could be more explicit on: run QEMU, run gpg, note failure, install proposed version, run gpg, note success, but one can derive those pieces from what's presented). * on the "where things could go wrong section", I feel it's important to point out that the extra patch affects RISC-V code-paths only so that testing of other architectures can be safely excluded, as the test plan is only exercising the RISC-V architecture. Might be worth revising those before the SRU team takes a look -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2154120 Title: [SRU] gpg buggy on RISC-V when vector length /= 128B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/2154120/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
