Devuan logs - #721, boring messages


Message sent to [email protected], [email protected]:


X-Loop: [email protected]
Subject: bug#721: Jabberd2 start failture on devuan
Reply-To: Leonid <[email protected]>, [email protected]
Resent-From: Leonid <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
X-Loop: [email protected]
Resent-Date: Tue, 01 Nov 2022 07:32:02 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Devuan-PR-Message: report 721
X-Devuan-PR-Package: jabberd2
X-Devuan-PR-Keywords: 
Received: via spool by [email protected] id=B.166728781011644
          (code B); Tue, 01 Nov 2022 07:32:02 +0000
Received: (at submit) by bugs.devuan.org; 1 Nov 2022 07:30:10 +0000
Delivered-To: [email protected]
Received: from mail.dyne.org [141.95.83.167]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Tue, 01 Nov 2022 07:30:10 +0000 (UTC)
Received: from forward502o.mail.yandex.net (forward502o.mail.yandex.net [37.140.190.204])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mx1.dyne.org (Postfix) with ESMTPS id 1682D7409E0
	for <[email protected]>; Tue,  1 Nov 2022 08:28:45 +0100 (CET)
Authentication-Results: mx1.dyne.org;
	dkim=pass (1024-bit key; unprotected) header.d=ya.ru [email protected] header.a=rsa-sha256 header.s=mail header.b=LaVVvp5q;
	dkim-atps=neutral
Received: from sas2-ffeb92823cb1.qloud-c.yandex.net (sas2-ffeb92823cb1.qloud-c.yandex.net [IPv6:2a02:6b8:c08:6803:0:640:ffeb:9282])
	by forward502o.mail.yandex.net (Yandex) with ESMTP id D4E3425D407D
	for <[email protected]>; Tue,  1 Nov 2022 10:28:48 +0300 (MSK)
Received: by sas2-ffeb92823cb1.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id lvragILrmn-SkgmEIV2;
	Tue, 01 Nov 2022 10:28:47 +0300
X-Yandex-Fwd: 1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ya.ru; s=mail; t=1667287727;
	bh=sDq8utY7olMsWW8uIMpshjNy0furpt5rJyJjUKiPMs8=;
	h=In-Reply-To:To:Date:References:Subject:Message-ID:From;
	b=LaVVvp5qyKGCW70iryXwMR0Cv3+wBSPWrFnGHAjF1NkQh+n8dO/TFeaPeVIcIPeyR
	 Mmwaxt2pYI8uop2/+M8wYjXT3F0/McPkPY41pp/GnFrGHdGasubQImAKOgIpI276gR
	 AJVRPmWaYXkAnjBFWe+GKFZ9ZdEMPtoLu6noiTuE=
Authentication-Results: sas2-ffeb92823cb1.qloud-c.yandex.net; dkim=pass [email protected]
Content-Type: multipart/alternative;
 boundary="------------0xxT01XKnI9qwpQT02LLJ1y8"
Message-ID: <[email protected]>
Date: Tue, 1 Nov 2022 12:28:46 +0500
MIME-Version: 1.0
Content-Language: en-US
To: [email protected]
From: Leonid <[email protected]>
In-Reply-To: <[email protected]>
X-Forwarded-Message-Id: <[email protected]>
X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE
	autolearn=disabled version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on mail.dyne.org

This is a multi-part message in MIME format.
--------------0xxT01XKnI9qwpQT02LLJ1y8
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Package: jabberd2
Version: 2.7.0-2
Hello, dear Devuan developers!
I can't fix this bug:
I try run jabberd2 service, it doesn't work.

```
root@hostname~# service jabberd2 start
Starting Jabber services: router smstart-stop-daemon: missing group name
<Failed> s2sstart-stop-daemon: missing group name
<Failed> c2sstart-stop-daemon: missing group name
<Failed>.
```
What do you think about this problem?

