Source: newsboat
Version: 2.18-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

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-compat (= 12), libncursesw5-dev, libxml2-dev, 
> libstfl-dev, libsqlite3-dev, perl, pkg-config, libcurl4-gnutls-dev, 
> libjson-c-dev, asciidoc, libxml2-utils, xsltproc, docbook-xml, docbook-xsl, 
> cargo, librust-chrono-0.4-dev, librust-time-0.1-dev, librust-rand-0.7-dev, 
> librust-once-cell-1+parking-lot-dev, librust-regex-1-dev, librust-url-2-dev, 
> librust-dirs-2-dev, librust-xdg-2-dev, librust-backtrace-0.3-dev, 
> librust-backtrace-sys-0.1-dev, librust-unicode-width-0.1-dev, 
> librust-nom-4-dev, librust-unicode-segmentation-1-dev, 
> librust-curl-sys-0.4+ssl-dev, librust-libc-0.2-dev, 
> librust-gettext-rs-0.4-dev, librust-natord-1-dev, librust-clap-2-dev, 
> librust-gettext-sys-0.19-dev, librust-tempfile-3-dev, 
> librust-proptest-0.9+bit-set-dev, librust-proptest-0.9+rusty-fork-dev, 
> librust-proptest-0.9+timeout-dev, librust-percent-encoding-2-dev, 
> librust-section-testing-0.0.4-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), libncursesw5-dev, 
> libxml2-dev, libstfl-dev, libsqlite3-dev, perl, pkg-config, 
> libcurl4-gnutls-dev, libjson-c-dev, asciidoc, libxml2-utils, xsltproc, 
> docbook-xml, docbook-xsl, cargo, librust-chrono-0.4-dev, 
> librust-time-0.1-dev, librust-rand-0.7-dev, 
> librust-once-cell-1+parking-lot-dev, librust-regex-1-dev, librust-url-2-dev, 
> librust-dirs-2-dev, librust-xdg-2-dev, librust-backtrace-0.3-dev, 
> librust-backtrace-sys-0.1-dev, librust-unicode-width-0.1-dev, 
> librust-nom-4-dev, librust-unicode-segmentation-1-dev, 
> librust-curl-sys-0.4+ssl-dev, librust-libc-0.2-dev, 
> librust-gettext-rs-0.4-dev, librust-natord-1-dev, librust-clap-2-dev, 
> librust-gettext-sys-0.19-dev, librust-tempfile-3-dev, 
> librust-proptest-0.9+bit-set-dev, librust-proptest-0.9+rusty-fork-dev, 
> librust-proptest-0.9+timeout-dev, librust-percent-encoding-2-dev, 
> librust-section-testing-0.0.4-dev, 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 [672 B]
> Get:5 copy:/<<RESOLVERDIR>>/apt_archive ./ Packages [759 B]
> Fetched 2394 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> ----------------------------------------------------
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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-regex-1-dev
>                                    Depends: librust-gettext-rs-0.4-dev
> 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/2020/03/21/newsboat_2.18-2_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Reply via email to