Hello,

I think that the executables should be moved from /usr/lib/cni to /usr/libexec/cni

/usr/libexec is a more sutable location for executables (and it will
also help with systemd labeling)

Searching the archive with codesearch it seems that ansible is the only
other package with a reference to that path, but it seems that it will
try both /usr/libexec/cni and /usr/lib/cni. In worst case, a symlink
could be added I guess?

Same should happen with /usr/lib/cni/dnsname that is installed by
golang-github-containernetworking-plugin-dnsname I guess?

Could you please move the files in /usr/libexec/cni?

Kind regards,
Laurent Bigonville

On Wed, 02 Feb 2022 14:31:25 +0100 Laurent Bigonville <bigon@debian.org>  wrote:

 > /usr/libexec is a more sutable location for executables (and it will
 > also help with systemd labeling)

s/systemd/selinux

If we reset the time to the beginning  of this package, then I think
it should install files in libexec.

But what's the benefit to do it now, after this package has been in
stable release.

The path /usr/lib/cni/ is also included in containerd's conffile.
Please do a better search with codesearch.d.n
https://codesearch.debian.net/search?q=%2Fusr%2Flib%2Fcni&literal=1&perpkg=1

 I prefer not to change it.

Le 2/02/22 à 14:58, Shengjing Zhu a écrit :

Usage of /usr/libexec was probably not allowed by the debian policy when
the package was first created :)

Well I was proposing this because it makes the selinux a tiny bit easier
(and also a question of consistencies as a lot of packages have moved
their executables in /usr/libexec)

Mhh interesting, that didn't show up when I did the search an hour ago

That could still be managed with making a symlink
OK, I'll manage this in an other way then