[Pkg-rust-maintainers] Bug#1026618: rust-trust-dns-client: FTBFS: build-dependency not installable: librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~)

[Lucas Nussbaum]

Source: rust-trust-dns-client
Version: 0.21.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +------------------------------------------------------------------------------+
> | Install package build dependencies                                           |
> +------------------------------------------------------------------------------+
> 
> 
> Setup apt archive
> -----------------
> 
> Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, libstd-rust-dev, librust-cfg-if-1+default-dev, librust-data-encoding-2+default-dev (>= 2.2.0-~~), librust-futures-channel-0.3+std-dev (>= 0.3.5-~~), librust-futures-util-0.3+std-dev (>= 0.3.5-~~), librust-lazy-static-1+default-dev (>= 1.2.0-~~), librust-log-0.4+default-dev, librust-radix-trie-0.2+default-dev, librust-rand-0.8+default-dev, librust-thiserror-1+default-dev (>= 1.0.20-~~), librust-time-0.3+default-dev, librust-tokio-1+default-dev, librust-tokio-1+rt-dev, librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~), build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, libstd-rust-dev, librust-cfg-if-1+default-dev, librust-data-encoding-2+default-dev (>= 2.2.0-~~), librust-futures-channel-0.3+std-dev (>= 0.3.5-~~), librust-futures-util-0.3+std-dev (>= 0.3.5-~~), librust-lazy-static-1+default-dev (>= 1.2.0-~~), librust-log-0.4+default-dev, librust-radix-trie-0.2+default-dev, librust-rand-0.8+default-dev, librust-thiserror-1+default-dev (>= 1.0.20-~~), librust-time-0.3+default-dev, librust-tokio-1+default-dev, librust-tokio-1+rt-dev, librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~), build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in '/<<RESOLVERDIR>>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<<RESOLVERDIR>>/apt_archive ./ InRelease
> Get:2 copy:/<<RESOLVERDIR>>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<<RESOLVERDIR>>/apt_archive ./ Release.gpg
> Get:4 copy:/<<RESOLVERDIR>>/apt_archive ./ Sources [560 B]
> Get:5 copy:/<<RESOLVERDIR>>/apt_archive ./ Packages [636 B]
> Fetched 2159 B in 0s (174 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> ----------------------------------------------------
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~) but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/rust-trust-dns-client_0.21.2-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lucas@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.