Bug#1017219: arbtt: FTBFS: unsatisfiable build-dependency: libghc-aeson-dev (< 1.5) but 2.0.3.0-1+b1 is to be installed

[Lucas Nussbaum]

Source: arbtt
Version: 0.11.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-20220813 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: cdbs, haskell-devscripts (>= 0.16.14), debhelper (>= 10), ghc, libghc-mtl-dev, libghc-binary-dev, libghc-time-dev, libghc-aeson-dev (>= 0.10), libghc-aeson-dev (<< 1.5), libghc-x11-dev (>= 1.9), libghc-parsec3-dev, libghc-pcre-light-dev, libghc-utf8-string-dev, libghc-deepseq-dev, libghc-strict-dev, libghc-terminal-progress-bar-dev (>= 0.2), libghc-terminal-progress-bar-dev (<< 0.5), libghc-bytestring-progress-dev, libghc-conduit-dev (>= 1.2), libghc-conduit-dev (<< 1.4), libghc-exceptions-dev (>= 0.8), libghc-resourcet-dev (>= 1.2), libghc-unliftio-core-dev, libxss-dev, docbook-xsl, fop, xsltproc, build-essential, fakeroot
> Filtered Build-Depends: cdbs, haskell-devscripts (>= 0.16.14), debhelper (>= 10), ghc, libghc-mtl-dev, libghc-binary-dev, libghc-time-dev, libghc-aeson-dev (>= 0.10), libghc-aeson-dev (<< 1.5), libghc-x11-dev (>= 1.9), libghc-parsec3-dev, libghc-pcre-light-dev, libghc-utf8-string-dev, libghc-deepseq-dev, libghc-strict-dev, libghc-terminal-progress-bar-dev (>= 0.2), libghc-terminal-progress-bar-dev (<< 0.5), libghc-bytestring-progress-dev, libghc-conduit-dev (>= 1.2), libghc-conduit-dev (<< 1.4), libghc-exceptions-dev (>= 0.8), libghc-resourcet-dev (>= 1.2), libghc-unliftio-core-dev, libxss-dev, docbook-xsl, fop, xsltproc, 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 [576 B]
> Get:5 copy:/<<RESOLVERDIR>>/apt_archive ./ Packages [664 B]
> Fetched 2203 B in 0s (129 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: libghc-aeson-dev (< 1.5) but 2.0.3.0-1+b1 is to be installed
> 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/08/13/arbtt_0.11.1-1_unstable.log

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