Package: lprng
Version: 3.8.B-7
Severity: normal
User: bi...@debian.org
Usertags: nm-hook-scripts
Hi,
NetworkManager provides a service named NetworkManager-dispatcher
[1], which executes scripts in
/{etc,usr/lib}/NetworkManager/dispatcher.d upon (network) state
changes.
This is in spirit similar to ifupdown's /etc/network/if-*.d/ scripts.
Previously, NetworkManager tried to call those ifupdown hook scripts
via NetworkManager-dispatcher by faking an ifupdown environment.
This caused a variety of problems though. While the concepts are
similar, the actual implementations differ significantly, e.g. when
certain events are triggered. So the mapping was never really correct
and complete. Also, some ifupdown hook scripts are meant to extend
the functionality of ifupdown. The bridge-utils and wpasupplicant
package are examples here, that provide hook scripts that should not
be run under NetworkManager, as it has builtin implementations for
this kind of functionality.
As a result, NetworkManager in trixie will remove support for running
ifupdown hook scripts.
Your package lprng installs one or more ifupdown hook scripts.
Please evaluate, whether your package would benefit from shipping a
native hook script for NetworkManager. If not, please just close this
bug report with a corresponding comment.
Such package provided hook scripts should be placed in
/usr/lib/NetworkManager/dispatcher.d/. If your hook script needs
additional configuration, please place this configuration in /etc and
source that in your hooks script. It is discouraged to place package
provided hook scripts directly in /etc/NetworkManager/dispatcher.d/.
This directory is meant for local modifications.
You can read more about the NetworkManager-dispatcher interface at
[1].
If you have further questions, you can contact me directly or
preferably the pkg-utopia mailing list at
<pkg-utopia-maintain...@lists.alioth.debian.org>.
Kind regards,
Michael
[1]
https://manpages.debian.org/bookworm/network-manager/NetworkManager-d
ispatcher.8.en.html [2]
