The problem comes when a file's existence or non-existence affects how a package behaves (such as /etc/defense- package/autorun/launch_nuclear_missiles). If the user removes such a file to control package behavior, and then an update re-adds the files, it would change the package behavior in a way the user doesn't want, each and every time the package gets a security update.
So, since we can't know if the file removal was intentional or not, debian packaging errs on the side of caution, and doesn't re-add the file. In this particular case, of course, a missing conf file breaks the whole thing, but debian packaging doesn't have the level of sophistication to know the difference. As to what actually caused the conf file to go missing in your case, there are unfortunately no logs or traces to help track down what actually happened, so unless it happens again in future and we can get more info, we don't really have a way to find a solution :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811610 Title: latest strongswan update is broken in 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1811610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
