Your message dated Thu, 02 May 2024 18:37:22 +0000
with message-id <e1s2bj4-002skk...@fasolo.debian.org>
and subject line Bug#1069350: fixed in netavark 1.4.0-4.1
has caused the Debian Bug report #1069350,
regarding netavark: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo
build returned exit code 101
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.)
--
1069350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netavark
Version: 1.4.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64.
Relevant part (hopefully):
> 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=4'] []
> ['-j4'] 0
> debian cargo wrapper: rust_type, gnu_type: aarch64-unknown-linux-gnu,
> aarch64-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=4'] []
> ['-j4'] 0
> debian cargo wrapper: rust_type, gnu_type: aarch64-unknown-linux-gnu,
> aarch64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j4', '--target', 'aarch64-unknown-linux-gnu'],) {}
> error: failed to select a version for the requirement `sysctl = "^0.4"`
> candidate versions found which didn't match: 0.5.5
> location searched: directory source `/<<PKGBUILDDIR>>/debian/cargo_registry`
> (which is replacing registry `crates-io`)
> required by package `netavark v1.4.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
The full build log is available from:
http://qa-logs.debian.net/2024/04/20/netavark_1.4.0-4_unstable-arm64.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240420&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: netavark
Source-Version: 1.4.0-4.1
Done: Peter Michael Green <plugw...@debian.org>
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 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Michael Green <plugw...@debian.org> (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: SHA256
Format: 1.8
Date: Thu, 02 May 2024 17:08:20 +0000
Source: netavark
Architecture: source
Version: 1.4.0-4.1
Distribution: unstable
Urgency: medium
Maintainer: Reinhard Tartler <siret...@tauware.de>
Changed-By: Peter Michael Green <plugw...@debian.org>
Closes: 1064580 1069350
Changes:
netavark (1.4.0-4.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Apply upstream patch for new version of rust-nix (Closes: #1064580)
* Relax cargo dependency on sysctl crate (Closes: #1069350)
Checksums-Sha1:
de0efccf3d31b33ab89c90017dcec0c99d812195 2700 netavark_1.4.0-4.1.dsc
856657734fe21e706ec2b561669cb4623f020496 5568 netavark_1.4.0-4.1.debian.tar.xz
c3e9e9efa0857ac878c040c3a71c9750b3f49667 23666
netavark_1.4.0-4.1_source.buildinfo
Checksums-Sha256:
85e85b3a814a4acbb850898228f75322605329b00048f22eabcfa45ffe0d9f2d 2700
netavark_1.4.0-4.1.dsc
983e909cc799cfc99477fa812f9ad973f13bb1c98a19d76fdc6c631a174586ef 5568
netavark_1.4.0-4.1.debian.tar.xz
1bdfe0afa36692d913c38807ea5bcd4be15c3105180e42a906bd1b67db67cd7d 23666
netavark_1.4.0-4.1_source.buildinfo
Files:
8a385e0c948542d83e24b8b7098a1858 2700 net optional netavark_1.4.0-4.1.dsc
36aefaaf6dc1df98002ea8630569f798 5568 net optional
netavark_1.4.0-4.1.debian.tar.xz
fbc1a0f2ee234e84db66d30d9f1ef224 23666 net optional
netavark_1.4.0-4.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmYz2mIUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvPWA//aKcJXr9/87UmqGQ+jVDo64qS9h13
F6kUL4jtC6Udw7L1Hg5CbdTSYIYV8efcENu232qw4drJ75/CKQg/XeE/fEd6HHGW
hwgVA8yCGKjTY9/Ypb7t5e/w28kHcw5YztwXIPlCJjUzRmgvq8sZJZL7iD2Ruy/+
CNU0cZfeqJlb0JUvRE7Z4VMeC4/mFIxyb/RcW71iASKN0ZiBgO7I/hbOk/9mWJrX
U/qxI5DWLT3kSf7bVdkU14gKXH1UbRHsqJXCWe2lkn1LXjjWAdm5u+kMIwPbmpPY
skWpBPN7ffW+UPLKCxncDbpaZkQ6cm81jrxLJ88zHiyfhy6O4lhQym46N5MHfAg1
KflhBiwU6vCu63/SYsNCjt/6M0OAdjLiiq4wkiER7zy+YNEAMyacr2UXdbhmx0ma
zKgSv+u3h+GevFsUxY1aPLc6V76amqwzYNOHyW4bJG/98RP0hBBARsUTZXG3VbW3
+bAv0TAyYhlN3DVyxx4+vkI6qopB2Bdxwg2GZ78qzvt7K5yhf0ZqJ34bvmZ2CDsU
JeyhpBy5HtXeTsapqhT5nyO7AqWZygG1K9jv1v1XxOJeLcljbNtpp07R2UX5W9Sb
jlpMGUBzrJiNLMvGbNR2o6LjUZQXANs9BnVffSF5kQ1sCemc2VG7qM2DQW34KejM
BeKEpcxVUTbBVkQ=
=4TFO
-----END PGP SIGNATURE-----
pgpItgKZHdG1M.pgp
Description: PGP signature
--- End Message ---