package: libstdc++6
severity: serious


It seems the symbols file for libstdc++6 is missing some symbols on armel. The
build adds these with the latest version. This causes new builds that use
these symbols to pick up an (unnecessary) versioned dependency on the latest
gcc in unstable.

As this bug sometimes causes testing migrations to block on the migration of
gcc, and thus interferes with transitions, I'm filing this as serious. This
currently is the case with the opencv binNMU on armel, which is blocked behind
gcc-10, blocking the python3-defauls transition.

Maybe the build should we configured to fail when new symbols are discovered,
to avoid similar issues in the future.



Reply via email to