Le 12/02/2013 12:19, Colin Guthrie a écrit :
'Twas brillig, and EatDirt at 12/02/13 10:06 did gyre and gimble:
Within today update of cauldron:
7/232: Default-kde4-config ###########################
warning: /var/lib/mageia/kde4-profiles/Default/share/config/kdm/kdmrc
created as
/var/lib/mageia/kde4-profiles/Default/share/config/kdm/kdmrc.rpmnew
Now if I go to that directory, I see this is not the case:
ls -trl
total 80
-rw-r--r-- 1 root root 347 May 21 2011 backgroundrc
-rw-r--r-- 1 root root 21677 Jun 6 2012 kdmrc.rpmsave
drwxr-xr-x 3 root root 4096 Feb 6 22:29 themes/
-rw-r--r-- 1 root root 21689 Feb 12 11:02 kdmrc.ccpbackup
-rw-r--r-- 1 root root 21630 Feb 12 11:02 kdmrc
It has been created as kdmrc, with a rpmsave. It seems we have a problem
in between the message and what is actually done?
No, I think the file itself is indeed created as a .rpmnew at the time
RPM prints that message.
In the spec:
http://svnweb.mageia.org/packages/cauldron/mageia-kde4-config/current/SPECS/mageia-kde4-config.spec?revision=397256&view=markup#l117
we use the "ccp" program to merge the .rpmnew config to the current
config (i.e. merging in your customisations to the new file, such that
new comments and directives are present).
This has the effect of subsequently deleting the .rpmnew file (although
creating the kdmrc.ccpbackup file).
Thus it's doing everything correctly, even if the use of ccp can result
in the rpmnew warnings being misleading.
Yes, it's a side effect of using ccp.
I need to make some tests, but I will probably try to remove the '-d' to
keep the .rpmnew. This would allow users to see, and possibly merge in
their kdmrc, the changes in default values.
regards,
Luc
--
Luc Menut
