Debian Bug report logs - #950273
uwsgi: missing-systemd-service-for-init.d-script

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Andreas Henriksson <andreas@fatal.se>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: uwsgi: missing-systemd-service-for-init.d-script

Date: Thu, 30 Jan 2020 21:24:17 +0100

Source: uwsgi
Version: 2.0.18-7
Severity: normal

Dear Maintainer,

Please consider shipping a native systemd service masking the
currently shipped init script (fixing lintian tag[1] in subject).

It seems upstream has a section in the documentation around this:
https://uwsgi-docs.readthedocs.io/en/latest/Systemd.html

I'm not attempting a patch as it would be good to first know
if you favour the "emperor"-mode or using templated instances.

For extra bonus points look into the security hardening flags
and see which ones can be applied to limit access to what
uwsgi actually needs.

Regards,
Andreas Henriksson

[1]: https://lintian.debian.org/tags/missing-systemd-service-for-init.d-script.html
[2]: https://uwsgi-docs.readthedocs.io/en/latest/Systemd.html

Message #10 received at 950273@bugs.debian.org (full text, mbox, reply):

From: Andreas Henriksson <andreas@fatal.se>

To: 950273@bugs.debian.org

Subject: Re: uwsgi: missing-systemd-service-for-init.d-script

Date: Thu, 30 Jan 2020 22:35:15 +0100

Control: forcemerge 833067 -1

On Thu, Jan 30, 2020 at 09:24:17PM +0100, Andreas Henriksson wrote:
> Source: uwsgi
> Version: 2.0.18-7
> Severity: normal
> 
> Dear Maintainer,
> 
> Please consider shipping a native systemd service masking the
> currently shipped init script (fixing lintian tag[1] in subject).
[...]

Sorry for the noise. I see now that this has already been discussed
in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833067

If someone has interest in working on this, but the only problem
stopping them being not being comfortable with systemd I'd recommend
reaching out to the pkg-systemd-maintainers mailing list where people
are generally helpful in giving helpful systemd related feedback as
long as someone knows how their application/daemon works internally.

FWIW I personally gave a quick glance at the init script and at first it
seemed like it was a simple script that would be quite straight forward,
then I noticed the complicated logic was hidden in the do_command
script. My next thought was that maybe a systemd service file would
simply wrap the do_command script, but unfortunately it can't be
used directly because it relies on being imported from something that
has already imported LSB functionality (which can mostly be disabled
by setting VERBOSE=no, but not all cases unfortunately - eg.
log_message_done). I didn't investigate further.

Regards,
Andreas Henriksson

Message #25 received at 833067-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 833067-close@bugs.debian.org

Subject: Bug#833067: fixed in uwsgi 2.0.22-4

Date: Wed, 27 Sep 2023 16:45:01 +0000

Source: uwsgi
Source-Version: 2.0.22-4
Done: Jonas Smedegaard <dr@jones.dk>

We believe that the bug you reported is fixed in the latest version of
uwsgi, 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 833067@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard <dr@jones.dk> (supplier of updated uwsgi 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)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 27 Sep 2023 17:18:53 +0200
Source: uwsgi
Architecture: source
Version: 2.0.22-4
Distribution: unstable
Urgency: medium
Maintainer: uWSGI packaging team <pkg-uwsgi-devel@lists.alioth.debian.org>
Changed-By: Jonas Smedegaard <dr@jones.dk>
Closes: 833067 1051752
Changes:
 uwsgi (2.0.22-4) unstable; urgency=medium
 .
   [ Alexandre Rossi ]
   * fix typo in d/uwsgi-core.README.Debian
   * update pcre2 patch from upstream merge request
   * add documentation link to systemd unit files
   * systemd socket unit: directly use /run instead of /var/run
   * add lintian override for missing uwsgi systemd service (Closes: #833067)
   * fix regular expressions for mangling debian/rules;
     really truly closes: bug#1051752
 .
   [ Jonas Smedegaard ]
   * update regular expressions for mangling debian/rules:
     + tighten and merge patterns
     + fix properly cover greenlet openjdk mono rados gccgo
       (not only glusterfs)
   * really exclude arch mipsel and add arch riscv64
     related to greenlet openjdk mono rados gccgo
Checksums-Sha1:
 62c55ff1e10cef1bce7b607f4a93da37c70920a6 6934 uwsgi_2.0.22-4.dsc
 63e06d0f9d1ce33962a232b1a6cdc38b0eeb467b 72764 uwsgi_2.0.22-4.debian.tar.xz
 247f3fcb009f9c1156cb7ede30da32603f67c315 37735 uwsgi_2.0.22-4_amd64.buildinfo
Checksums-Sha256:
 f62cb34d94e27757ba836dcca6e0e4d58acaeaaeac30a1a1340b44caab711e39 6934 uwsgi_2.0.22-4.dsc
 9edb0ec5bdd08d072ce105f76bff93e3668a51a2b385a34efaa428bf1571f17e 72764 uwsgi_2.0.22-4.debian.tar.xz
 41e49406d479ca8b56a0cef72c64030c679df048fa1d5252bcebfb21920330ee 37735 uwsgi_2.0.22-4_amd64.buildinfo
Files:
 c383e8bd24cc20ef09e9f6fe90baec0f 6934 httpd optional uwsgi_2.0.22-4.dsc
 9b7a09992b79735f955880a730525a90 72764 httpd optional uwsgi_2.0.22-4.debian.tar.xz
 76785ae1712ce771fe884a697a4aaba3 37735 httpd optional uwsgi_2.0.22-4_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUUS2AACgkQLHwxRsGg
ASFy4hAAl6S5w5rdY9ecQLcD/02unlWdzuWcTgCq/CpE+RGQsucuEzsWdBRlyhNo
238Jsw2G7oPiac+98FHPYbYQ17ilXqu24fG2kLqCLQqRs1N9e8HN7CJThLXyjecw
3/4Zz4vaOWiReJUYXvxvm2fe925dYgJ9x6/zVFTS1oUMKJTu/XpeOExzS/JeLs0A
mT9ndiOap8IqJVRMJ0whTz1cW5TRVClUG16vuJ7MM5g1cvsMWLHkAbtGrmql48bC
5MG6Op3Z2RGffkmrQtwtLFPnhNkEdnoXwa0QqG+BIcBOshVpUHeMzbJhACdqi22O
F8tcfTe2SseN3CFVZoJBN34ccxSGRqvALRaqn4Npg0k3Z8y4M7xWnjn4BwDGlhfQ
eSesBF1JWFJB/8VNeRLU2dyk1EzOw0aZaL+awZ24Ba9UE+OTdjQ6RaFKqPoOQSkL
zlRshYpk759Ls0hPYM4J62UxA3MQAJx/bZ2u9hbCWLvUmpzAbeAXBfCMTQmC4w4+
CBbOvxB7OVcGzstALPJ8fn9fgQWGEXrFf0lQ25FKObtszWukyWOp/jsEsP9GQyQI
4Fc9PDzWbKt4GVyIsFpZbQipjmn3qFvUYaOIQ7g07I9m41nkPHCqOFXMatygjlhf
9pjZ2T+IRCzK3PbzTHlR9555YM2rb+jJb+F1h1zd5xmRe7NLV+U=
=GTM8
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.