autopkgtests fail with gpgme1.0 1.18.0-2ubuntu1 from lunar proposed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gpgme1.0 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
rust-gpgme-sys (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
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:/
https:/
[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/
Caused by:
process didn't exit successfully: `/tmp/tmp.
--- stdout
cargo:
cargo:
cargo:
cargo:
cargo:
--- stderr
running: "sh" "-c" "gpgme-config --version"
sh: 1: gpgme-config: not found
command did not execute successfully, got: exit status: 127
Error: ()
tags: | added: update-excuse |
description: | updated |
Changed in rust-gpgme-sys (Ubuntu): | |
status: | Fix Committed → Fix Released |
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