On Wed, Oct 15, 2008 at 11:07:05AM +0200, Thijs Kinkhorst wrote:
On Wed, October 15, 2008 07:48, Helmut Grohne wrote:
(...) /usr must not be written to. However after changing the
configuration file /usr/lib/mailman/Mailman/mm_cfg.pyc is updated on
restarting mailman which is a violation of
On Tue, February 10, 2009 20:20, Lionel Elie Mamane wrote:
Too late for lenny now, but it would be worth testing if installing a
dangling symlink /usr/lib/mailman/Mailman/mm_cfg.pyc -
/var/cache/mailman/mm_cfg.pyc
in the package would lead to python create and update the file there (as
severity 502263 important
thanks
Hi Helmut,
On Wed, October 15, 2008 23:57, Helmut Grohne wrote:
I welcome input on this issue from people with more deep knowledge than
myself about these Python cached files, and how we could best address
it in this case. If there's a straightforward
On Wed, October 15, 2008 07:48, Helmut Grohne wrote:
Policy section 9.1.1 says that FHS must be complied and FHS Chapter 4
says that /usr must not be written to. However after changing the
configuration file /usr/lib/mailman/Mailman/mm_cfg.pyc is updated on
restarting mailman which is a
I welcome input on this issue from people with more deep knowledge than
myself about these Python cached files, and how we could best address it
in this case. If there's a straightforward solution I think we can apply
it for lenny.
The simplest solution might actually be to take the approach
Package: mailman
Version: 1:2.1.9-7
Severity: serious
Justification: Policy 9.1.1
Policy section 9.1.1 says that FHS must be complied and FHS Chapter 4
says that /usr must not be written to. However after changing the
configuration file /usr/lib/mailman/Mailman/mm_cfg.pyc is updated on
restarting
6 matches
Mail list logo
