> Would it be ok to add them to override with this reasoning? Hi, yes you can override them, but make it detailed and trackable please. For example finding the exact reason in that PR you posted for a given issue is hard.
Not: "also broken in llvm-20 let us not care either" lintian-override ... lintian-override ... lintian-override ... More like: # LLVM-20 has the same issues, we'd aim to resolve them over time. The overrides get # individual explanations where we know the details # This one is broken as it is an intentionally bad artifact for tests lintian-override ... # These windows binaries are not used in the final package due to ... lintian-override ... # These can't be unpacked due to ... lintian-override ... If any of them have upstream or Debian or Ubuntu bugs to further track them down, please refer to those. And if they don't then create them please. That way it will not stay ignored forever and maintainers/reviewers will have an easy way to check if this changed (by checking the bug state) Thereby actually like: # LLVM-20 has the same issues, we'd aim to resolve them over time. The overrides get # individual explanations where we know the details # This one is broken as it is an intentionally bad artifact for tests (LP: #1234) lintian-override ... # These windows binaries are not used in the final package due to ... (upstream foo/issue/1234) lintian-override ... # These can't be unpacked due to ... (Debian bug #1234) lintian-override ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2133814 Title: NEW package request: llvm-toolchain-rocm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2133814/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
