Your message dated Wed, 25 Mar 2026 14:55:38 +0000
with message-id <[email protected]>
and subject line Bug#1131575: fixed in feature-check 2.3.2-1
has caused the Debian Bug report #1131575,
regarding feature-check: FTBFS: error: failed to select a version for the 
requirement `nom = "^7.1"`
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.)


-- 
1131575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1131575
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:feature-check
Version: 2.2.0-2
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:feature-check, so that this is still
visible in the BTS web page for this package.

Thanks.

--------------------------------------------------------------------------------
[...]
 debian/rules clean
dh "clean"
   dh_auto_clean
        make -j2 clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rm -f feature-check feature-check.1.gz
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   debian/rules execute_after_dh_auto_clean-indep
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_clean --buildsystem pybuild
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_clean
 debian/rules binary
dh "binary"
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   dh_auto_build
        make -j2 INSTALL="install --strip-program=true"
make[1]: Entering directory '/<<PKGBUILDDIR>>'
install --strip-program=true -m 755 perl5/feature-check.pl feature-check
gzip -c9 feature-check.1 > feature-check.1.gz.tmp || (rm -f 
feature-check.1.gz.tmp; false)
install: WARNING: ignoring --strip-program option as -s option was not specified
mv feature-check.1.gz.tmp feature-check.1.gz || (rm -f feature-check.1.gz 
feature-check.1.gz.tmp; false)
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   debian/rules execute_after_dh_auto_build-arch
make[1]: Entering directory '/<<PKGBUILDDIR>>'
mkdir -p rust/.cargo
install -m 644 -- '/<<PKGBUILDDIR>>/debian/cargo-config.toml' 
'/<<PKGBUILDDIR>>/rust/.cargo/config.toml'
{ \
        set -e; \
        cd -- '/<<PKGBUILDDIR>>/rust'; \
        cargo build --release; \
}
error: failed to select a version for the requirement `nom = "^7.1"`
candidate versions found which didn't match: 8.0.0
location searched: directory source `/usr/share/cargo/registry` (which is 
replacing registry `crates-io`)
required by package `feature-check v2.2.0 (/<<PKGBUILDDIR>>/rust)`
perhaps a crate was updated and forgotten to be re-vendored?
As a reminder, you're using offline mode (--offline) which can sometimes cause 
surprising resolution failures, if this error is too confusing you may wish to 
retry without `--offline`.
make[1]: *** [debian/rules:22: execute_after_dh_auto_build-arch] Error 101
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:17: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit 
status 2
--------------------------------------------------------------------------------

--- End Message ---
--- Begin Message ---
Source: feature-check
Source-Version: 2.3.2-1
Done: Peter Pentchev <[email protected]>

We believe that the bug you reported is fixed in the latest version of
feature-check, 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.
Peter Pentchev <[email protected]> (supplier of updated feature-check 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: Wed, 25 Mar 2026 16:27:09 +0200
Source: feature-check
Architecture: source
Version: 2.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev <[email protected]>
Changed-By: Peter Pentchev <[email protected]>
Closes: 1131575
Changes:
 feature-check (2.3.2-1) unstable; urgency=medium
 .
   * Adjust the Salsa CI pipeline definition:
     - add a "---" marker at the top of the file
     - use recipes/debian.yml
     - use salsa-ci.yml as the config file name
     - add a `debputy reformat` check job
     - make some of the checks a bit stricter
     - drop the blhc check, not applicable for Rust
   * Tell git-buildpackage about the release/* upstream tags.
   * New upstream release:
     - now uses nom 8.x; Closes: #1131575
     - no longer uses thiserror, so drop the rust-thiserror-2 patch
     - refresh the line numbers in the python-no-executable patch
   * Build with debug symbols in release mode, too.
   * Convert the watch file to version 5 of the format.
   * Declare compliance with Policy 4.7.3; drop the implied Priority: optional.
Checksums-Sha1:
 ce24469e408fed54764d6f231f129c8f31f6edb6 2970 feature-check_2.3.2-1.dsc
 bb105234ce54e9478e9207db05af4602c8984d78 101708 feature-check_2.3.2.orig.tar.xz
 2edd7560ee2602d09d181beb32858b0b38182a63 833 
feature-check_2.3.2.orig.tar.xz.asc
 a7095bb2a99e106cd93952c952907d1c4ad63aae 11020 
feature-check_2.3.2-1.debian.tar.xz
Checksums-Sha256:
 928e732c27c5a45a7a766f9f7e00feee1069de382a3ad92a6216b08fe6f20894 2970 
feature-check_2.3.2-1.dsc
 316749ea58953803b372e0b7bcb9b32bdad91206077d5ff389f3679819b6cf7c 101708 
feature-check_2.3.2.orig.tar.xz
 60aff093e7e69cd4c0c6445f5e99f2c237146019d9ca629aa96c174309c3bc68 833 
feature-check_2.3.2.orig.tar.xz.asc
 9c21c5b78ee205aaff813b2ff5acb4e53cc14183509281c339e35ce0c9d78c97 11020 
feature-check_2.3.2-1.debian.tar.xz
Files:
 cd173888aa50bbdc876957dbc7d6842a 2970 utils optional feature-check_2.3.2-1.dsc
 87e1ed874ad353df0fa807d9111b75a9 101708 utils optional 
feature-check_2.3.2.orig.tar.xz
 feca66702597940104799c45d12b1a89 833 utils optional 
feature-check_2.3.2.orig.tar.xz.asc
 516780ed8e2ea6836e830603fb2e40d2 11020 utils optional 
feature-check_2.3.2-1.debian.tar.xz

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

iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmnD8QcQHHJvYW1AZGVi
aWFuLm9yZwAKCRBlHu+wJSffE3DiD/9XQDR6yM1rPuEcReoPaRhdUtQXTH1rlsJX
evIZ7tQpqZlJX4eYL8a2sofpuyLpnfy4ue/1DyQUjWYFtkDN/vKsiqSdr70Umes8
+916iiATwUICKM1QP9MaKJhOJY6+8jCYLxyLyJB7qN1AAV+llC7aG/G4jT9R8zfl
9D1IK6EMHHknXMvieZKzM+mrdbfv8SxNi5KIb9+tb2gqhtn4hJ6hE1hJs/p2HSwr
QH1vxONtbo9uKE03ABOOS6YU1vovR0Wuf3HKC3c6C3BBXPLXEQdBk7c/n8poHjzt
Cq1mABUU7P9ZM40eobzOpNSaEsS6fg2VHrw94agBvm1yKJCZFQ926aV3fDfEOXIf
pHgO3joWByPHVDKQ+fE3Sor/oEeLTnavBwlo6G1nhhmRivLMIQ6Bo1conZdopqNR
xv77l15cnfwyUIGserwo2mE5ACqxWSC7su2e+Z3Vg+9FKabJ5Hp08cwh+n/osycq
+yI7xIt7QKO+4IZ+VjhEZ2oRtJGYKty47CE67eaCiDnRdmXlbHJR87VWWNFrNSW+
GlPdpW+BppRILocDxpzlxofeSuzT8L9PbgUM5adnDlO+tf+xrl79auxb9qy3r4kP
JA5v5vdKG5ap7LBIdeyfe9golp5stW5mlhVS3goWOxqRNIaIfUKiGts/hBRMwe/E
HiJ8IfsR+A==
=26jR
-----END PGP SIGNATURE-----

Attachment: pgpWPRrcJmkWv.pgp
Description: PGP signature


--- End Message ---

Reply via email to