In my opinion, this smells like a Policy violation, but I'm setting the
severity at non-RC since it's not my judgment that matters, but that of
the CI team.

Because DEP-8 tests (autopkgtests) speed up migration and have other
consequences on the release process, any tests that do not exercise a
significant amount of functionality must be marked with
Restrictions: superficial. I was wondering whether GPGME had any
autopkgtests because I was interested in writing one.

The Python test only checks that the gpg module can be imported and a
context obtained, but doesn't do anything with it. Only checking if a
module can be imported is the go-to example of a superficial test.

The checky2106 test likewise doesn't actually exercise any actual
functionality from GPGME, or even include the appropriate header.

If you'd like a significant autopkgtest, I'd be glad to write one, but
I'd like to bring to your attention that these existing tests really
ought to be marked superficial.

Hello,

this took longer than necessary, I'm now sifting throught the long
backlog of bug repourts.

John Scott wrote...

They are indeed very basic and far from what autopkgtests should do.

Please do. The situation needs to be improved and I'm happy for
everything that helps.

    Christoph