[Expired for strongswan (Ubuntu) because there has been no activity for
60 days.]
** Changed in: strongswan (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Why wouldn't reinstalling a package restore a .conf file, when the file
is clearly in the .deb package, or when done via Synaptic?
I hadn't touched or deleted /etc/ipsec.conf. I only discovered the
problem after strongswan updates were performed, and I noticed errors in
my daily logwatch report.
Restoring config files from debs is not straightforward. We won't now
know what removed it, but, for example, if a mistake happened and for
some reason "rm -f /etc/ipsec.conf" was run, special flags have to be
given to dpkg to restore a missing config.
Since you restored it already, there is
Restoring config files from debs is not straightforward. We won't now
know what removed it, but, for example, if a mistake happened and for
some reason "rm -f /etc/ipsec.conf" was run, special flags have to be
given to dpkg to restore a missing config.
Since you restored it already, there is
I forgot to mention... when I submitted the bug report, I had already
manually restored /etc/ipsec.conf, so that's why it found that file.
--
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:
I checked /var/log/apt/history.log and /var/log/apt/history.log.1.gz and
only found references to when I tried to reinstall strongswan-
starter_5.6.3-1ubuntu4.1_amd64.deb on Jan 13. I had tried Synaptic, and
the .deb file downloaded from packages.ubuntu.com. Neither reinstalled
the missing
If installing the package doesn't restore ipsec.conf, then it's because
it was removed outside the package's control, usually.
Could you check /var/log/apt/history.log to backtrack the packages you
installed and upgrade to see if there is a clear way to reproduce this
problem?
That being said,
If installing the package doesn't restore ipsec.conf, then it's because
it was removed outside the package's control, usually.
Could you check /var/log/apt/history.log to backtrack the packages you
installed and upgrade to see if there is a clear way to reproduce this
problem?
That being said,
