Package: cpputest Version: 4.0-2 Severity: serious Justification: policy 5.6.34.2 Control: affects -1 + src:amd-aie-rt User: [email protected] Usertags: ftcbfs
cpputest is wrongly marked Multi-Arch: foreign. It is sold as a package that you can depend on and have cpputest work. That way, it exposes libcpputest-dev. So when amd-aie-rt Build-Depends: cpputest, it receives a build architecture libcpputest-dev and when CMake tries to find it, it finds nothing. This is a straight forward violation of policy section 5.6.34.2. What is not clear to me is how to correctly handle this. A simple way of handling the exposure is turning cpputest Arch:any + M-A:same. At that point, the split between cpputest and libcpputest-dev may no longer be useful. Moving all the files to libcpputest-dev and having it provide cpputest would be an option. Another option is to stop claiming that cpputest was the main package. If it were dropping its dependency on libcpputest-dev and saying that it was scripts and examples, users would have to depend on libcpputest-dev explicitly and things would work on their end. So the main question here is: When someone issues a dependency, can they expect to be able to link the cpputest library? Helmut
