autopkgtests fail with gpgme1.0 1.18.0-2ubuntu1 from lunar proposed

[Rik Mills]

Release: Lunar
Version: 0.10.0-1

Failure due to the upstream gpgme-config script not being shipped by debian with gpgme1.0 1.18.0-2

Related bugs:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023601
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348

[gpgme-sys 0.10.0] running: "sh" "-c" "gpgme-config --version"
[gpgme-sys 0.10.0] sh: 1: gpgme-config: not found
[gpgme-sys 0.10.0] command did not execute successfully, got: exit status: 127
[gpgme-sys 0.10.0] Error: ()
error: failed to run custom build command for `gpgme-sys v0.10.0 (/usr/share/cargo/registry/gpgme-sys-0.10.0)`

Caused by:
  process didn't exit successfully: `/tmp/tmp.DkCl1cHFak/target/debug/build/gpgme-sys-cf9d18ac09e05ddc/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-env-changed=GPGME_PREFIX
  cargo:rerun-if-env-changed=GPGME_INCLUDE
  cargo:rerun-if-env-changed=GPGME_LIB_DIR
  cargo:rerun-if-env-changed=GPGME_LIBS
  cargo:rerun-if-env-changed=GPGME_CONFIG

  --- stderr
  running: "sh" "-c" "gpgme-config --version"
  sh: 1: gpgme-config: not found
  command did not execute successfully, got: exit status: 127
  Error: ()

[Rik Mills (rikmills)]

Turns of that rust-gpgme-sys 0.10.0-2 in proposed has a fix, but was FTBFS when synced. On poking the builds again, they built. Tests now pass when the trigger for 0.10.0-2 is added.

https://autopkgtest.ubuntu.com/packages/r/rust-gpgme-sys/lunar/amd64