Dear Maintainer(s),

hopm has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because a transitional
sysv-init-to-unit generator was shipped by systemd. This is in the
process of being deprecated and will be removed by the time Trixie
ships, so the remaining packages that ship init scripts without
systemd units will stop working.

There are various advantages to using native units, for example the
legacy generator cannot tell the different between a oneshot service
and a long running daemon. Also, sanboxing and security features
become available for services. For more information, consult the
systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html

You can find the Lintian warning here:

https://lintian.debian.org/sources/hopm

In case this is a false positive, please add a Lintian override to
silence it and then close this bug.

Thanks!

Dear Maintainer(s) of affected packages, these bugs have been open for
more than 2 years now. Policy was updated to make units mandatory for
system services. The removal of compat with sysv-init scripts from
systemd has been postponed from trixie to forky, but it is now
approaching. In approximately a month's time, this should hit
unstable, if everything goes well.

Therefore in order to ensure the remaining bugs do not fall through
the cracks I am raising severity again, as there is a very high chance
the affected packages will stop working as intended in about a month's
time in the default setup.

As already mentioned in the original bug report, if your package is
not intended to work as a systemd service or under systemd at all,
please feel free to downgrade or close+wontifx or anything else as you
see fit. The severity raising is not intended to make anyone support
scenarios they don't wish to support, but simply to ensure attention
is given to the issue, even if just to close+wontfix. Also the bugs
were opened based on Lintian reports, and it is possible that there
might be false positives.

Thanks for your work and understanding.

Hi,

I prepared an attached packaging patch adding a native systemd unit for
`hopm`.

The patch is intentionally narrow:

- adds `debian/hopm.service`
- keeps the existing SysV init script for non-systemd compatibility
- preserves the package's current disabled-by-default behavior by adding
  `dh_installsystemd --no-enable` alongside the existing
  `dh_installinit --no-enable`
- uses `/run/hopm/hopm.pid` with `RuntimeDirectory=hopm`
- uses `ExecReload=/bin/kill -HUP $MAINPID`, matching upstream's existing
  SIGHUP handling

Validation performed:

- local `dpkg-buildpackage -us -uc -b`
- clean `sbuild` on `unstable/arm64`
- clean `sbuild` on `trixie/arm64`

Both clean builds completed successfully. Lintian only reported pre-existing
warnings (`depends-on-obsolete-package lsb-base`, `no-manual-page`,
`old-fsf-address-in-copyright-file`).

This was a fun Bug of the Day to work through.

Regards,
James

Howdy,

I have some changes staged locally, one of which adds a systemd unit which
includes some hardening as well.  I guess I was delyaing until upstream
released a new version or I was positive the changes wouldn't introduce a
regression, but since it's been running for months and I'm not planning on
making any changes to how it runs, I'm not sure how I could be more
confident of it.

The builds would work because nothing with the buildsystem was really
changed, since it's an addition of a systemd unit whether it runs
correctly or not would be of far more interest.

Note, it's useful to send a CC to the maint address as for some reason
debbugs doesn't forward replies to bugs to the maintainer.


Regards,

~Unit 193
Unit193 @ Libera
Unit193 @ OFTC

Good to hear - happy to step aside. Please consider my patch superseded
by your staged version. A production-tested unit with hardening is a much
stronger basis than my build-only validation :).

Fair point, and a useful lesson. I validated clean sbuild runs on
unstable/arm64 and trixie/arm64 but did not do functional service testing.
If you would find it useful, I am happy to test your unit against the same
targets before you upload.

Noted, thanks for the tip.

Regards,
James

