hyperkitty: FTBFS on noble
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hyperkitty (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
$ pull-lp-source hyperkitty
$ sbuild --no-clean --no-run-lintian -d noble .
Logs snippet:
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules override_
make[1]: Entering directory '/<<PKGBUILDDIR>>'
py3versions: no X-Python3-Version in control file, using supported versions
set -e; \
for python3 in python3.12 python3.11; do \
$python3 /usr/bin/
done
Traceback (most recent call last):
File "/usr/bin/
sys.
File "/usr/lib/
utility.
File "/usr/lib/
django.setup()
File "/usr/lib/
apps.
File "/usr/lib/
app_
File "/usr/lib/
raise ImproperlyConfi
django.
make[1]: *** [debian/rules:15: override_
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:8: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
This version is incompatible with python-mistune 3.0.2-1.
A fix exist upstream to make it compatible with mistune 3.X, see [0] but this is on top of more than a year of changes. So there is a high chance that using this commit as a patch will not work properly I think.
But only mailman3-web depends on python3- django- hyperkitty, and mailman-suite was not updated since 2020 (from upstream), but upstream is still maintained.
Since the only purpose (AFAIU) of hyperkitty is to be used by mailman-suite, maybe we should upload an up-to-date version of both pkgs from upstream, so we will be sure they work properly together.
[0] https:/ /gitlab. com/mailman/ hyperkitty/ -/commit/ 68a0e57a87e9090 5a96b8f7194cf23 d53a0915c2