Your message dated Wed, 19 Oct 2022 21:09:00 +0000
with message-id <e1olgja-00h50b...@fasolo.debian.org>
and subject line Bug#1020122: fixed in netavark 1.0.3-4
has caused the Debian Bug report #1020122,
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.)


-- 
1020122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netavark
Version: 1.0.3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


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: ['parallel=8'] [] ['-j8']
> 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: ['parallel=8'] [] ['-j8']
> 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', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu'],) {}
> error: failed to select a version for the requirement `nix = "^0.24"`
> candidate versions found which didn't match: 0.25.0
> location searched: directory source `/<<PKGBUILDDIR>>/debian/cargo_registry` 
> (which is replacing registry `crates-io`)
> required by package `netavark v1.0.3 (/<<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/2022/09/17/netavark_1.0.3-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&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 marking 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.0.3-4
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 1020...@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: Wed, 19 Oct 2022 16:22:07 -0400
Source: netavark
Architecture: source
Version: 1.0.3-4
Distribution: unstable
Urgency: medium
Maintainer: Reinhard Tartler <siret...@tauware.de>
Changed-By: Reinhard Tartler <siret...@tauware.de>
Closes: 1020122
Changes:
 netavark (1.0.3-4) unstable; urgency=medium
 .
   * Fix FTBFS, bump nix version, thanks to Lucas Nussbaum (Closes: #1020122).
Checksums-Sha1:
 a1fb3d7e190fbf9b297dff60c43bb4b08ed1fb35 2662 netavark_1.0.3-4.dsc
 dc90c57f90f538921fe0512c073877ad1a6115ab 4324 netavark_1.0.3-4.debian.tar.xz
Checksums-Sha256:
 ecaae2d43b1e001c46592402bfd41c7f75a0fa2e5bf577e118e15f2c3231a553 2662 
netavark_1.0.3-4.dsc
 0963979b09b2c3f12e670bc6e06025af5143405e22d493375debb339790a2b8e 4324 
netavark_1.0.3-4.debian.tar.xz
Files:
 2d76a49e7bd6df980b089a009f879762 2662 net optional netavark_1.0.3-4.dsc
 c459277914572ef4abaa31d4643dce95 4324 net optional 
netavark_1.0.3-4.debian.tar.xz

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

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmNQXKcUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJss+6RAAz6dJTZbp4EkI3cEK/ASy0PXT/fwJ
C6HJljgIZAlumBLqcdVAnkq3Gx6Qw6xc7I1slqUEakSHDHNtbJe/zonr36+0YZUe
l/YiGPlb9mUC5syOoUuxw5HEjKkHnjHzToGApKGthb2TtoKiVFzgTy7Ctw0KTjXy
+ClPsi0DyKyVxY+yOIsr5SpAGB+DqXhUiuIl6mgi1vrpb4bmv4rCMAp0jcKp2mhZ
l6bd2NNCwxn5n3WoyPI1USqHAjlsWCKja5MdZcGXPltiQwFmpoHGkHIzy9x1SSCC
ps0POvYw7spbEjyxP8v8uNHhDXpx/ZW0fDF3q4TWA2IBlH7tP7gtPlWlJLjMduFw
f2HbHro+sRoU8l9XI2URwhykRt3vuvr2m1r9cumqq7yk+VpgTFhLdlv5bLAyLJ08
p11aOo71FsPINcy//Ptm69YWP/e5AyTGP0+POny5jTdEo4hebLr2E2ZhOqDkyrmX
KJs4S2GCs3StkE67u9rPoGKohysmLd1PA9cH/BOISbiePjciNxD1QAEfHxxPjh8B
Gl0vwXWc+Mp+XQFvhjjZh+AeyWXXonmTKjI3VQb3F4TH8AeKCSxB05qoCleL/Nkl
C48JpO80rb5IFEjBk188gu7WBdr0Ql0wYVA5b37cuuEYkM2Z8OV6TzYt7ig8E+Xg
M9T1N3clgCOwD5I=
=plsM
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to