127439 – Upgrading mailman does not save old python config files

Bug 127439 - Upgrading mailman does not save old python config files

Summary: Upgrading mailman does not save old python config files

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	x86 Linux

Importance:	Normal normal (vote)
Assignee:	Net-Mail Packages

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-03-24 08:52 UTC by ChazeFroy
Modified:	2006-04-13 05:40 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description ChazeFroy 2006-03-24 08:52:00 UTC

I upgraded mailman from 2.1.5 to 2.1.7. In doing so, portage overwrote my custom config file at "/usr/local/mailman/Mailman/Defaults.py".

It would be nice to have the directory "/usr/local/mailman/Mailman" treated the same way as "/etc" when dealing with updated config files (ie, naming new config files "._cfg*" instead of automatically overwriting them).

I do not know the inner workings of "etc-update", but that script may also need updating if you decide to protect "/usr/local/mailman/Mailman".

Comment 1 Tero Pelander 2006-04-06 01:02:01 UTC

> I upgraded mailman from 2.1.5 to 2.1.7. In doing so, portage overwrote my
> custom config file at "/usr/local/mailman/Mailman/Defaults.py".

The file in question starts with following warning.

# NEVER make site configuration changes to this file.  ALWAYS make them in
# mm_cfg.py instead, in the designated area.  See the comments in that file
# for details.

Comment 2 Martin Holzer (RETIRED) gentoo-dev

2006-04-13 05:40:30 UTC

see comment #1