From unknown Tue May 19 11:42:29 2026
MIME-Version: 1.0
X-Mailer: MIME-tools 5.502 (Entity 5.502)
X-Loop: owner@bugs.x2go.org
From: owner@bugs.x2go.org (X2Go Bug Tracking System)
Subject: Bug#171 closed by tag@ymir, 0.0.1.1@ymir (X2Go issue #171
 (src:x2gobroker) has been marked as closed)
Message-ID: <handler.171.c.13667470378555.notifdone@bugs.x2go.org>
References: <20130423195621.A24F55DB27@ymir>
X-X2go-PR-Keywords: pending
X-X2go-PR-Message: they-closed 171
X-X2go-PR-Package: x2gobroker-authservice
X-X2go-PR-Source: x2gobroker
Date: Tue, 23 Apr 2013 19:57:38 +0000
Content-Type: multipart/mixed; boundary="----------=_1366747058-8670-0"

This is a multi-part message in MIME format...

------------=_1366747058-8670-0
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8

This is an automatic notification regarding your Bug report
which was filed against the x2gobroker-authservice package:

#171: x2gobroker-authservice does not create needed user/group

It has been closed by tag@ymir, 0.0.1.1@ymir.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact tag@ymir, 0.0.1.1@ymir=
 by
replying to this email.


--=20
X2Go Bug Tracking System
Contact owner@bugs.x2go.org with problems

------------=_1366747058-8670-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at control) by bugs.x2go.org; 23 Apr 2013 19:57:17 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=FH_FROMEML_NOTLD,NO_RELAYS,
	URIBL_BLOCKED autolearn=no version=3.3.2
Received: by ymir (Postfix, from userid 1005)
	id A24F55DB27; Tue, 23 Apr 2013 21:56:21 +0200 (CEST)
From: tag@ymir, 0.0.1.1@ymir
To: 171-submitter@bugs.x2go.org
Cc: control@bugs.x2go.org, 171@bugs.x2go.org
Subject: X2Go issue #171 (src:x2gobroker) has been marked as closed
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Message-Id: <20130423195621.A24F55DB27@ymir>
Date: Tue, 23 Apr 2013 21:56:21 +0200 (CEST)

close #171
thanks

Hello,

we are very hopeful that X2Go issue #171 reported by you
has been resolved in the new release (0.0.1.1) of the
X2Go source project »src:x2gobroker«.

You can view the complete changelog entry of src:x2gobroker (0.0.1.1)
below, and you can use the following link to view all the code changes
between this and the last release of src:x2gobroker.

    http://code.x2go.org/gitweb?p=x2gobroker.git;a=commitdiff;h=4085176be6f5895c931e34e6549ea9849e13ca0b;hp=7a77058f345af93356c9615df70c92644fa98549

If you feel that the issue has not been resolved satisfyingly, feel
free to reopen this bug report or submit a follow-up report with
further observations described based on the new released version
of src:x2gobroker.

Thanks a lot for contributing to X2Go!!!

light+love
X2Go Git Admin (on behalf of sender of this mail)

