Hi Faidon, On 05-11-2023 21:41, Faidon Liambotis wrote:
Hi Paul, Thank you for your report. This is caused #1052002, which I had marked as affects: wasmedge previously.
Sorry for not checking that, but because you marked it as affecting the *binary* package wasmedge, it doesn't show up looking for bugs in the source package wasmedge (that may be a bts bug). Because this is a FTBFS issue, I recommend you to mark it affects src:wasmedge instead of wasmedge.
I don't know how you'd like ot handle this w.r.t. the BTS, and testing migrations. I'm inclined to just reassign/merge it to the bug above, but I'll wait for your opinion first.
That's probably OK, I see you already did that.
Also, I'm not sure I understand how clang migrated to testing when it introduced an autopkgtest regression in another package. Isn't autopkgtest integration in britney supposed to prevent this kind of thing from happening?
britney prevents this kind of things currently only for *direct* reverse (test) dependencies. In this case we have:
test/Depends: clang (from src:llvm-defaults) -> (Depends) clang-16As I'm pretty sure you meant not clang, but one of the versioned clang packages, britney didn't see the breakage. There are multiple ways to improve this: * britney should look at all transitive dependencies (we lack the resources and also not environmentally friendly) * britney could be taught to translate (automatically or via configuration) "-defaults" packages to their real packages. This would be good for multiple ecosystems, patches welcome. * Individual packages that are sensitive could use the `hint-testsuite-triggers` trick from the autopkgtest spec [1] and add the current real packages. That's a PITA to maintain though, and adding versions that you don't really test is wrong.
Paul[1] https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst
OpenPGP_signature.asc
Description: OpenPGP digital signature
