Your message dated Tue, 09 Jan 2024 00:29:30 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-mailman-hackers] Bug#1003196:
python3-mailman-hyperkitty: postinst should run django-admin migrate
has caused the Debian Bug report #1003196,
regarding python3-mailman-hyperkitty: postinst should run django-admin migrate
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1003196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003196
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-mailman-hyperkitty
Version: 1.1.0-10
Severity: normal
Dear Maintainer,
After a routine apt-upgrade, archives showed 'server error' instead of an
archive.
THe issue was that the database schema needed update.
I believe the postinst script should run:
sudo -u www-data django-admin migrate --pythonpath /usr/share/mailman3-web
--settings settings
or ask the user to.
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-cloud-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-mailman-hyperkitty depends on:
ii debconf [debconf-2.0] 1.5.79
ii mailman3 3.3.3-1
ii python3 3.9.8-1
ii python3-pkg-resources 59.6.0-1
ii python3-requests 2.25.1+dfsg-2
ii python3-zope.interface 5.4.0-1+b1
ii ucf 3.0043
Versions of packages python3-mailman-hyperkitty recommends:
ii mailman3-web 0+20200530-2
ii python3-django-hyperkitty 1.3.5-1
python3-mailman-hyperkitty suggests no packages.
-- debconf information:
python3-mailman-hyperkitty/no_archiverkey:
--- End Message ---
--- Begin Message ---
And it's the wrong package for this bug report.
Pierre-Elliott Bécue <[email protected]> wrote on 06/01/2022 at 13:24:33+0100:
> [[PGP Signed Part:Signature made by expired key 29BFA0D079290ACA
> Pierre-Elliott Bécue <[email protected]>]]
>
> Peter Chubb <[email protected]> wrote on 06/01/2022 at 02:03:27+0100:
>
>> Package: python3-mailman-hyperkitty
>> Version: 1.1.0-10
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> After a routine apt-upgrade, archives showed 'server error' instead of an
>> archive.
>>
>> THe issue was that the database schema needed update.
>>
>> I believe the postinst script should run:
>> sudo -u www-data django-admin migrate --pythonpath /usr/share/mailman3-web
>> --settings settings
>> or ask the user to.
>
> Hi,
>
> It's done in mailman3-web's postinst, but as it not updated anymore
> upstream, the update is not triggered.
>
> We'll probably include django maintenance in django-mailman3 as it tends
> to be updated along with hyperkitty and postorius that both depend on
> it.
>
> Regards,
signature.asc
Description: PGP signature
--- End Message ---
