[Pkg-mailman-hackers] Bug#983681: Bug#983681: Hyperkitty API token is not set in Hyperkitty configuration

[Jonas Meurer]

Hey Thomas,

Am 28.02.21 um 13:09 schrieb Thomas Koch:
> The README.Debian.gz claims:
> 
>   * A secure API token for the Hyperkitty archiver is generated and
>     set both in the Django and in the Hyperkitty configuration.
> 
> However I only see this token being set in MAILMAN_ARCHIVER_KEY in /etc/mailman3/mailman-web.py.
> The api_key setting in section general of /etc/mailman3/mailman-hyperkitty.cfg is still "SecretArchiverAPIKey".
> 
> This has probably not yet been reported since the hyperkitty configuration still needs manual intervention anyways, e.g. enabling the archiver in mailman.cfg.

You might have to run `dpkg-reconfigure python3-mailman-hyperkitty` in 
order to get the correct API token into `mailman-hyperkitty.cfg`.

This is due to a chicken-and-egg problem: if mailman3-web and 
python3-mailman-hyperkitty are installed at the same time and the latter 
is configured earlier in the install process, then the generated token 
is not known yet.

I documented this now in README.Debian to make it more clear.

Kind regards
  jonas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-mailman-hackers/attachments/20210308/94991b12/attachment-0001.sig>