On 28 Aug 2017, at 20:10, Antoine Beaupré <anar...@debian.org> wrote: > On 2017-08-28 20:53:02, Uwe Kleine-König wrote: >> Hello, >> >> On 08/28/2017 04:32 PM, Antoine Beaupré wrote: >>> Control: severity 873508 serious >>> Control: affects 873508 horst >>> >>> On 2017-08-28 15:22:20, James Clarke wrote: >>>> As discussed on IRC, ppc64 and sparc64 are also affected; while they are >>>> not release architectures and are thus less important, it would make >>>> sense to fix those (and check any other Debian architectures) at the >>>> same time. >>> >>> Also discussed on IRC is the above change in severity to make the bug >>> RC. >> >> As I didn't follow that irc discussion and fail to see why this bug >> should be severity serious. Can you please repeat the justification >> here? I would have picked "normal". > > I believe the reason is that it doesn't actually work on two supported > architectures.
Specifically that it's built for the architectures but can't actually be used. Looking at the build logs, some of the tests run as part of the test suite hit this error, but the upstream test harness always exits with code 0[0] so it's not fatal. Boo. James [0] https://anonscm.debian.org/cgit/collab-maint/sparse.git/tree/validation/test-suite#n251
