Your message dated Wed, 23 Jan 2019 12:39:29 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-mailman-hackers] Bug#919282: #charset: utf-8
has caused the Debian Bug report #919282,
regarding #charset: utf-8
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.)
--
919282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919282
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mailman3
Version: 3.2.0-4
Severity: normal
Dear Maintainer,
the template directory of mailman is empty. It should contain language specific
template files instead.
Like it is, statements like
[language.en]
charset: utf-8
enabled: yes
[language.de]
description: German
charset: iso-8859-1
enabled: yes
will fail.
Kind regards
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mailman3 depends on:
ii dbconfig-mysql 2.0.11
ii debconf [debconf-2.0] 1.5.69
ii logrotate 3.14.0-4
ii lsb-base 10.2018112800
ii python3 3.7.1-3
ii python3-aiosmtpd 1.2-3
ii python3-alembic 1.0.0-2
ii python3-click 7.0-1
ii python3-dnspython 1.16.0-1
ii python3-falcon 1.0.0-2+b3
ii python3-flufl.bounce 2.3-4
ii python3-flufl.i18n 2.0.1-1
ii python3-flufl.lock 3.2-1
ii python3-lazr.config 2.2-1
ii python3-passlib 1.7.1-1
ii python3-psycopg2 2.7.6.1-3
ii python3-public 0.5-1
ii python3-pymysql 0.9.2-2
ii python3-requests 2.20.0-2
ii python3-sqlalchemy 1.2.15+ds1-1
ii python3-zope.component 4.3.0-1
ii python3-zope.configuration 4.0.3-3
ii python3-zope.event 4.2.0-1
ii python3-zope.interface 4.3.2-1+b2
ii ucf 3.0038+nmu1
Versions of packages mailman3 recommends:
ii exim4-daemon-heavy [mail-transport-agent] 4.92~RC4-2
Versions of packages mailman3 suggests:
ii chromium [www-browser] 72.0.3626.7-4
ii lynx [www-browser] 2.8.9rel.1-2
ii mailman3-doc 3.2.0-4
ii mariadb-server-10.1 [virtual-mysql-server] 1:10.1.37-3
ii postgresql 11+198
ii w3m [www-browser] 0.5.3-37
-- Configuration Files:
/etc/cron.d/mailman3 [Errno 2] No such file or directory: '/etc/cron.d/mailman3'
-- debconf information:
mailman3/pgsql/changeconf: false
* mailman3/database-type: pgsql
mailman3/dbconfig-reinstall: false
mailman3/config_hyperkitty:
mailman3/purge: false
mailman3/install-error: abort
mailman3/passwords-do-not-match:
mailman3/pgsql/authmethod-user: password
mailman3/upgrade-error: abort
mailman3/remote/port:
mailman3/remote/newhost: localhost
mailman3/mysql/admin-user:
mailman3/mysql/method: Unix socket
mailman3/pgsql/no-empty-passwords:
mailman3/dbconfig-upgrade: true
mailman3/pgsql/authmethod-admin: password
mailman3/db/app-user: mailman3@localhost
mailman3/internal/reconfiguring: false
mailman3/internal/skip-preseed: false
mailman3/dbconfig-remove: true
mailman3/pgsql/method: TCP/IP
* mailman3/dbconfig-install: true
mailman3/missing-db-package-error: abort
mailman3/upgrade-backup: true
mailman3/pgsql/manualconf:
mailman3/pgsql/admin-user: postgres
mailman3/db/basepath:
mailman3/init_service_failed:
* mailman3/remote/host: localhost
mailman3/db/dbname: mailman3
mailman3/remove-error: abort
--- End Message ---
--- Begin Message ---
Hi Jörg,
Pierre-Elliott Bécue:
> Le lundi 14 janvier 2019 à 14:21:28+0100, Jörg M. Schulz a écrit :
>> Package: mailman3
>> Version: 3.2.0-4
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> the template directory of mailman is empty. It should contain language
>> specific template files instead.
>> Like it is, statements like
>>
>> [language.en]
>> charset: utf-8
>> enabled: yes
>>
>> [language.de]
>> description: German
>> charset: iso-8859-1
>> enabled: yes
>>
>> will fail.
>
> Looking at upstream source, I see no language specific template files
> provided.
>
> My guess would be that such template files would have to be created by
> members of the community and provided to upstream.
Indeed, that's the current situation. There's no translations for the
mailman3 template files available upstream yet. That's why we don't ship
any either.
That's an issue that should rather be tracked upstream.
https://gitlab.com/mailman/mailman would be the place to do so.
I'm closing the bugreport for now.
Cheers
jonas
signature.asc
Description: OpenPGP digital signature
--- End Message ---
