What about the observation (second half of Comment #42) that cupsd.conf is *not* part of cups-daemon.list nor cups-daemon.conffiles ? This seems to be the reason systems are ending up with ancient crufty cupsd.conf. The same observation occurs in Comment #44, where a different approach for keeping the file up-to-date is proposed. Personally, I favor the dpkg conffile mechanism, that's how cups-browsed does it, and that ensures that my cups-browsed.conf remains up-to-date (while prompting me whenever I have customized the file). The same approach seems fine to me for cupsd.conf. Does anyone know a reason why cupsd.conf is isn't already part of dpkg conffile mechanism?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2133207 Title: cups security update causes issues with invalid config file To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/2133207/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