---
X2Go Component: src:x2gobroker
Version: 0.0.1.1
Status: RELEASE
Date: Tue, 23 Apr 2013 21:38:07 +0200
Fixes: 154 170 171 172 175 176 180
Changes: 
 x2gobroker (0.0.1.1) RELEASED; urgency=low
 .
   * New upstream version (0.0.1.1):
     - Add WSGI support to X2Go Session Broker. Allows plugging into
       Apache2 by using the mod_wsgi module.
     - Add Apache2 configuration for WSGI support that shows how to
       setup a VirtualHost for X2Go Session Broker.
     - For sessions profiles with autologin enable, add a dummy key
       session profile parameter that triggers key based auth in X2Go Client.
       (Fixes: #154).
     - Fix hard-coded path to x2gobroker's authservice socket.
     - Separate logging logic of x2gobroker-authservice from the rest of
       the logging in x2gobroker. (Fixes: #172).
     - x2gobroker-pubkeyauthorizer: no logging-to-file support anymore.
       (Fixes: #175).
     - Fix name of get() method for /pubkeys/ URL path. (Fixes: #176).
     - Move AuthService server code fully into x2gobroker-authservice
       daemon script.
     - Add forgotten file: x2gobroker-authservice-logger.conf. (Fixes: #180).
     - Add script: x2gobroker-testauth.
     - Add enable()/disable() methods to broker backends.
     - Move complete authservice logic into x2gobroker-authservice script.
     - Add command and directrdp session profile parameters to defaults.
     - Fix wrong usage of session option »cmd«, has to be »command«.
   * /debian/control:
     + Fix --root parameter in DEB_PYTHON_INSTALL_ARGS.
     + Let bin:package x2gobroker-authservice depend on python-x2gobroker (of the
       same version). (Fixes: #170).
   * Properly remove the X2Go Session broker log files on package purgal.
   * Let bin:package x2gobroker-authservice create x2gouser:x2gouser, as well.
     (Fixes: #171).


------------=_1366747058-8670-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at submit) by bugs.x2go.org; 17 Apr 2013 12:51:59 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=HTML_MESSAGE,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2
Received: from eu1sys200aog104.obsmtp.com (eu1sys200aog104.obsmtp.com [207.126.144.117])
	by ymir (Postfix) with SMTP id 67A845DB05
	for <submit@bugs.x2go.org>; Wed, 17 Apr 2013 14:51:58 +0200 (CEST)
Received: from mail-oa0-f72.google.com ([209.85.219.72]) (using TLSv1) by eu1sys200aob104.postini.com ([207.126.147.11]) with SMTP
	ID DSNKUW6a7jyhcNbSXznsNK5WutGH0ZZ+v/gL@postini.com; Wed, 17 Apr 2013 12:51:58 UTC
Received: by mail-oa0-f72.google.com with SMTP id j6so10113265oag.3
        for <submit@bugs.x2go.org>; Wed, 17 Apr 2013 05:51:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=dsl.dk; s=google;
        h=x-received:mime-version:x-received:date:message-id:subject:from:to
         :content-type;
        bh=EseKkDVUdCeQC7QETRb8z6Hdjbp4miQ9foGE3+7C2ZE=;
        b=azkg6ujUKFASTnLpY2Jht3OyPWccPx2Lra72ffeZfeVQe4N4U0OYBjAEfp7QtcVUeJ
         Bavl5vSkvkGT9ZnxhrwU+oKzkh8sVfAlG/kK1fAV2+P/Zi6UouZIwQrip9vwGWgw335z
         JxN8uoPgIkxA0hx0dstuIWbQ8rb7iuavBYcz0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=x-received:mime-version:x-received:date:message-id:subject:from:to
         :content-type:x-gm-message-state;
        bh=EseKkDVUdCeQC7QETRb8z6Hdjbp4miQ9foGE3+7C2ZE=;
        b=b9qReeEcwmLcxnd5vdKKwIrDGQFT+N783mAj86dNk1kP+YLh1aNqcgAfXzhcQ4RlBZ
         dBT6fe37Dz/otZT71ZFxN9z6X4So4C+veug0/rRx3lUzzYLB9a6CfniPkz8UQpsyMqbj
         7PL9HUEBj4ByhHvsmnudNvdMmkeypHlYYp2+N2pB9NMTGQnjAA85sGh/+07nKVf+wbbF
         /WGS6m8+ZA4EFtuy8bvFtH/HS+etE4AtM/sM+NF6WfVKhu2sveOaLu87HJyddrPMHa+J
         93nVsiN3BPm2FHid4Trx3NYt/UfS1JdVMhsbbbi5/D26lRKXBxHsdcHv1jTXha36wavh
         iKzw==
X-Received: by 10.60.133.197 with SMTP id pe5mr2572847oeb.21.1366202625719;
        Wed, 17 Apr 2013 05:43:45 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.133.197 with SMTP id pe5mr2572835oeb.21.1366202625330;
 Wed, 17 Apr 2013 05:43:45 -0700 (PDT)
Received: by 10.182.87.200 with HTTP; Wed, 17 Apr 2013 05:43:45 -0700 (PDT)
Date: Wed, 17 Apr 2013 14:43:45 +0200
Message-ID: <CAFJm-UOobyHH5txHCeBmsEq0ka8SwoD4w-iEnBv-pE7CPF7LMQ@mail.gmail.com>
Subject: x2gobroker-authservice does not create needed user/group
From: Anders Bruun Olsen <abo@dsl.dk>
To: submit@bugs.x2go.org
Content-Type: multipart/alternative; boundary=047d7b4722cc2d4b7504da8dd693
X-Gm-Message-State: ALoCoQnedK5YQpAH3oiW8hs2yGvVTlX+gPyZ/TKdgHVR5bI9swOw0dAlNlbPZKzULGCsynHKYrwNUjwltGpmSbp+nP1rb9oSHwy9ZSdk4UEEyoTUDPE27VRV1Ltmp+9oennHisBFuhk2s6JPcsD3RIyt+gWvqhXVtA==

--047d7b4722cc2d4b7504da8dd693
Content-Type: text/plain; charset=UTF-8

Package: x2gobroker-authservice
Version: 0.0.1.0-0~334~precise1

While researching why a newly installed x2gobroker-daemon would not start,
I found out that x2gobroker-authservice expects there to be a user and a
group called x2gobroker. It does not create these itself, and thus won't
start at all if installed without x2gobroker-daemon. Either the
x2gobroker-authservice packages should create the needed users (if
neccessary) or it should depend upon x2gobroker-daemon, which will then
handle it.

-- 
Anders Bruun Olsen
It-ansvarlig
Det Danske Sprog- og Litteraturselskab
(Society for Danish Language and Literature)

--047d7b4722cc2d4b7504da8dd693
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Package: x2gobroker-authservice<div>Version:=C2=A00.0.1.0-=
0~334~precise1</div><div><br></div><div>While researching why a newly insta=
lled x2gobroker-daemon would not start, I found out that x2gobroker-authser=
vice expects there to be a user and a group called x2gobroker. It does not =
create these itself, and thus won&#39;t start at all if installed without x=
2gobroker-daemon. Either the x2gobroker-authservice packages should create =
the needed users (if neccessary) or it should depend upon x2gobroker-daemon=
, which will then handle it.<br clear=3D"all">
<div><br></div>-- <br>Anders Bruun Olsen<br>It-ansvarlig<br>Det Danske Spro=
g- og Litteraturselskab<br>(Society for Danish Language and Literature)<br>
</div></div>

--047d7b4722cc2d4b7504da8dd693--

------------=_1366747058-8670-0--
