Your message dated Tue, 17 Mar 2026 15:50:42 +0000
with message-id <[email protected]>
and subject line Bug#1130946: fixed in silver-platter 0.8.3-2
has caused the Debian Bug report #1130946,
regarding silver-platter: FTBFS: error: no matching package found - searched 
package name: `gpgme`
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1130946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1130946
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:silver-platter
Version: 0.8.3-1
Severity: serious
Tags: ftbfs forky sid

Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202603/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:silver-platter, so that this is still
visible in the BTS web page for this package.

Thanks.

--------------------------------------------------------------------------------
[...]
 debian/rules clean
dh clean --buildsystem=rust
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
mv Cargo.lock.saved Cargo.lock || true
mv: cannot stat 'Cargo.lock.saved': No such file or directory
dh_auto_clean
        /usr/share/dh-rust/bin/cargo clean
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=2'] [] 
['-j2'] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', 'clean', '--verbose', '--verbose'],) {'check': True}
     Removed 0 files
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_autoreconf_clean -O--buildsystem=rust
   dh_clean -XCargo.toml.orig -O--buildsystem=rust
 debian/rules binary
dh binary --buildsystem=rust
   dh_update_autotools_config -O--buildsystem=rust
   dh_autoreconf -O--buildsystem=rust
   dh_auto_configure --buildsystem=rust -O--buildsystem=rust
        /usr/share/dh-rust/bin/cargo prepare-debian debian/cargo_registry
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=2'] [] 
['-j2'] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into 
/<<PKGBUILDDIR>>/debian/cargo_registry/
        cargo update
error: no matching package found
searched package name: `gpgme`
perhaps you meant:      flume, home, mime, ...
location searched: directory source `/<<PKGBUILDDIR>>/debian/cargo_registry` 
(which is replacing registry `crates-io`)
required by package `silver-platter v0.8.3 (/<<PKGBUILDDIR>>)`
dh_auto_configure: error: cargo update returned exit code 101
make: *** [debian/rules:6: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit 
status 2
--------------------------------------------------------------------------------

--- End Message ---
--- Begin Message ---
Source: silver-platter
Source-Version: 0.8.3-2
Done: Jelmer Vernooij <[email protected]>

We believe that the bug you reported is fixed in the latest version of
silver-platter, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jelmer Vernooij <[email protected]> (supplier of updated silver-platter package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 17 Mar 2026 15:13:52 +0000
Source: silver-platter
Architecture: source
Version: 0.8.3-2
Distribution: unstable
Urgency: medium
Maintainer: Jelmer Vernooij <[email protected]>
Changed-By: Jelmer Vernooij <[email protected]>
Closes: 1130946
Changes:
 silver-platter (0.8.3-2) unstable; urgency=medium
 .
   * Add librust-gpgme-0.11+default-dev to Build-Depends. Closes:
     #1130946
Checksums-Sha1:
 87d980e834595edd35ef110cc90aeb9e8b10e67e 3536 silver-platter_0.8.3-2.dsc
 6c3f82240773a92c4966f53914861f10d4d7760b 4596 
silver-platter_0.8.3-2.debian.tar.xz
 c9ae83de62b49d3f2dacef62999ce09ac21cfc65 48494 
silver-platter_0.8.3-2_source.buildinfo
Checksums-Sha256:
 cf13b9662aac6162906bdabdf4a87cb44415fecb6000283a8e279fccdd1a1740 3536 
silver-platter_0.8.3-2.dsc
 c541bf6218f1f2aa1cd44eb827d65c029a6e94bbb996f065865aa7266a50b096 4596 
silver-platter_0.8.3-2.debian.tar.xz
 7d312b7d974a63ee0621b85e01da04fb0f76faf00f5a3b8f5b04536b153a7738 48494 
silver-platter_0.8.3-2_source.buildinfo
Files:
 db5c8b5b8e1d399da52d421b7e21a9ab 3536 vcs optional silver-platter_0.8.3-2.dsc
 5530c0ea66d9b098efc8991a28bddad5 4596 vcs optional 
silver-platter_0.8.3-2.debian.tar.xz
 ae694a6a359dac42d56398cb9062969d 48494 vcs optional 
silver-platter_0.8.3-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQFGBAEBCgAwFiEE45ORIHAv6kHRgdNzhp0ktO57TaYFAmm5c5MSHGplbG1lckBk
ZWJpYW4ub3JnAAoJEIadJLTue02mamIIAMqAb4YGHTJFpj8+/dd1aEfiIRQlR666
Ol9RkEFIZ9+JxwhWeIRIZPj2rlEAcXP6bETbfl1i6hZY7nQ0MfjbKilJpfoWGcuN
4QWUt/PK4JAP3Gd/Hsm4LFpXPA5bPE/mZocaiGvYDRNFf/oodGeFM732iQ6++ZHK
qwHU3cj3wq0uWICPymeVPpUgcEopgzxgFhCBZfPzy6v3os8aW5yXAiq9SUX2ZS0Q
MgP/Fwg0Ta8vnlsJe4tdFAgXlZdkTOx5pEQ6pubxzg5x4jF3gW5qFHTEa0QQGNuZ
kx6vkvJWdxiwn7iAbsi+SxKZk48cO4dBnYd7/iy2Yg2YMRkM6XxxHKQ=
=oE34
-----END PGP SIGNATURE-----

Attachment: pgpK7W7apF4Zi.pgp
Description: PGP signature


--- End Message ---

Reply via email to