P.S.:
I'm using Devuan 4.
5.10.74-v8 aarch64 GNU/Linux
-- 
Devuan user,
Leonid
--------------0xxT01XKnI9qwpQT02LLJ1y8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-forward-container">
      <div><font face="monospace">Package: jabberd2<br>
          Version: <span
            style="color:#000000;background-color:#ffffff;">2.7.0-2</span></font>
      </div>
      <div><font face="monospace">Hello, dear Devuan developers!</font></div>
      <div><font face="monospace"> </font></div>
      <div><font face="monospace">I can't fix this bug:</font></div>
      <div><font face="monospace">I try run jabberd2 service, it doesn't
          work.</font></div>
      <div><font face="monospace"><br>
          ```</font></div>
      <div>
        <div><font face="monospace">root@hostname~# service jabberd2
            start <br>
            Starting Jabber services: router smstart-stop-daemon:
            missing group name<br>
            &lt;Failed&gt; s2sstart-stop-daemon: missing group name<br>
            &lt;Failed&gt; c2sstart-stop-daemon: missing group name<br>
            &lt;Failed&gt;.<br>
            ```</font></div>
      </div>
      <div><font face="monospace"> </font></div>
      <div><font face="monospace">What do you think about this problem?</font></div>
      <div><font face="monospace"><br>
        </font></div>
      <div><font face="monospace">P.S.:</font></div>
      <div><font face="monospace">I'm using Devuan 4.</font><br>
        <font face="monospace"><span style="font-family:monospace"><span
              style="color:#000000;background-color:#ffffff;">5.10.74-v8
              aarch64 GNU/Linux</span><br>
          </span></font></div>
      <div><font face="monospace"> </font></div>
      <div><font face="monospace">-- </font></div>
      <div><font face="monospace">Devuan user,</font></div>
      <div><font face="monospace">Leonid</font></div>
    </div>
  </body>
</html>

--------------0xxT01XKnI9qwpQT02LLJ1y8--

Message sent:


Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
Content-Type: text/plain; charset=utf-8
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Leonid <[email protected]>
Subject: bug#721: Acknowledgement (Jabberd2 start failture on devuan)
Message-ID: <[email protected]>
References: <[email protected]>
X-Devuan-PR-Message: ack 721
X-Devuan-PR-Package: jabberd2
Reply-To: [email protected]
Date: Tue, 01 Nov 2022 07:32:04 +0000

Thank you for filing a new bug report with Devuan.

You can follow progress on this bug here: 721: https://bugs.devuan.org/cgi/=
bugreport.cgi?bug=3D721.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 [email protected]

If you wish to submit further information on this problem, please
send it to [email protected].

Please do not send mail to [email protected] unless you wish
to report a problem with the Bug-tracking system.

--=20
721: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D721
Devuan Bug Tracking System
Contact [email protected] with problems

Message sent to [email protected], [email protected]:


X-Loop: [email protected]
Subject: bug#721: Jabberd2 start failture on devuan
Reply-To: Mark Hindley <[email protected]>, [email protected]
Resent-From: Mark Hindley <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
X-Loop: [email protected]
Resent-Date: Wed, 02 Nov 2022 09:26:01 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Devuan-PR-Message: followup 721
X-Devuan-PR-Package: jabberd2
X-Devuan-PR-Keywords: 
References: <[email protected]> <[email protected]> <[email protected]>
Received: via spool by [email protected] id=B721.166738104910448
          (code B ref 721); Wed, 02 Nov 2022 09:26:01 +0000
Received: (at 721) by bugs.devuan.org; 2 Nov 2022 09:24:09 +0000
Delivered-To: [email protected]
Received: from mail.dyne.org [141.95.83.167]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 02 Nov 2022 09:24:08 +0000 (UTC)
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by mx1.dyne.org (Postfix) with ESMTPS id 7EBDD740A2E
	for <[email protected]>; Wed,  2 Nov 2022 10:24:01 +0100 (CET)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1oq9yd-0007hE-I6; Wed, 02 Nov 2022 09:24:03 +0000
Received: (nullmailer pid 30208 invoked by uid 1000);
	Wed, 02 Nov 2022 09:24:03 -0000
Date: Wed, 2 Nov 2022 09:24:03 +0000
From: Mark Hindley <[email protected]>
To: Leonid <[email protected]>, [email protected]
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
X-Spam-Status: No, score=1.4 required=5.0 tests=KHOP_HELO_FCRDNS,RDNS_DYNAMIC
	autolearn=disabled version=3.4.6
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on mail.dyne.org

Control: tags -1 moreinfo
Control: tags -1 debian

Leonid,

On Tue, Nov 01, 2022 at 12:28:46PM +0500, Leonid wrote:
>    Package: jabberd2
>    Version: 2.7.0-2
>    Hello, dear Devuan developers!
> 
>    I can't fix this bug:
>    I try run jabberd2 service, it doesn't work.

Thanks for this. In general jabberd2 is not forked in Devuan and we use Debian's
packages directly without recompilation. So any bug should be reported to
Debian's BTS.

Looking at Debian's tracker[1], I don't see any significant recent changes. You
will need to provide more information.

 - What group is jabber trying to run as? It looks[2] as if it should be
   jabber. Does the group exist? It should be created in the preinst[3]
 
Mark

[1]  https://tracker.debian.org/pkg/jabberd2

[2]  https://salsa.debian.org/xmpp-team/jabberd2/-/blob/master/debian/init#L18

