--- Begin Message ---
Source: curry-frontend
Version: 1.0.4-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 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 (>= 10), haskell-devscripts (>= 0.8), cdbs,
> ghc, ghc-prof, libghc-containers-dev, libghc-containers-prof,
> libghc-curry-base-dev (>= 1.1.1~), libghc-curry-base-dev (<< 1.1.2),
> libghc-curry-base-prof (>= 1.1.1~), libghc-curry-base-prof (<< 1.1.2),
> libghc-directory-dev, libghc-directory-prof, libghc-filepath-dev,
> libghc-filepath-prof, libghc-file-embed-dev, libghc-file-embed-prof,
> libghc-mtl-dev, libghc-mtl-prof, libghc-network-uri-dev (>= 2.6),
> libghc-network-uri-prof (>= 2.6), libghc-process-dev, libghc-process-prof,
> libghc-set-extra-dev, libghc-set-extra-prof, libghc-syb-dev, libghc-syb-prof,
> libghc-transformers-dev, libghc-transformers-prof, build-essential, fakeroot,
> ghc-doc, libghc-base-doc, libghc-containers-doc, libghc-curry-base-doc (>=
> 1.1.1~), libghc-curry-base-doc (<< 1.1.2), libghc-directory-doc,
> libghc-filepath-doc, libghc-file-embed-doc, libghc-mtl-doc,
> libghc-network-uri-doc, libghc-process-doc, libghc-set-extra-doc,
> libghc-syb-doc, libghc-transformers-doc
> Filtered Build-Depends: debhelper (>= 10), haskell-devscripts (>= 0.8), cdbs,
> ghc, ghc-prof, libghc-containers-dev, libghc-containers-prof,
> libghc-curry-base-dev (>= 1.1.1~), libghc-curry-base-dev (<< 1.1.2),
> libghc-curry-base-prof (>= 1.1.1~), libghc-curry-base-prof (<< 1.1.2),
> libghc-directory-dev, libghc-directory-prof, libghc-filepath-dev,
> libghc-filepath-prof, libghc-file-embed-dev, libghc-file-embed-prof,
> libghc-mtl-dev, libghc-mtl-prof, libghc-network-uri-dev (>= 2.6),
> libghc-network-uri-prof (>= 2.6), libghc-process-dev, libghc-process-prof,
> libghc-set-extra-dev, libghc-set-extra-prof, libghc-syb-dev, libghc-syb-prof,
> libghc-transformers-dev, libghc-transformers-prof, build-essential, fakeroot,
> ghc-doc, libghc-base-doc, libghc-containers-doc, libghc-curry-base-doc (>=
> 1.1.1~), libghc-curry-base-doc (<< 1.1.2), libghc-directory-doc,
> libghc-filepath-doc, libghc-file-embed-doc, libghc-mtl-doc,
> libghc-network-uri-doc, libghc-process-doc, libghc-set-extra-doc,
> libghc-syb-doc, libghc-transformers-doc
> 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 [610 B]
> Get:5 copy:/<<RESOLVERDIR>>/apt_archive ./ Packages [693 B]
> Fetched 2266 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...
> 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:
> libghc-curry-base-doc : Depends: haddock-interface-33 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/2020/07/09/curry-frontend_1.0.4-4_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.
--- End Message ---
