Not good. I guess we just need to figure out the proper file path.
If /var/lib/i2p/i2p-config/router.config
is regarded by i2p I would imagine that
/etc/i2p/router.config
OR/etc/i2p/i2p-config/router.config
would overrule /var/lib/i2p/i2p-config/router.config
. Please ask upstream about this. Ask if Debian ships a file /var/lib/i2p/i2p-config/router.config
then how derivative distributions such as Whonix or local system administrators would configure their i2p daemon. Which file location to use.
That’s really hacky, often fragile and should only be last resort if upstream is aware and there is no better solution yet.
/var/lib/i2p/i2p-config/router.config
is not really “owned” (not managed by its APT package) by any i2p package.
dpkg -S /var/lib/i2p/i2p-config/router.config
dpkg-query: no path found matching pattern /var/lib/i2p/i2p-config/router.config
No surprise since file location in in /var.
But we don’t know by what and how /var/lib/i2p/i2p-config/router.config is (re-)generated. Any manual change (or change by sed) might be reverted later (such as perhaps on pacakge upgrades) which would then break the functionality provided by the sed hack.
See also:
cat /usr/share/doc/i2p-router/README.Debian
cat /lib/systemd/system/i2p.service
cat /etc/default/i2p
cat /etc/i2p/wrapper.config