From: <jlt...@ad...> - 2004-01-06 20:27:31
|
At 19:56 06/01/2004, you wrote: >Jos=E9 Luis Tall=F3n wrote: >>At 23:09 31/12/2003, you wrote: >>I hope you will report *each and every* bug you discover so that i can=20 >>fix it promptly :) > >>>However install stomps on existing config files (bacula-dir.conf etc)=20 >>>but doesn't update bacula-dir.conf.dpkg-dist. This really bothers me: the postinst is supposed to write the modified=20 config to /etc/bacula/bacula-dir.conf , or=20 /etc/bacula/bacula-dir.conf.dpkg-dist if the former already exists. >FYI: >It stomped on my modified version of /usr/lib/bacula/delete_catalog_backup= =20 >too :-( Those were supposed to be "parts of the program", that is why they are=20 placed under /usr/lib/bacula instead of /etc/bacula. Therefore, that they=20 have been overwritten is only to be expected. Another different question=20 would be whether they are supposed to be modified by the user under normal= =20 operation: in that case, that file should be moved somewhere else. >I Only just noticed! It can't be that important. It isn't :) >I see all the files in that directory have been replaced. Correct >Isn't there something new in Debian where the MD5 of the files was going=20 >to be checked before updating. That's not new... it has been there for a long time. However, this=20 mechanism is only employed for files marked as "conffiles" that is, those=20 who are supposed to contain valuable user configurations. >Maybe these are good candidates for that or maybe one should put modified= =20 >scripts elsewhere. Scripts meant to be modified should go under /etc/bacula[/scripts] This might mean i misplaced delete_catalog_backup under /usr/lib/bacula=20 when it belongs in /etc/bacula/scripts... Kern will have to clarify us(me)= =20 what purpose were those scripts intended to serve and hence where should=20 they be placed. >Dick Thanks. Keep the bug reports / unexpected behaviour report coming. They are= =20 always appreciated :) Best, J.L.=20 |