gcc-N binary packages trigger some dozen warnings of the form:

W: libgcc-11-dev: breakout-link usr/lib/gcc/x86_64-linux-gnu/11/libgomp.so ->
usr/lib/x86_64-linux-gnu/libgomp.so.1

These are wrong.

It might be a good thing to check a new lintian release against some fixed set
of packages, maybe including gcc-10 and gcc-10-cross.

Hi Matthias,

We are working on away for maintainers to request exemptions for
groups of packages. It has been a long-standing pattern in Lintian but
will soon be resolved in a better place. The current effort was
prompted by Bug#974175. Your bug will likely be resolved using that
new mechanism when it is ready.

Also, it was pointed out on IRC that this bug is similar to
Bug#968525. That remark is for our records. We do not currently expect
bug reporters to check our list of open bugs, because it is so long.

Kind regards
Felix Lechner

you misunderstand. I'm not asking for exemptions for certain packages, but that
you check for the consequences of a new warning before you upload to unstable.

the ratio of lintian noise and real issues for some packages is high, at least
for gcc-N.