[Pkg-privacy-maintainers] Bug#1024137: obfs4proxy: Restart tor process on update

[meskio]

Package: obfs4proxy
Version: 0.0.14-1
Severity: important

Dear Maintainer,

obfs4proxy is normally used in comvination with tor either to connect to
a bridge or to provide a bridge. The upgrade will not be taking into
account unless tor is restarted.

Many bridge operators will update automatically the package, but the
update will not be really applied as tor will not be restarted.

Can we restart the tor proces on obfs4proxy update? I'm not sure what
are the rules in debian to restart other daemons not provided by the
package (is not even a dependency).

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.76-1.fc32.qubes.x86_64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_SOFTLOCKUP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages obfs4proxy depends on:
ii  libc6  2.35-3

obfs4proxy recommends no packages.

obfs4proxy suggests no packages.

-- no debconf information