[Pkg-mailman-hackers] Bug#1052805: hyperkitty: FTBFS: unsatisfiable build-dependencies: python3-django (< 3:4.2), python3-django-mailman3 (>= 1.3.8)

[Lucas Nussbaum]

Source: hyperkitty
Version: 1.3.7-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

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 (= 13), dh-python, python3-all, python3-bs4, python3-django (>= 2:3.2), python3-django (<< 3:4.2), python3-django-compressor, python3-django-extensions, python3-django-gravatar2, python3-django-haystack, python3-django-mailman3 (>= 1.3.8), python3-django-q, python3-djangorestframework, python3-elasticsearch, python3-flufl.lock, python3-isort, python3-lxml, python3-mailmanclient, python3-mistune (>= 2.0.0), python3-mock, python3-networkx, python3-robot-detection, python3-setuptools, python3-tz, python3-whoosh, python3-sphinx, sassc, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-python, python3-all, python3-bs4, python3-django (>= 2:3.2), python3-django (<< 3:4.2), python3-django-compressor, python3-django-extensions, python3-django-gravatar2, python3-django-haystack, python3-django-mailman3 (>= 1.3.8), python3-django-q, python3-djangorestframework, python3-elasticsearch, python3-flufl.lock, python3-isort, python3-lxml, python3-mailmanclient, python3-mistune (>= 2.0.0), python3-mock, python3-networkx, python3-robot-detection, python3-setuptools, python3-tz, python3-whoosh, python3-sphinx, sassc, 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 [615 B]
> Ign:3 copy:/<<RESOLVERDIR>>/apt_archive ./ Release.gpg
> Get:4 copy:/<<RESOLVERDIR>>/apt_archive ./ Sources [1147 B]
> Get:5 copy:/<<RESOLVERDIR>>/apt_archive ./ Packages [1180 B]
> Fetched 2942 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:
>  sbuild-build-depends-main-dummy : Depends: python3-django (< 3:4.2) but 3:4.2.5-2 is to be installed
>                                    Depends: python3-django-mailman3 (>= 1.3.8) but it is not going 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/2023/09/25/hyperkitty_1.3.7-1_unstable.log

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