Hello, I've re-run the update on a virtual machine to see what would go wrong. I can say the update process did not go wrong "per se". It asked me what files i wanted to replace, so i told it to replace all the .conf files. It did, so of course i removed the line "UNCONFIGURED" in dansguardian.conf and it could start.
The update process is OK. It's the mere fact that there's such an important update in security repositories that caught my attention. Here's the situation here : i've got 25 dansguardian installations, which synchronise their configuration files (along with blacklists) from a "master" dansguardian installation. All previous installations were 2.8. When a new installation was done (i.e. my customised CD shipping dansguardian) on a new server, security patches were applied at installation so 2.9 was installed, then it synchronised and it got 2.8 configuration files. New installation was broken. Also if a current installation is updated, config files are replaced and future synchronisations, baised on .diff files, will probably fail. I know the synchronisation process isn't so smart. That's because i assumed no such big update would hit the security repositories. A security update which changes features can harm production environments; that was the situation here. I was unaware of the needed update of libclamav; I understand the dilemna, there were 2 possible choices and none of it were perfect, so it was decided to go for the most secure one. I guess it was impossible to patch libclamav3 instead of updating to libclamav5? -- 8.04 security update breaks configuration https://bugs.launchpad.net/bugs/385567 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
