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 <x2go-dev@lists.x2go.org>.
- Uploaders: add myself. Also, force a rebuild due to the changed
versioning.
_______________________________________________
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev
