Your message dated Tue, 29 Aug 2006 22:04:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line config_list screws up list when config contains
new_member_options
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mailman
Version: 2.1.5-1.1
Severity: normal
I had a brief look around but could not find anything useful. The
following is reproducible on various installations of mailman.
If I export a list config with `config_list -o ...` it dumps the
file fine. If I funnel that right back into `config_list -i ...` it
hoses the list. Visiting it over the web interface triggers
a mailman bug, and all (!) command line tools traceback when invoked
on the list:
Traceback (most recent call last):
File "/usr/sbin/sync_members", line 286, in ?
main()
File "/usr/sbin/sync_members", line 258, in main
mlist.ApprovedAddMember(userdesc, welcome, notifyadmin)
File "/var/lib/mailman/Mailman/MailList.py", line 903, in ApprovedAddMember
1 - self.mime_is_default_digest)
File "/var/lib/mailman/Mailman/OldStyleMemberships.py", line 314, in
setMemberOption
self.__mlist.user_options[memberkey] &= ~flag
TypeError: unsupported operand type(s) for &=: 'list' and 'int'
The solution is *not* to feed the
new_member_options = 256
line into `config_list -i ...`.
I am not sure what the right format is, but I would assume that
`config_list -o ...` outputs it correctly. So either the export
writes the wrong thing, or the import expects something else.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (600, 'testing'), (98, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8
--
Please do not CC me when replying to lists; I read them!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, admin, and user
`. `'`
`- Debian - when you have better things to do than fixing a system
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
also sprach Thijs Kinkhorst <[EMAIL PROTECTED]> [2006.08.09.1600 +0200]:
> > I cannot reproduce this bug with Mailman 2.1.6-1 (uploaded to sid
> > seconds ago).
> >
> > Please confirm whether you still suffer from this problem in 2.1.6-1
> > or later.
>
> It would really help if you could try to reproduce this issue, thanks!
I can't because I can't install 2.1.6-1 on any of the productive
machines right now or anytime before the freeze. I cannot reproduce
it in a chroot, so I'll just close it for now and hope that it's in
fact gone.
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
signature.asc
Description: Digital signature (GPG/PGP)
--- End Message ---
