On Mon, 11 Sept 2023 at 13:03, Daniel Gröber <d...@darkboxed.org> wrote: > > Hi, > > On Mon, Sep 11, 2023 at 08:32:10AM +0200, Sven Joachim wrote: > > > After upgrading to 6.5.0-1 adequate shows: > > > > > > adequate found packaging bugs > > > ----------------------------- > > > > > > iproute2: obsolete-conffile /etc/iproute2/rt_tables.d/README > > > iproute2: obsolete-conffile /etc/iproute2/rt_protos.d/README > > > iproute2: obsolete-conffile /etc/iproute2/rt_protos > > > iproute2: obsolete-conffile /etc/iproute2/rt_dsfield > > > iproute2: obsolete-conffile /etc/iproute2/nl_protos > > > iproute2: obsolete-conffile /etc/iproute2/ematch_map > > > iproute2: obsolete-conffile /etc/iproute2/bpf_pinning > > > > There are a few more leftovers still present in 6.5.0-2: > > > > ,---- > > | $ adequate iproute2 > > | iproute2: obsolete-conffile /etc/iproute2/group > > | iproute2: obsolete-conffile /etc/iproute2/rt_realms > > | iproute2: obsolete-conffile /etc/iproute2/rt_scopes > > | iproute2: obsolete-conffile /etc/iproute2/rt_tables > > `---- > > > > There are also the directories /etc/iproute2/rt_protos.d, > > /etc/iproute2/rt_tables.d and /etc/iproute2 which are no longer shipped > > in the package. Unfortunately dpkg-maintscript-helper does not clean > > those up automatically (see #584185). > > I want to question whether removing these conffiles is a good idea at > all. I'm probably one of the few people that actually muck around in there > but it seems like this is going to break things for any users that do. > > Is it really sensible to move these files to /usr/lib in the standard > Debian installation? It seems to me upstream only wants to better support > /usr-only deployments without /etc: > > commit 0a0a8f12fa1b03dd0ccbebf5f85209d1c8a0f580 > Read configuration files from /etc and /usr > > Add support for the so called "stateless" configuration pattern (read > from /etc, fall back to /usr), giving system administrators a way to > define local configuration without changing any distro-provided files. > > In practice this means that each configuration file FOO is loaded > from /usr/lib/iproute2/FOO unless /etc/iproute2/FOO exists. > > So why not simply keep the conffiles in /etc for regular admins and let > people that want to do image based deployments create /usr/lib/iproute2 if > they want to override or remove /etc?
As far as I understand dpkg's conffile machinery should recognize if you changed anything, and leave it in place. Upstream moved the default ones to /usr, so we just follow what they do.
