mailman-suite 0+20170523-12 source package in Ubuntu
Changelog
mailman-suite (0+20170523-12) unstable; urgency=medium [ Jonas Meurer ] * Rename binary package 'mailman3-suite' to 'mailman3-web' to avoid further confusion, drop binary package 'mailman3-suite'. A bit more background: - The naming of our mailman3 packages caused some confusion. So we decided on the following: 1. binary package 'mailman3-suite' will become 'mailman3-web' to make the purpose more obvious. 2. binary and source package 'mailman3-core' will become 'mailman3'. This is closer to the upstream name. 3. binary metapackage 'mailman3' will become 'mailman3-full' and moves to the source package 'mailman3-core'/'mailman3'. This upload of source package 'mailman-suite' takes care of part 1. * d/NEWS: - Document the renaming of the binary package name. * d/mailman3-web.*, d/patches/*, d/contrib/uwsgi.ini, d/rules: - Move logfiles to new subdirectory /var/log/mailman3/web * d/control: - Drop binary package 'mailman3', will be provided by another source package in future. - Add 'Conflicts: mailman3-suite' to mailman3-web, to prevent parallel installation of old and new binary package. * d/mailman3-web.postinst: - Add '-f' to ucfr for hyperkitty.conf, as we might hijack the file from old package mailman3-suite. - Explicitly run python2.7 version of django-admin * d/contrib/hyperkitty.cfg.sample, d/mailman3-web.{install,postinst,postrm}: - Remove 'hyperkitty.cfg', it belongs to python3-mailman-hyperkitty * d/rules: - Run debhelper with '--with systemd' - Set owner of /var/lib/mailman3/web/static/CACHE to www-data:www-data. (Closes: #892427) * d/mailman3-web.config: - Fix sed command in get_config_option() - Wrap db_input into 'db_beginblock' and 'db_endblock' * d/templates: - Enhance description for mailman3-web/superuser-password [ Pierre-Elliott Bécue ] * d/mailman3-web.install: - Move uwsgi.ini to /etc/mailman3 * d/contrib/nginx.conf: - Add nginx.conf file * d/mailman3-web.cron.d: - Fix cron jobs to call explicitly python2.7 version of django-admin.py * d/template: - Add a new debconf readme entry to display when a user choses nginx. * d/po/fr.po: updated translation * d/mailman3-web.postinxt: - Displays the readme if nginx is chosen -- Jonas Meurer <email address hidden> Wed, 14 Mar 2018 16:57:34 +0100
Upload details
- Uploaded by:
- Mailman for Debian
- Uploaded to:
- Sid
- Original maintainer:
- Mailman for Debian
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
mailman-suite_0+20170523-12.dsc | 2.0 KiB | 3866dd57e3b99908d957c316630e4c2e634e01f726ac63c42e07bcb86995cba4 |
mailman-suite_0+20170523.orig.tar.gz | 18.4 KiB | bef9213b960c6db3af7f2b5129804575f9022a126214e3d2d173ffd5159aa1e5 |
mailman-suite_0+20170523-12.debian.tar.xz | 17.8 KiB | edb9b39e1c002832791597473c84bcdc232668a1930154a7deee70db355914cf |
Available diffs
- diff from 0+20170523-10 to 0+20170523-12 (16.6 KiB)
No changes file available.
Binary packages built by this source
- mailman3-web: Django project integrating Mailman3 Postorius and HyperKitty
This django web application provides the Mailman3 Postorius web interface
and the HyperKitty mailinglist archiver integrated into one project.
.
The package automates most of the necessary configuration for the Django
project (database setup, webserver configuration, secret and API key
generation, Django project configuration) to get a ready-to-use Mailman3
web suite.
.
The Mailman3 Django project runs as uWSGI daemon and optionally a webserver
is configured as reverse proxy. In this case, the service can be accessed
at '/mailman3'.
.
Default database backend is SQLite3 in order to not break automated
installations. For productive setups, PostgreSQL or MySQL are much better
options though. See README.Debian for further information.