[3]  https://salsa.debian.org/xmpp-team/jabberd2/-/blob/master/debian/preinst#L38

Message received at [email protected]:


Received: (at 721) by bugs.devuan.org; 2 Nov 2022 09:24:09 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from mail.dyne.org [141.95.83.167]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 02 Nov 2022 09:24:08 +0000 (UTC)
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by mx1.dyne.org (Postfix) with ESMTPS id 7EBDD740A2E
	for <[email protected]>; Wed,  2 Nov 2022 10:24:01 +0100 (CET)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1oq9yd-0007hE-I6; Wed, 02 Nov 2022 09:24:03 +0000
Received: (nullmailer pid 30208 invoked by uid 1000);
	Wed, 02 Nov 2022 09:24:03 -0000
Date: Wed, 2 Nov 2022 09:24:03 +0000
From: Mark Hindley <[email protected]>
To: Leonid <[email protected]>, [email protected]
Subject: Re: bug#721: Jabberd2 start failture on devuan
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
X-Debbugs-No-Ack: No Thanks
X-Spam-Status: No, score=1.4 required=5.0 tests=KHOP_HELO_FCRDNS,RDNS_DYNAMIC
	autolearn=disabled version=3.4.6
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on mail.dyne.org

Control: tags -1 moreinfo
Control: tags -1 debian

Leonid,

On Tue, Nov 01, 2022 at 12:28:46PM +0500, Leonid wrote:
>    Package: jabberd2
>    Version: 2.7.0-2
>    Hello, dear Devuan developers!
> 
>    I can't fix this bug:
>    I try run jabberd2 service, it doesn't work.

Thanks for this. In general jabberd2 is not forked in Devuan and we use Debian's
packages directly without recompilation. So any bug should be reported to
Debian's BTS.

Looking at Debian's tracker[1], I don't see any significant recent changes. You
will need to provide more information.

 - What group is jabber trying to run as? It looks[2] as if it should be
   jabber. Does the group exist? It should be created in the preinst[3]
 
Mark

[1]  https://tracker.debian.org/pkg/jabberd2

[2]  https://salsa.debian.org/xmpp-team/jabberd2/-/blob/master/debian/init#L18

[3]  https://salsa.debian.org/xmpp-team/jabberd2/-/blob/master/debian/preinst#L38


Message received at [email protected]:


Received: (at 721) by bugs.devuan.org; 2 Nov 2022 09:24:09 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from mail.dyne.org [141.95.83.167]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 02 Nov 2022 09:24:08 +0000 (UTC)
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by mx1.dyne.org (Postfix) with ESMTPS id 7EBDD740A2E
	for <[email protected]>; Wed,  2 Nov 2022 10:24:01 +0100 (CET)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1oq9yd-0007hE-I6; Wed, 02 Nov 2022 09:24:03 +0000
Received: (nullmailer pid 30208 invoked by uid 1000);
	Wed, 02 Nov 2022 09:24:03 -0000
Date: Wed, 2 Nov 2022 09:24:03 +0000
From: Mark Hindley <[email protected]>
To: Leonid <[email protected]>, [email protected]
Subject: Re: bug#721: Jabberd2 start failture on devuan
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
X-Debbugs-No-Ack: No Thanks
X-Spam-Status: No, score=1.4 required=5.0 tests=KHOP_HELO_FCRDNS,RDNS_DYNAMIC
	autolearn=disabled version=3.4.6
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on mail.dyne.org

Control: tags -1 moreinfo
Control: tags -1 debian

Leonid,

On Tue, Nov 01, 2022 at 12:28:46PM +0500, Leonid wrote:
>    Package: jabberd2
>    Version: 2.7.0-2
>    Hello, dear Devuan developers!
> 
>    I can't fix this bug:
>    I try run jabberd2 service, it doesn't work.

Thanks for this. In general jabberd2 is not forked in Devuan and we use Debian's
packages directly without recompilation. So any bug should be reported to
Debian's BTS.

Looking at Debian's tracker[1], I don't see any significant recent changes. You
will need to provide more information.

 - What group is jabber trying to run as? It looks[2] as if it should be
   jabber. Does the group exist? It should be created in the preinst[3]
 
Mark

[1]  https://tracker.debian.org/pkg/jabberd2

[2]  https://salsa.debian.org/xmpp-team/jabberd2/-/blob/master/debian/init#L18

[3]  https://salsa.debian.org/xmpp-team/jabberd2/-/blob/master/debian/preinst#L38


Message sent to [email protected], [email protected]:


