Your message dated Thu, 29 Mar 2018 18:00:28 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-mailman-hackers] Bug#891703: Bug#891703: 
mailman3-suite: DB user isn't read from setting_local (mailman3-suite.py in 
/etc)
has caused the Debian Bug report #891703,
regarding mailman3-suite: DB user isn't read from setting_local 
(mailman3-suite.py in /etc)
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.)


-- 
891703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891703
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mailman3-suite
Version: 0+20170523-10
Severity: important

Hi,

The default user is being read from the packaged settings.py instead of the 
settings_local.py file symlinked to /etc/mailman3 .
I see error logs saying "mailmansuite" has no access, which is true since 
that's not what I configured. I had to hand edit
the /usr/share/mailman3-suite/settings.py by hand to have to work like I wanted 
(which isn't recommended, nor what I would like to do).

Is there some solution to this?

Thank you
Eric

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.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)

Versions of packages mailman3-suite depends on:
ii  dbconfig-mysql            2.0.9
ii  dbconfig-pgsql            2.0.9
ii  dbconfig-sqlite3          2.0.9
ii  debconf [debconf-2.0]     1.5.65
ii  lsb-base                  9.20170808
ii  node-less                 1.6.3~dfsg-2
ii  python                    2.7.14-4
ii  python-django-hyperkitty  1.1.4-3
ii  python-django-postorius   1.1.2-1
ii  python-psycopg2           2.7.4-1
ii  python-whoosh             2.7.4+git6-g9134ad92-1
ii  python3-pymysql           0.8.0-1
ii  ruby-sass                 3.5.3-1
ii  ucf                       3.0038
ii  uwsgi                     2.0.15-10.2
ii  uwsgi-plugin-python       2.0.15-10.2

Versions of packages mailman3-suite recommends:
ii  nginx-extras [nginx]  1.13.9-1

Versions of packages mailman3-suite suggests:
ii  mariadb-server-10.1 [virtual-mysql-server]  1:10.1.29-6
ii  postgresql                                  10+190

-- Configuration Files:
/etc/cron.d/mailman3-suite changed:
* *     * * *   list    command -v django-admin >/dev/null && django-admin 
runjobs minutely --pythonpath /usr/share/mailman3-suite --settings settings
2,17,32,47 * * * * root command -v django-admin >/dev/null && django-admin 
runjobs quarter_hourly --pythonpath /usr/share/mailman3-suite --settings 
settings
@hourly         list    command -v django-admin >/dev/null && django-admin 
runjobs hourly   --pythonpath /usr/share/mailman3-suite --settings settings
@daily          list    command -v django-admin >/dev/null && django-admin 
runjobs daily    --pythonpath /usr/share/mailman3-suite --settings settings
@weekly         list    command -v django-admin >/dev/null && django-admin 
runjobs weekly   --pythonpath /usr/share/mailman3-suite --settings settings
@monthly        list    command -v django-admin >/dev/null && django-admin 
runjobs monthly  --pythonpath /usr/share/mailman3-suite --settings settings
@yearly         list    command -v django-admin >/dev/null && django-admin 
runjobs yearly   --pythonpath /usr/share/mailman3-suite --settings settings

/etc/logrotate.d/mailman3-suite changed:
/var/log/mailman3/mailman-suite.log {
        copytruncate
        daily
        rotate 5
        compress
        delaycompress
        missingok
        notifempty
    su www-data list
        create 660 www-data list
}
/var/log/mailman3/mailman-suite-uwsgi.log {
        copytruncate
        weekly
        rotate 3
        compress
        delaycompress
        missingok
        notifempty
    su www-data list
        create 660 www-data list
}


-- debconf information excluded

--- End Message ---
--- Begin Message ---
Hi Eric,

I'm closing this bugreport as it's missing further information from you.

I'm pretty sure that the bug you discovered is solved in the current
mailman3/mailman3-web packages in Debian unstable/testing/stretch-backports.

Cheers,
 jonas

Am 15.03.2018 um 22:47 schrieb Jonas Meurer:
> Hi Eric,
> 
> Am 04.03.2018 um 04:59 schrieb Eric Côté:
>> Bug is still present.
> 
> I did quite some testing of the mailman3 packages in the last days,
> using all possible database backends. So far, I failed to reproduce the
> bug you discovered.
> 
> We renamed the 'mailman3-suite' package to 'mailman3-web' recently, to
> avoid further confusion about the purpose of the package. Similarly, we
> renamed 'mailman3-core' to 'mailman3'. You should find all these
> packages in Debian Unstable by now.
> 
> Would you mind to purge all your mailman3 packages, do a fresh
> installation and see, whether you're still able to reproduce the bug
> with the latest packages from Debian Unstable?
> 
>> Like I mentioned in my original report, "mailman3suite" is the user in
>> /usr/share/mailman3-suite/settings.py . I've had to hand edit it so my 
>> install
>> reads my DB settings in /etc/mailman3/mailman3-suite.py . 
> 
> After testing different settings, I'm pretty confident that indeed the
> database settings from '/etc/mailman3/mailman3-suite.py' (or now
> '/etc/mailman/mailman-web.py') are used in a clean
> mailman3-suite/mailman3-web installation.
> 
> Please send the output of the following commands:
> 
> $ ls -al /etc/mailman3/mailman-suite.py
> $ ls -al /usr/share/mailman3-suite/settings*
> 
>> Seems this might be in either python-django-hyperkitty (which is I think is 
>> the
>> case), since the log is referencing django and hyperkitty, or in
>> python3-mailman-hyperkitty (which doesn't seem to be picking up my list 
>> content
>> anyway; I should be seeing archives, but I don't, in the web UI).
>>
>> I dunno how to refile a bug to another source package or tag another (if 
>> that's doable).
> 
> You can reassign existing bugreports by using 'Control:' pseudo-headers
> at the beginning of mails or by sending control commands to the
> bugtracker[1].
> 
> [1] https://www.debian.org/Bugs/server-control
> 
> Cheers,
>  jonas
> 
> 
> 
> _______________________________________________
> Pkg-mailman-hackers mailing list
> [email protected]
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mailman-hackers
> 


Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to