Debian Bug report logs - #833067
uwsgi: does not use systemd for services

Display info messages

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

From: Chris Warrick <kwpolska@gmail.com>

To: submit@bugs.debian.org

Subject: uwsgi: does not use systemd for services

Date: Sun, 31 Jul 2016 14:34:04 +0200

Subject: uwsgi: add systemd service files
Package: uwsgi
Version: 2.0.7-1
Severity: normal

Dear Maintainer,

the uwsgi (and uwsgi-emperor) packages do not contain systemd service
files, instead opting for old LSB service files. Other distros
(Fedora, CentOS with EPEL, Arch Linux) already use systemd units. The
uwsgi developers provide a systemd
service file in the documentation [0].  Is it possible to update the
Debian packages to ship those files instead of /etc/init.d/uwsgi* as
well?

[0]: http://uwsgi-docs.readthedocs.io/en/latest/Systemd.html

-- System Information:
Debian Release: 8.5
 APT prefers stable
 APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages uwsgi depends on:
ii  initscripts  2.88dsf-59
ii  lsb-base     4.1+Debian13+nmu1
ii  uwsgi-core   2.0.7-1

uwsgi recommends no packages.

uwsgi suggests no packages.

-- no debconf information

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

From: Jonas Smedegaard <dr@jones.dk>

To: Chris Warrick <kwpolska@gmail.com>, 833067@bugs.debian.org

Subject: Re: [pkg-uWSGI-devel] Bug#833067: uwsgi: does not use systemd for services

Date: Sun, 31 Jul 2016 15:57:30 +0200

[Message part 1 (text/plain, inline)]

Hi Chris,

Quoting Chris Warrick (2016-07-31 14:34:04)
> the uwsgi (and uwsgi-emperor) packages do not contain systemd service 
> files, instead opting for old LSB service files. Other distros 
> (Fedora, CentOS with EPEL, Arch Linux) already use systemd units. The 
> uwsgi developers provide a systemd service file in the documentation 
> [0].  Is it possible to update the Debian packages to ship those files 
> instead of /etc/init.d/uwsgi* as well?

I am not comfortable writing/patching/debugging systemd files yet 
myself.

I would very much welcome someone joining the team who would take the 
responsibility of caring for those files, ensuring that the behaviour 
across init systems is consistent (e.g. write Debian-specific systemd 
files behaving same as the Debian-specific sysV files, or help adapt the 
sysV files to match whatever possibly more sensible behaviour of 
upstream shipped systemd files).

Would you perhaps be interested in joining our team to care for that?


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

[signature.asc (application/pgp-signature, inline)]

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

From: Chris Warrick <kwpolska@gmail.com>

To: 833067@bugs.debian.org

Subject: Re: [pkg-uWSGI-devel] Bug#833067: uwsgi: does not use systemd for services

Date: Sun, 31 Jul 2016 16:05:13 +0200

On 31 July 2016 at 15:57, Jonas Smedegaard <dr@jones.dk> wrote:
> Hi Chris,
>
> Quoting Chris Warrick (2016-07-31 14:34:04)
>> the uwsgi (and uwsgi-emperor) packages do not contain systemd service
>> files, instead opting for old LSB service files. Other distros
>> (Fedora, CentOS with EPEL, Arch Linux) already use systemd units. The
>> uwsgi developers provide a systemd service file in the documentation
>> [0].  Is it possible to update the Debian packages to ship those files
>> instead of /etc/init.d/uwsgi* as well?
>
> I am not comfortable writing/patching/debugging systemd files yet
> myself.
>
> I would very much welcome someone joining the team who would take the
> responsibility of caring for those files, ensuring that the behaviour
> across init systems is consistent (e.g. write Debian-specific systemd
> files behaving same as the Debian-specific sysV files, or help adapt the
> sysV files to match whatever possibly more sensible behaviour of
> upstream shipped systemd files).
>
> Would you perhaps be interested in joining our team to care for that?

Sorry, but I don’t have time to do OS development, I despise SysV init
and I don’t use Debian often anyways. I’m afraid you will have to find
someone else, or accept the fact that there might be some minor
incompatibilities. That said, looking at /etc/init.d/uwsgi-emperor, it
could be replaced by uwsgi’s proposed systemd service file pretty
easily. (I have no idea about /etc/init.d/uwsgi)

-- 
Chris Warrick <https://chriswarrick.com/>
PGP: 5EAAEA16

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

From: Jonas Smedegaard <dr@jones.dk>

To: Chris Warrick <kwpolska@gmail.com>, 833067@bugs.debian.org

Subject: Re: [pkg-uWSGI-devel] Bug#833067: Bug#833067: uwsgi: does not use systemd for services

Date: Sun, 31 Jul 2016 18:36:32 +0200

[Message part 1 (text/plain, inline)]

Quoting Chris Warrick (2016-07-31 16:05:13)
> On 31 July 2016 at 15:57, Jonas Smedegaard <dr@jones.dk> wrote:
> > Quoting Chris Warrick (2016-07-31 14:34:04)
> >> the uwsgi (and uwsgi-emperor) packages do not contain systemd 
> >> service files, instead opting for old LSB service files. Other 
> >> distros (Fedora, CentOS with EPEL, Arch Linux) already use systemd 
> >> units. The uwsgi developers provide a systemd service file in the 
> >> documentation [0].  Is it possible to update the Debian packages to 
> >> ship those files instead of /etc/init.d/uwsgi* as well?
> >
> > I am not comfortable writing/patching/debugging systemd files yet 
> > myself.
> >
> > I would very much welcome someone joining the team who would take 
> > the responsibility of caring for those files, ensuring that the 
> > behaviour across init systems is consistent (e.g. write 
> > Debian-specific systemd files behaving same as the Debian-specific 
> > sysV files, or help adapt the sysV files to match whatever possibly 
> > more sensible behaviour of upstream shipped systemd files).
> >
> > Would you perhaps be interested in joining our team to care for 
> > that?
> 
> Sorry, but I don’t have time to do OS development, I despise SysV init 
> and I don’t use Debian often anyways. I’m afraid you will have to find 
> someone else, or accept the fact that there might be some minor 
> incompatibilities.

Fair enough.


> That said, looking at /etc/init.d/uwsgi-emperor, it could be replaced 
> by uwsgi’s proposed systemd service file pretty easily. (I have no 
> idea about /etc/init.d/uwsgi)

Thanks for your input.  They are appreciated - and now on record, 
pending someone to take on that task.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

[signature.asc (application/pgp-signature, inline)]

Message #35 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.