Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

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


acedit AT armory.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|1.13.x                      |1.14.x




------- Additional Comments From acedit AT armory.com  2006-11-12 01:25 -------
I think this is only possible by casting net-tools at least once with devel
sorcery using installwatch 6 (logging only). This was, of course, the one
configuration i didn't test while trying to reproduce this.

The problem ultimately has to do with erroneously tracking the facilities 
file's
md5sum.

In libinitd init_post_install modifies facilities.

In stable sorcery that code is run after installwatch is disabled (thanks
ruskie). In devel sorcery, in order to fix bug 10031 a new bash instance is
started through delve. But that means installwatch isnt devoked in the middle 
of
POST_INSTALL anymore. So the code in libinitd runs with impunity.

This bug is minor variation of a much larger issue with sysconfig files a year
or two ago. In that bug any sysconfig file could easily get into this state.
There are two sysconfig related functions, one that does facilities and one 
that
does everything else. I fixed the one for "everything else" already but
neglected the facilities case.

The fix should be to just check/mark for modification like in the other
function. Alternatively instead of in place modification, copy the file
somewhere and modify it there, then run install_config_files.

The problem shouldn't happen with castfs because it forces all /etc files
through install_config_files.

I think remnant keymap deletions are left over from the older sorcery bug, or
some other unknown bug with tracking.

I will work on reproducing it to prove my theory and then I can test my fix 
(its
a one-liner).

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