X-Loop: [email protected]
Subject: bug#721: Jabberd2 start failture on devuan
Reply-To: Mark Hindley <[email protected]>, [email protected]
Resent-From: Mark Hindley <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
X-Loop: [email protected]
Resent-Date: Wed, 11 Jan 2023 19:42:02 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Devuan-PR-Message: followup 721
X-Devuan-PR-Package: jabberd2
X-Devuan-PR-Keywords: moreinfo debian
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>
Received: via spool by [email protected] id=B721.16734660366891
          (code B ref 721); Wed, 11 Jan 2023 19:42:02 +0000
Received: (at 721) by bugs.devuan.org; 11 Jan 2023 19:40:36 +0000
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 11 Jan 2023 19:40:36 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id EAVKOogQv2NYEQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 11 Jan 2023 19:39:52 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id E0518B85; Wed, 11 Jan 2023 19:39:52 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 9EEAD2A8
	for <[email protected]>; Wed, 11 Jan 2023 19:39:49 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pFgwu-0004It-Fj; Wed, 11 Jan 2023 19:39:48 +0000
Received: (nullmailer pid 2349 invoked by uid 1000);
	Wed, 11 Jan 2023 19:39:48 -0000
Date: Wed, 11 Jan 2023 19:39:48 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Cc: Leonid <[email protected]>
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

Control: tags -1 patch

On Wed, Nov 02, 2022 at 09:24:03AM +0000, Mark Hindley wrote: 
>  - What group is jabber trying to run as? It looks[2] as if it should be
>    jabber. Does the group exist? It should be created in the preinst[3]

I have had a quick look at this and the USER and GROUP environment variables
need to be exported so that they are passed to the scripts in
/etc/jabberd2/component.d.

USER is already an exported variable, so actually works either way, but GROUP
isn't so fails.

Try this.

diff -u /home/mark/Downloads/jabberd2.init /home/mark/Downloads/jabberd2.init.new
--- /home/mark/Downloads/jabberd2.init	2023-01-11 19:36:24.104716244 +0000
+++ /home/mark/Downloads/jabberd2.init.new	2023-01-11 19:37:12.319574513 +0000
@@ -14,8 +14,8 @@
 set -e
 
 # user and group
-USER=jabber
-GROUP=jabber
+export USER=jabber
+export GROUP=jabber
 test -f /etc/default/jabberd2 && . /etc/default/jabberd2
 
 COMPONENTDPATH=/etc/jabberd2/component.d

Diff finished.  Wed Jan 11 19:38:28 2023

Message received at [email protected]:


Received: (at 721) by bugs.devuan.org; 11 Jan 2023 19:40:36 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 11 Jan 2023 19:40:36 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id EAVKOogQv2NYEQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 11 Jan 2023 19:39:52 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id E0518B85; Wed, 11 Jan 2023 19:39:52 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 9EEAD2A8
	for <[email protected]>; Wed, 11 Jan 2023 19:39:49 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pFgwu-0004It-Fj; Wed, 11 Jan 2023 19:39:48 +0000
Received: (nullmailer pid 2349 invoked by uid 1000);
	Wed, 11 Jan 2023 19:39:48 -0000
Date: Wed, 11 Jan 2023 19:39:48 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Cc: Leonid <[email protected]>
Subject: Re: bug#721: Jabberd2 start failture on devuan
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
 <[email protected]>
 <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
X-Debbugs-No-Ack: No Thanks

Control: tags -1 patch

On Wed, Nov 02, 2022 at 09:24:03AM +0000, Mark Hindley wrote: 
>  - What group is jabber trying to run as? It looks[2] as if it should be
>    jabber. Does the group exist? It should be created in the preinst[3]

I have had a quick look at this and the USER and GROUP environment variables
need to be exported so that they are passed to the scripts in
/etc/jabberd2/component.d.

USER is already an exported variable, so actually works either way, but GROUP
isn't so fails.

Try this.

diff -u /home/mark/Downloads/jabberd2.init /home/mark/Downloads/jabberd2.init.new
--- /home/mark/Downloads/jabberd2.init	2023-01-11 19:36:24.104716244 +0000
+++ /home/mark/Downloads/jabberd2.init.new	2023-01-11 19:37:12.319574513 +0000
@@ -14,8 +14,8 @@
 set -e
 
 # user and group
-USER=jabber
-GROUP=jabber
+export USER=jabber
+export GROUP=jabber
 test -f /etc/default/jabberd2 && . /etc/default/jabberd2
 
 COMPONENTDPATH=/etc/jabberd2/component.d

Diff finished.  Wed Jan 11 19:38:28 2023

Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.

Devuan Bugs Owner <[email protected]>.
Last modified: Wed, 29 Jan 2025 20:39:01 UTC