Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 15192] New: modified config files reaped after two recasts

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 15192] New: modified config files reaped after two recasts
  • Date: 19 Apr 2009 18:14:31 -0000

http://bugs.sourcemage.org/show_bug.cgi?id=15192

Summary: modified config files reaped after two recasts
Product: Sorcery
Version: Untargetted future release
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: subroutines
AssignedTo: sm-sorcery-bugs AT lists.ibiblio.org
ReportedBy: glyn AT ox.compsoc.net


libdispel's reap_config_files checks whether a spell's configuration files
have
been modified by searching for their md5 in that spell's "md5sums" file.
Provided that sorcery's "PRESERVE" variable is "on" (the default), recasting
(including upgrading) a spell after its configuration file has been modified
will cause the following message during installation:

Preparing to install hdparm
/etc/sysconfig/hdparm
was previously modified by SA?
Therefore, it was not reaped.

The md5 of the modified config file will be stored in the new spell's md5sums
file. If the spell is then recast/upgraded again, without subsequent changes
to the config file, then reap_config_files sees that the md5 matches that in
the md5sums file, decides that the config file hasn't been modified, and
overwrites it with the "new" version from the updated spell, losing the
modifications made two casts earlier.

As well as the hdparm config example above, this has caused similar lost
modifications in the postfix spell's /etc/postfix/main.cf - I suspect it be
the
cause of the most recent comment in bug 13751.

--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.




Archive powered by MHonArc 2.6.24.

Top of Page