Bug#1125722: dpkg-gensymbols: error if symbols file is too lax

Package: dpkg-dev
Version: 1.23.3
Severity: wishlist

I've come across several symbols files that use wildcards to match
basically any symbol. Doesn't this make the symbols file kind of moot,
as it will never detect any symbols that got removed and it will
always match any symbols added?

Could dpkg-gensymbols start erroring if it encounters files like this,
and fail the build to prevent such symbol files from getting into any
release?

Example:

libssl3t64.symbols

libcrypto.so.3 libssl3t64 #MINVER#
* Build-Depends-Package: libssl-dev
 *@OPENSSL_3.0.0 3.0.0
 *@OPENSSL_3.0.3 3.0.3
 *@OPENSSL_3.0.8 3.0.8
 *@OPENSSL_3.0.9 3.0.9
 *@OPENSSL_3.1.0 3.1.0
 *@OPENSSL_3.2.0 3.2.0
 *@OPENSSL_3.3.0 3.3.0
 *@OPENSSL_3.4.0 3.4.0
 *@OPENSSL_3.5.0 3.5.0
libssl.so.3 libssl3t64 #MINVER#
* Build-Depends-Package: libssl-dev
 *@OPENSSL_3.0.0 3.0.0
 *@OPENSSL_3.2.0 3.2.0
 *@OPENSSL_3.3.0 3.3.0
 *@OPENSSL_3.4.0 3.4.0
 *@OPENSSL_3.5.0 3.5.0

Another example which I fixed yesterday:
https://salsa.debian.org/debian/xz-utils/-/commit/77d9470ff01acac116af14c28bd037cdf0f3e640