We believe that the bug you reported is fixed in the latest version of
hopm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1039221@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193 <unit193@debian.org> (supplier of updated hopm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 28 May 2026 04:50:22 -0400
Source: hopm
Architecture: source
Version: 1.1.10-2
Distribution: unstable
Urgency: medium
Maintainer: Unit 193 <unit193@debian.org>
Changed-By: Unit 193 <unit193@debian.org>
Closes: 1039221
Changes:
 hopm (1.1.10-2) unstable; urgency=medium
 .
   * d/*: Rename files to prefix with package name.
   * d/control, d/rules: Drop 'priority', R³, lsb-base, and --as-needed.
   * d/control: Bump DH compat to 13.
   * d/copyright: Bump years.
   * d/hopm.service, d/rules: Add systemd unit. (Closes: #1039221)
   * d/watch:
     - Update, GitHub no longer includes tags on releases page.
     - Use version 5.
   * Update Standards-Version to 4.7.4.
Checksums-Sha1:
 82507ef60d63c8f0b521659818eb63421fa546c9 1833 hopm_1.1.10-2.dsc
 44e7ba9b26b416eb278080a5270df5a4875a8cf6 489453 hopm_1.1.10.orig.tar.gz
 35751244e4a7a384033a221d41bb07256038a9f6 4364 hopm_1.1.10-2.debian.tar.xz
 fe2f088151e470d54d9b5a05d1251bda2bcc963f 5922 hopm_1.1.10-2_amd64.buildinfo
Checksums-Sha256:
 d728d75959cb367e4558c74190466d3a35b7340af0974ff52e4d6ed52039ac13 1833 hopm_1.1.10-2.dsc
 dfe26e8963444467bb95380d4b40af68ca6721c3b6f093b332f15ee85683068b 489453 hopm_1.1.10.orig.tar.gz
 dd414473eb1addc613460982a61762e356e71cbf034695e7cbb8a204f9e8f750 4364 hopm_1.1.10-2.debian.tar.xz
 a72d7e892b18bcac66c315ab945f7423d09153239e9dcbbde151990ff94f1064 5922 hopm_1.1.10-2_amd64.buildinfo
Files:
 7c59c5e6c58ab5eef20ac90ce7443cdd 1833 net optional hopm_1.1.10-2.dsc
 439d1be1b6bda1ef6a5fde805ea2f687 489453 net optional hopm_1.1.10.orig.tar.gz
 b754913c322dd54b31abbb41c0e518a7 4364 net optional hopm_1.1.10-2.debian.tar.xz
 6a1a35e9190e88411b00f3ca0d337b12 5922 net optional hopm_1.1.10-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmoYBmIACgkQUAHhsJqj
dEvC/Q//UemBbIt7Qt6B8RsIPoGj8Dr3x0o0KD/eGKc9ZCDHNNepNvBiAudYDpzB
SMhl+aJnaNR2xNZiC/X4uuSRq4dS6wruy+vj6Qg3we+K1H2+degApMoHYTaQmpl6
doinWR96jJJU5QL1w/9UJLOmmmkcDFagejhoASOdTBJBFUlzlPBiO69I8WxDzv8H
r6KJwvOV991NGdY+TfSkc4OuZ7X/R9suz1ollXFp6IWQSyfnnntQGDQwYi+tkYrz
yTnmqnOJ9QJNUd5T20Mcn5uQ6ADK3mh6i62u3Yiphq5JINLgAiaXv1uEYIrouoBy
DFYeY2469QJ1KjAfTGShKtGQLNQy1BnZzmfuyhO3DwbN6S9sSHeluw0FZ1RzCSY5
0hMeBjBhrQdCKxZd3zz3QInsbxehIoxfrfl+fddC66aoy/pVS40ac6KV37TXiV41
ynfSSe4CAW1u99Gi2g9C2o/bAdDAJJTzttnR/zfKx/9NkuCYPDSpLbGEy2iveaMv
OOc2rub4sYGYV0pJdrqdZZHid0+irocI8Q9l1oAMAWMjIA75xmcDQH1c8qGO/Fz2
GbQz3kAFF+UShAd3lSiyTQ1B2QN78+0Isa/BI4RepfQaXkafieh4gSP23PepM2zM
eICWedexxMqNCgWcCjMAi8Sj8CYYw8767FbG1IwZpZ66afTf95U=
=ZByQ
-----END PGP SIGNATURE-----