On Mon, 2019-01-14 at 21:25 +0100, Florian Schlichting wrote: > Hi, > > in the course of looking into the upgrade failure, I ended up purging > dnssec-trigger and then installed it again. I notice this creates > keys > and config files in both /etc/ and /etc/dnssec-trigger?! Different to > Alex, I get traceback in the middle of the log (also for subsequent > attempts to 'apt-get install -f' etc):
... I thought I had fixed that... But apparently I had just found a few other places that had hardcoded paths that weren't being updated. Apparently there are still more hardcoded paths. I'm a little worried about just rm-ing previously invalid locations for configuration files. Might you have suggestions about how to safely clean up dnssec-triggers configuration file mess? (At the very least it seems like it should check that a configuration file was actually created by it before just deleting it) Diane
