From unknown Fri Mar 29 07:06:44 2024 X-Loop: owner@bugs.x2go.org Subject: Bug#1016: X2Go issue (in src:python-x2go) has been marked as closed Reply-To: X2Go Release Manager , 1016@bugs.x2go.org Resent-From: X2Go Release Manager Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Mon, 15 May 2017 14:40:02 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 1016 X-X2Go-PR-Package: python-x2go X-X2Go-PR-Keywords: pending Received: via spool by 1016-submit@bugs.x2go.org id=B1016.149485919215053 (code B ref 1016); Mon, 15 May 2017 14:40:02 +0000 Received: (at 1016) by bugs.x2go.org; 15 May 2017 14:39:52 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=-2.9 required=3.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.1 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 68D8E5DAD1; Mon, 15 May 2017 16:39:43 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de Received: from ymir.das-netzwerkteam.de ([127.0.0.1]) by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66VxgjlX1gJR; Mon, 15 May 2017 16:39:35 +0200 (CEST) Received: by ymir.das-netzwerkteam.de (Postfix, from userid 1005) id BBC5F5DAD2; Mon, 15 May 2017 16:39:35 +0200 (CEST) From: X2Go Release Manager To: 1016-submitter@bugs.x2go.org Cc: control@bugs.x2go.org, 1016@bugs.x2go.org Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Message-Id: <20170515143935.BBC5F5DAD2@ymir.das-netzwerkteam.de> Date: Mon, 15 May 2017 16:39:35 +0200 (CEST) close #1016 thanks Hello, we are very hopeful that X2Go issue #1016 reported by you has been resolved in the new release (0.5.0.5) of the X2Go source project »src:python-x2go«. You can view the complete changelog entry of src:python-x2go (0.5.0.5) below, and you can use the following link to view all the code changes between this and the last release of src:python-x2go. http://code.x2go.org/gitweb?p=python-x2go.git;a=commitdiff;h=64c77967e7ae4ec038549eb19fef5c6fc5b525af;hp=59e42be74d34033dfd259bcfc54a84399893c44b 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:python-x2go. Thanks a lot for contributing to X2Go!!! light+love X2Go Git Admin (on behalf of the sender of this mail) --- X2Go Component: src:python-x2go Version: 0.5.0.5-0x2go1 Status: RELEASE Date: Mon, 15 May 2017 16:38:16 +0200 Fixes: 1016 Changes: python-x2go (0.5.0.5-0x2go1) RELEASED; urgency=low . [ Mike Gabriel ] * New upstream version (0.5.0.5): - documentation: Fix wording in docstring. - Don't blindly release gevent locks. We need to check if a semaphore is locked for some code paths and only then release it. (Fixes: #1016). . [ Mihai Moldovan ] * New upstream version (0.5.0.5): - x2go/__init__.py: update mailing list address. * debian/control: - Maintainer change in package: X2Go Developers . - Uploaders: add myself. Also, force a rebuild due to the changed versioning.