Bug#971589: clazy's test suite uses the default clang, while the package uses the versioned one

2020-10-31 Thread Pino Toscano
severity 971589 important
tag 971589 + needinfo
thanks

Hi,

In data venerdì 2 ottobre 2020 13:12:19 CET, Matthias Klose ha scritto:
> Package: src:clazy
> Version: 1.7-3
> Severity: serious
> Tags: sid bullseye
> 
> This is seen when updating llvm-defaults to point to 11, and then running the
> autopkg test.  The test tries to run with the updated default clang (11), but
> the package is still built using the previous 10 version.  The package itself
> uses a versioned clang for building, and also gets this dependency encoded in
> the package.  The plugins are not compatible across versions, so the test 
> should
> always use the version that the package was built for.

clazy will run against the clang version it was built with. The two
unversioned invocations of clang are done only for diagnostic (one by
the run-tests autopkgtest, and one by the upstream script used for
testing).

Considering the situation described is already what happens, I'm
lowering the severity, and requesting for more information.

-- 
Pino Toscano

signature.asc
Description: This is a digitally signed message part.


Bug#971589: clazy's test suite uses the default clang, while the package uses the versioned one

2020-10-02 Thread Matthias Klose
Package: src:clazy
Version: 1.7-3
Severity: serious
Tags: sid bullseye

This is seen when updating llvm-defaults to point to 11, and then running the
autopkg test.  The test tries to run with the updated default clang (11), but
the package is still built using the previous 10 version.  The package itself
uses a versioned clang for building, and also gets this dependency encoded in
the package.  The plugins are not compatible across versions, so the test should
always use the version that the package was built for.