Comment 9 for bug 799225

Jean-Louis: regarding WARNING vs. ERROR you're partly right. In case the build stops this seems to be rather an error than a warning. However, the check is some guesswork which is intended to *warn* me in cases where the check fails on first build. In this particular case the check didn't fire for my Debian build. I assume the reason why the check didn't fire is that the new symbols in libaqbanking that picked up the newer Gwenhywfar version were generated by a Gwenhywfar macro. In the sense of the Debian Policy this means that the newer version in the build-dep is not required, i.e. the check including its warning message was wrong! Without this check the package builds without errors and with the older Gwenhywfar version installed.

Anyways, this check helps me (in some cases) to upload a package with insufficient build dependencies.