[Cooker] [Bug 4098] [GConf2] no configuration management for default gconf database
http://qa.mandrakesoft.com/show_bug.cgi?id=4098 --- Additional Comments From [EMAIL PROTECTED] 2003-27-06 11:39 --- to 1.: maybe the schemas should only be deinstalled on package removal and not on upgrades. to 2. : I don't know if schemas will have to be reinstalled, I think we should test this. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: The default gconf database (/etc/gconf) is altered by severl package post install scripts. It is easily possible to overwrite the settings of already installed packages (e.g. totem and nautilus-media video thumbnailer do this). It also seems to be impossible to undo some changes once made by the post install scripts leaving dead/unworking stuff in there breaking things (see Bug 4097 for an example). So we end up having race conditions between packages again: the last one overwrites the configuration of the previous ones and never undoes them when uninstalled.
[Cooker] [Bug 4098] [GConf2] no configuration management for default gconf database
http://qa.mandrakesoft.com/show_bug.cgi?id=4098 --- Additional Comments From [EMAIL PROTECTED] 2003-26-06 19:01 --- I think it will be fixed with GConf 2.3.3 which provides a way to uninstall schemas values but it will also require to fix all GNOME packages to uninstall their schemas in %preun -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: The default gconf database (/etc/gconf) is altered by severl package post install scripts. It is easily possible to overwrite the settings of already installed packages (e.g. totem and nautilus-media video thumbnailer do this). It also seems to be impossible to undo some changes once made by the post install scripts leaving dead/unworking stuff in there breaking things (see Bug 4097 for an example). So we end up having race conditions between packages again: the last one overwrites the configuration of the previous ones and never undoes them when uninstalled.
[Cooker] [Bug 4098] [GConf2] no configuration management for default gconf database
http://qa.mandrakesoft.com/show_bug.cgi?id=4098 --- Additional Comments From [EMAIL PROTECTED] 2003-26-06 21:34 --- I suspect the solution goes a little deeper than that, since I can imagine questions like: 1. What's the interaction between pre/post/preun/postun when updating package to new version? In %preun of new package, the new schemas file has already overwritten old schemas file, but the new one may or may not match the old one. 2. When nautilus-media was uninstalled, how can one determine if any other schemas file (in this case, totem) also provides the same set of schemas, and install them accordingly? -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: The default gconf database (/etc/gconf) is altered by severl package post install scripts. It is easily possible to overwrite the settings of already installed packages (e.g. totem and nautilus-media video thumbnailer do this). It also seems to be impossible to undo some changes once made by the post install scripts leaving dead/unworking stuff in there breaking things (see Bug 4097 for an example). So we end up having race conditions between packages again: the last one overwrites the configuration of the previous ones and never undoes them when uninstalled.
