[X2Go-Dev] Processed: X2Go issue (in src:x2goclient) has been marked as pending for release

Processing commands for cont...@bugs.x2go.org: > tag #336 pending Bug #336 [x2goclient] Don't allow users to override X2Go commands via ~/bin (or similar) Added tag(s) pending. > fixed #336 4.0.2.1 Bug #336 [x2goclient] Don't allow users to override X2Go commands via ~/bin (or similar) There is

[X2Go-Dev] Bug#336: X2Go issue (in src:x2goclient) has been marked as pending for release

tag #336 pending fixed #336 4.0.2.1 thanks Hello, X2Go issue #336 (src:x2goclient) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=4eb1fd1 The issue will most l

[X2Go-Dev] Processed: X2Go issue (in src:python-x2go) has been marked as pending for release

Processing commands for cont...@bugs.x2go.org: > tag #334 pending Bug #334 [python-x2go] Don't allow users to override X2Go commands via ~/bin (or similar) Added tag(s) pending. > fixed #334 0.5.0.0 Bug #334 [python-x2go] Don't allow users to override X2Go commands via ~/bin (or similar) There i

[X2Go-Dev] Bug#334: X2Go issue (in src:python-x2go) has been marked as pending for release

tag #334 pending fixed #334 0.5.0.0 thanks Hello, X2Go issue #334 (src:python-x2go) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=python-x2go.git;a=commitdiff;h=754bf16 The issue will most

[X2Go-Dev] Bug#468: X2Go issue (in src:x2goserver) has been marked as pending for release

tag #468 pending fixed #468 4.0.1.16 thanks Hello, X2Go issue #468 (src:x2goserver) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=ffa8638 The issue will most

[X2Go-Dev] Processed: X2Go issue (in src:x2goserver) has been marked as pending for release

Processing commands for cont...@bugs.x2go.org: > tag #468 pending Bug #468 [x2goserver] bug reporting about hostname error [x2golistsessions] Added tag(s) pending. > fixed #468 4.0.1.16 Bug #468 [x2goserver] bug reporting about hostname error [x2golistsessions] There is no source info for the pack

[X2Go-Dev] Processed: your mail

Processing commands for cont...@bugs.x2go.org: > reassign #429 packages.x2go.org Bug #429 {Done: Mike Gabriel } [x2goserver] x2goserver: x2goserever fails to upgrade. Bug reassigned from package 'x2goserver' to 'packages.x2go.org'. No longer marked as found in versions 4.1.0.0-0x2go1+git20140128

[X2Go-Dev] Processed: Scanning for duplicated of #302 (please test)

Processing control commands: > reassign #263 x2goserver Bug #263 [x2goserver] X2Go Client fails to resume Bug #206 [x2goserver] When a user ends pyhoca-gui, the session cannot be resumed Bug #302 [x2goserver] No session resume Ignoring request to reassign bug #263 to the same package Ignoring requ

[X2Go-Dev] Processed: Scanning for duplicated of #302 (please test)

Processing control commands: > reassign #263 x2goserver Bug #263 [x2goclient] X2Go Client fails to resume Bug reassigned from package 'x2goclient' to 'x2goserver'. Ignoring request to alter found versions of bug #263 to the same values previously set Ignoring request to alter fixed versions of bu

[X2Go-Dev] Processed: Scanning for duplicated of #302 (please test)

Processing control commands: > reassign #263 x2goserver Bug #263 [x2goserver] X2Go Client fails to resume Bug #206 [x2goserver] When a user ends pyhoca-gui, the session cannot be resumed Bug #302 [x2goserver] No session resume Ignoring request to reassign bug #263 to the same package Ignoring requ

[X2Go-Dev] Bug#302: Scanning for duplicated of #302 (please test)

Control: reassign #263 x2goserver Control: reassign #206 x2goserver Control: merge #263 -1 Control: merge #206 -1 From studying our bug tracker reports, I assume that #206 and #263 are duplicates of #302 which got closed yesterday. @Borys, and other potential testers: can you please check wha

[X2Go-Dev] Processed: Dev packages for X2Go Server "sneaked" themselves into the Baikal LTS package archive

Processing control commands: > close -1 Bug #429 {Done: Mike Gabriel } [x2goserver] x2goserver: x2goserever fails to upgrade. Bug 429 is already marked as done; not doing anything. -- 429: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=429 X2Go Bug Tracking System Contact ow...@bugs.x2go.org wi

[X2Go-Dev] Processed: Dev packages for X2Go Server "sneaked" themselves into the Baikal LTS package archive

Processing control commands: > close -1 Bug #429 [x2goserver] x2goserver: x2goserever fails to upgrade. Marked Bug as done -- 429: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=429 X2Go Bug Tracking System Contact ow...@bugs.x2go.org with problems ___

[X2Go-Dev] Bug#429: Dev packages for X2Go Server "sneaked" themselves into the Baikal LTS package archive

Control: close -1 Hi all, I have just stumbled over a very severe flaw in our X2Go package archive for Debian [1]. A development snapshot of X2Go Server (4.1.0.0-preview) got uploaded to the Baikal LTS area. That is a very very severe problem to people who run the long-term supported v

[X2Go-Dev] Processed: Issue should be resolved since x2goserver 4.0.1.10

Processing control commands: > close -1 Bug #353 {Done: Mike Gabriel } [x2goserver] Subsequent attempts to resume a fullscreen linux session fails Bug 353 is already marked as done; not doing anything. -- 353: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=353 X2Go Bug Tracking System Contact o

[X2Go-Dev] Processed: Issue should be resolved since x2goserver 4.0.1.10

Processing control commands: > close -1 Bug #353 [x2goserver] Subsequent attempts to resume a fullscreen linux session fails Marked Bug as done -- 353: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=353 X2Go Bug Tracking System Contact ow...@bugs.x2go.org with problems _

[X2Go-Dev] Bug#353: Issue should be resolved since x2goserver 4.0.1.10

Control: close -1 The issue reported as bug #353 should have been resolved in X2Go Server 4.0.1.10. Unfortunately, I forgot to close this bug with the fixing commit [1]. Thanks, Mike [1] http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=14900d5 -- DAS-NETZWERKTEAM mike gabriel, h