On Wednesday, March 24 2021, Robie Basak wrote: >> This particular update is not able to cause any regressions, because > the software did not work before it. > > What about on amd64? Am I right in understanding that this bug only > affects ppc64el? But we have no choice but to rebuild for all > architectures.
True, thanks for the catch. I have updated the "Where problems could occur" section and reworded it in a way that it's clear that I meant "there can be no regressions *on ppc64el*". > Accepting, but please could you add something to the Test Plan to ensure > that the package still basically works on amd64, if that's not already > covered by existing tests? Done for both Bionic and Focal, let me know if that's enough. Thanks, -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 ** Description changed: [Impact] After installing "gosu" on Bionic/Focal on ppc64el, attempts to run the resulting "gosu" binary result in the following error message: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b41bcc7af58 for symbol `' out of range [Test Plan] You will need a ppc64el machine in order to test this. This bug happens on Bionic and Focal. # apt update # apt install gosu # gosu nobody true gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000abd18d0af58 for symbol `' out of range + If you check on (e.g.) amd64, you can see that the software works fine. + The following is on Bionic: + + # gosu nobody true + # echo $? + 0 + + Then on Focal: + + # gosu nobody true + # echo $? + 0 + [Where problems could occur] This particular update is not able to cause any regressions, because the software did not work before it. One can always say that there is a chance for a regression when rebuilding an old package from Bionic against newer libraries, but in this case I think the chances are slim to none, especially because gosu depends on very few libraries (which is unusual for a Golang application). [Original Description] After installing "gosu" on Bionic on ppc64el, attempts to run the resulting "gosu" binary result in the following error message: - gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc + gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b41bcc7af58 for symbol `' out of range I spoke briefly with mwhudson about it (recalling he might've dealt with similar issues previously) and he suggested it probably needs a rebuild and asked me to file a bug. :) (Something something PIC something something PIE something something Go toolchain.) ** Description changed: [Impact] After installing "gosu" on Bionic/Focal on ppc64el, attempts to run the resulting "gosu" binary result in the following error message: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b41bcc7af58 for symbol `' out of range [Test Plan] You will need a ppc64el machine in order to test this. This bug happens on Bionic and Focal. # apt update # apt install gosu # gosu nobody true gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000abd18d0af58 for symbol `' out of range If you check on (e.g.) amd64, you can see that the software works fine. The following is on Bionic: # gosu nobody true # echo $? 0 Then on Focal: # gosu nobody true # echo $? 0 [Where problems could occur] - This particular update is not able to cause any regressions, because the - software did not work before it. One can always say that there is a + This particular update is not able to cause any regressions on ppc64el, + because the software did not work before it. + + As for the other architectures, one can always say that there is a chance for a regression when rebuilding an old package from Bionic against newer libraries, but in this case I think the chances are slim to none, especially because gosu depends on very few libraries (which is unusual for a Golang application). [Original Description] After installing "gosu" on Bionic on ppc64el, attempts to run the resulting "gosu" binary result in the following error message: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b41bcc7af58 for symbol `' out of range I spoke briefly with mwhudson about it (recalling he might've dealt with similar issues previously) and he suggested it probably needs a rebuild and asked me to file a bug. :) (Something something PIC something something PIE something something Go toolchain.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822632 Title: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
