On Mon, Jan 04, 2010 at 04:50:05PM +0000, Julien Cristau wrote: > On Mon, Jan 4, 2010 at 17:35:59 +0100, Patrick Schoenfeld wrote: > > > > I still believe that a check should be added for the symlink. If it > > > was removed, don't RE-add it, it the source conf file > > > /etc/cacti/apache.conf doesn't exist remove the broken symlink. > > > > How is this supposed to work? There is no difference between a manually > > removed file and a file that has never been created in the first place. > > > Yes there is. postinst scripts know whether the package is being > upgraded or newly installed.
Ah, good point. The third param. Still questionable if this should be handled this way. After all removing the symlink could be an accident as well, while one could argue that the "preserve administrator changes" case is more important as "take care for stupidness of people". And I haven't even searched policy for the symlink case, so I cannot tell if its is backed by policy however. So sorry for the noise, except that I still not understand why people answer a priority high question with "Configure my webserver: apache2" just for removing the symlink, it results into after, that. Best Regards, Patrick -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
