Your message dated Mon, 02 Sep 2024 13:51:28 +0000
with message-id <e1sl7sq-009skp...@fasolo.debian.org>
and subject line Bug#1080118: fixed in netavark 1.12.1-2
has caused the Debian Bug report #1080118,
regarding netavark: FTBFS: error: failed to select a version for the 
requirement `clap = "~4.4.8"`
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 ow...@bugs.debian.org
immediately.)


-- 
1080118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:netavark
Version: 1.9.0-4
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
 debian/rules binary
dh binary --buildsystem cargo
   dh_update_autotools_config -O--buildsystem=cargo
   dh_autoreconf -O--buildsystem=cargo
   debian/rules execute_before_dh_auto_configure
make[1]: Entering directory '/<<PKGBUILDDIR>>'
printf '{"package":"%s","files":{}}\n' $(sha256sum Cargo.toml | grep -Po '^\S+') 
> debian/cargo-checksum.json;
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_auto_configure -O--buildsystem=cargo
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/
   dh_auto_build -O--buildsystem=cargo
   dh_auto_test -O--buildsystem=cargo
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', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j2', 
'--target', 'x86_64-unknown-linux-gnu'],) {}
error: failed to select a version for the requirement `clap = "~4.4.8"`
candidate versions found which didn't match: 4.5.16
location searched: directory source `/<<PKGBUILDDIR>>/debian/cargo_registry` 
(which is replacing registry `crates-io`)
required by package `netavark v1.9.0 (/<<PKGBUILDDIR>>)`
perhaps a crate was updated and forgotten to be re-vendored?
dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------

The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

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

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

If you could not 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 affects, so that this is still visible in the BTS web
page for this package.

Thanks.

--- End Message ---
--- Begin Message ---
Source: netavark
Source-Version: 1.12.1-2
Done: Reinhard Tartler <siret...@tauware.de>

We believe that the bug you reported is fixed in the latest version of
netavark, 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 1080...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reinhard Tartler <siret...@tauware.de> (supplier of updated netavark 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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Mon, 02 Sep 2024 08:51:10 -0400
Source: netavark
Architecture: source
Version: 1.12.1-2
Distribution: unstable
Urgency: medium
Maintainer: Reinhard Tartler <siret...@tauware.de>
Changed-By: Reinhard Tartler <siret...@tauware.de>
Closes: 1080118
Changes:
 netavark (1.12.1-2) unstable; urgency=medium
 .
   * Upload to unstable
 .
 netavark (1.12.1-1) experimental; urgency=medium
 .
   * New upstream release: 1.12.1
   * Refresh patches
   * Compile against clap 4.5, Closes: #1080118
   * Tighten dependencies on aardvark-dns 1.12
   * Require qemu for autopkgtest tests
Checksums-Sha1:
 bdbcbef8d43f23dec1dee9716d4c54ab23d3a020 3148 netavark_1.12.1-2.dsc
 c3b16e41d832cded3b048c6c8415fd52fab914d2 19256 netavark_1.12.1-2.debian.tar.xz
Checksums-Sha256:
 5abebf481e7a3bc56fdc32614eedbe80c2162b9815c27ce50572fedf90f70942 3148 
netavark_1.12.1-2.dsc
 8a18b3cb11c02ccdc7f47c058a58ccd4c2c818b10eeb2dc08a2181a56ce3d5ac 19256 
netavark_1.12.1-2.debian.tar.xz
Files:
 f77f3dcef9faa390c382ecb9a2cc0e0b 3148 net optional netavark_1.12.1-2.dsc
 23374a67bfba8b5c06cd74a36d5cfbdd 19256 net optional 
netavark_1.12.1-2.debian.tar.xz

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

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmbVv4kUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJsv/Uw/7B7GG12Kb5t4KCMI6///OHs9kFwL6
X/lpMnbzhlbk24B3yzzXwlGm//P9Ry+hrTl57bRZYyGW/3Vpws8zSEjfL1CJN6b0
fETMSGpDT67iowoofGyRlHRfsXZS8N7Pg2pDvnJP3+XRO8z0UgC0knBnzx/PZtic
/UixWmBrG35r54f8r1wGlfO4vH+cDQuRiLR+1rfK8vd2qAvodJU4qnCrKUxLjxC1
m/6Tbp/k4VkIeAae80c5rg0AvEZP5diEvOj6caRPH9ck3E5oAQ0shwVpbfuxeGwb
3R4DFYBB38Vi/En+OxTH1ck0jK/Gcn8TPPLIwX1cHcTcPnK/qCK3G5fLpeWK/OgA
pRZO+6d62xzcQS81BHVAdYjrbjJrnFZihYrRJdYapZ//A+LgsjgaMkuGzR/8AE3I
n8gJxYWBeCIdXp2wAcjuQFtpD/yUS77RxJjxbKCRYvL2W8WWjm5EUOkeDRBp6vWn
csZZqnc7/ubflWGImPJIQE+msGF+Fcsy5ymQz+B9yCKvhlUI9392tpPldbrAHM31
Gx+S7KUA44gz2GkHGM9fRGjJTT8jM+cXf6nAWWvKbFJ9YjqEG00XuIbOUlQvjCNj
sgx/oOwEHC61MI37GMvIEzuyKm2/+R4nF133KsbLN5KaBXKGxXqqRwUdGkgMGwX6
OLep83GA7X/uUKI=
=piWN
-----END PGP SIGNATURE-----

Attachment: pgpDU8R7ZfQcN.pgp
Description: PGP signature


--- End Message ---

Reply via email to