Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Package: wnpp Version: N/A; reported 2012-01-06 Severity: wishlist * Package name : nx-libs Version : 3.5.0.3 Upstream Author : Mike Gabriel, Oleksandr Shneyder, Reinhard Tartler * URL : wiki.x2go.org * License : GPLv2 Description : NX protocol libraries and binaries NX is a software suite which implements very efficient compression of the X11 protocol. This increases performance when using X applications over a network, especially a slow one. The X2Go upstream team has started to provide ,,NX (redistributed)'' -- a redistribution of NX code originally provided by NoMachine. The X2Go upstream team has reviewed many patches from different sources and ships them with ,,NX (redistributed)''. X2Go upstream offers two tarball variants of ,,NX (redistributed)'': - LITE: nx-libs_-lite.tar.gz (NX client-only support) - FULL: nxlibs_-full.tar.gz (full NX client and server support) The X2Go upstream team has also made an effort on applying X2Go specific patches that allow to turn an unbranded NX agent (aka nxagent, stripped off !M logo from session startup splash, as done by the FreeNX team on Launchpad) into an X2Go branded (splash screen) agent (aka x2goagent). The name of the binary decides on the flavour (FreeNX or X2Go) the agent runs as. Due to the X2Go-specific patches, the latest ,,NX (redistributed)'' tarball provided by X2Go upstream works with FreeNX and X2Go. The X2Go upstream team has decided to actively provide source code maintenance of the original NX coded downloaded from NoMachine as a redistributor. This aims at providing higher downstream-responsive patch cycles compared to the past (with NoMachine as NX upstream). Patches applied to ,,NX (redistributed)'' also get reported to NoMachine (by the X2Go upstream team). Patches that find their way into original NoMachine release will be removed from the ,,NX (redist.)'' patch stack, once a new NoMachine tarball release has been tested and incorporated into ,,NX (redist)''. The first package upload of nx-libs to Debian unstable is planned to only provide nx-libs_-lite.tar.gz (the LITE variante of NX redist.) and update NX client support in Debian. This will be required for closing the following ITPs: x2goclient (#655602) python-x2go (#655608) pyhoca-gui (#655603) pyhoca-cli (#655607) The upload of nx-libs will replace to existing source packages and close open bugs: - nxcomp (3.2.0-7-1.1), closing #627803 - nxproxy (3.2.0-1-1), closing #637443 The maintenance of those packages will from then on be provided by the X2Go Packaging Team on Alioth (pkg-x2go-de...@lists.alioth.debian.org). Thanks to Mathew Johnson who agreed on handing the packages over to our team and also thanks for providing former versions of those packages during the last years!!! For some future upload the X2Go Packaging Team plans to switch over to providing the full ,,NX (redistributed)'' code base, including - nxcomp - nxcompext - nxcompshad - nx-X11 - nxagent - x2goagent - nxauth - nx-X11 This will close the ITP for X2Go Server: - x2go (#465821) The packaing of the full NX (redist) code base would also allow for FreeNX to finally be packaged for Debian (if developers of FreeNX have an interest on that). Contacts: X2Go Packagin Team: pkg-x2go-de...@lists.alioth.debian.org X2Go upstream developers: x2go-...@lists.berlios.de FreeNX developers: freenx-t...@lists.launchpad.net NX (redist) aka nx-libgs.git on: http://git.x2go.org http://code.x2go.org/gitweb?p=nx-libs.git;a=summary - full code base -> master branch - lite/client-only code base -> client-only branch -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpue7JSWpOaV.pgp Description: Digitale PGP-Unterschrift
Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Hi On Friday 13 January 2012, Mike Gabriel wrote: > Package: wnpp > Version: N/A; reported 2012-01-06 > Severity: wishlist > > * Package name : nx-libs >Version : 3.5.0.3 >Upstream Author : Mike Gabriel, Oleksandr Shneyder, Reinhard Tartler > * URL : wiki.x2go.org > * License : GPLv2 >Description : NX protocol libraries and binaries [...] >NX (redist) aka nx-libgs.git on: http://git.x2go.org >http://code.x2go.org/gitweb?p=nx-libs.git;a=summary >- full code base -> master branch >- lite/client-only code base -> client-only branch This appears to still contain a full (according to its size and a short look at your packaging git), forked monolithic X.org 6.9 source tree. Most likely with little to no bug-/ security fixes since 2005 - or am I missing anything vital in that packaging git? Likewise the current debian/copyright appears to lack all copyright notices of the original XFree86/ X.org code, which makes up, by far, most of the source. What are the plans for its future maintenance, given that NoMachine NX4 appears to switch to a closed source development model and is likely to abandon the NX 3.5 code base rather soon? In a similar fashion FreeNX appears to be dead upstream since November 2008 (and already was dead way before that). Wouldn't it make more sense to concentrate on filling the gaps to re-use something like Red Hat's SPICE protocol for remote desktop uses? Regards Stefan Lippers-Hollmann Disclaimer: I've had my bite with trying to package early NX 1.x, NX 2.x versions intended for Debian, but the sheer amount of forked upstream code (in particular nx-x11) and, back then, nxssh, samba, rdesktop, esound made those attempts appear to be an endeavour in futility. However I didn't actually follow development in this arena since the early NX 3 era. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201201130037.59101.s@gmx.de
Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Hi Stefan, I am discussing here being in a double role. I am part of X2Go upstream, redistributing the nx-libs tarballs and also member of the Debian X2Go packaging team. On Fr 13 Jan 2012 00:37:57 CET Stefan Lippers-Hollmann wrote: Hi On Friday 13 January 2012, Mike Gabriel wrote: Package: wnpp Version: N/A; reported 2012-01-06 Severity: wishlist * Package name : nx-libs Version : 3.5.0.3 Upstream Author : Mike Gabriel, Oleksandr Shneyder, Reinhard Tartler * URL : wiki.x2go.org * License : GPLv2 Description : NX protocol libraries and binaries [...] NX (redist) aka nx-libgs.git on: http://git.x2go.org http://code.x2go.org/gitweb?p=nx-libs.git;a=summary - full code base -> master branch - lite/client-only code base -> client-only branch This appears to still contain a full (according to its size and a short look at your packaging git), The packaging Git is on Alioth: http://anonscm.debian.org/gitweb/?p=collab-maint/x2go/nx-libs.git;a=summary Do you refer to that one? The redistributor's Git of NX (redistributed) is on X2Go Git: http://code.x2go.org/gitweb?p=nx-libs.git;a=summary forked monolithic X.org 6.9 source tree. This is indeed the case. Most likely with little to no bug-/ security fixes since 2005 - or am I missing anything vital in that packaging git? Likewise the current debian/copyright appears to lack all copyright notices of the original XFree86/ X.org code, which makes up, by far, most of the source. The X2Go upstream team will be open to security and feature patches and will love to be pointed at security issues discovered. In the very very very long run there might be someone (we are currently talking about people in Austria being interested in such a project) who refactors NX for latest Xorg code, but currently what we can provide is an active maintenance of NoMachine's code. And: NoMachine has lately released several tarballs around NX, please refer to http://www.nomachine.com/sources.php or check out the separate tarball import branches on nx-libs.git on X2Go Git. What are the plans for its future maintenance, given that NoMachine NX4 appears to switch to a closed source development model and is likely to abandon the NX 3.5 code base rather soon? In a similar fashion FreeNX appears to be dead upstream since November 2008 (and already was dead way before that). We are not packaging for FreeNX. We intend to package NX for usage with X2Go. And X2Go has been continuously active during the last years, esp. during 2011. However, what we took care of is that the way we redistribute latest NX sources does not interfere with FreeNX code and also provides all FreeNX functionalities. One reason for FreeNX becoming less and less active probably was the trouble getting nx-X11 into Debian. The placing of a redistributor between Linux distros and the original tarball provider NoMachine (who has not proved to be active on incorporating patches) aims at becoming more flexible and open to contributions here. Wouldn't it make more sense to concentrate on filling the gaps to re-use something like Red Hat's SPICE protocol for remote desktop uses? No, performance tests fail for us compared to NX. All technologies around apart from NX use capturing algorithms and they scale quite badly on low-bandwidth networks. Regards Stefan Lippers-Hollmann Disclaimer: I've had my bite with trying to package early NX 1.x, NX 2.x versions intended for Debian, but the sheer amount of forked upstream code (in particular nx-x11) and, back then, nxssh, samba, rdesktop, esound made those attempts appear to be an endeavour in futility. However I didn't actually follow development in this arena since the early NX 3 era. Things are moving so may I invite to take another look? Thanks for your open and honest feedback. Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpXV7yZrqCUk.pgp Description: Digitale PGP-Unterschrift
Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
On Fri, Jan 13, 2012 at 12:57:37AM +0100, Mike Gabriel wrote: > On Fr 13 Jan 2012 00:37:57 CET Stefan Lippers-Hollmann wrote: > >forked monolithic X.org 6.9 source tree. > > This is indeed the case. I can't speak for the ftpmasters and Security Team, but honestly I can't see why they would allow this in the archive or in any stable release, respectively. > >Most likely with little to no bug-/ security fixes since 2005 - or am > >I missing anything vital in that packaging git? Likewise the current > >debian/copyright appears to lack all copyright notices of the original > >XFree86/ X.org code, which makes up, by far, most of the source. > > The X2Go upstream team will be open to security and feature patches > and will love to be pointed at security issues discovered. In the > very very very long run there might be someone (we are currently > talking about people in Austria being interested in such a project) > who refactors NX for latest Xorg code, but currently what we can > provide is an active maintenance of NoMachine's code. I think you're missing the issue here. Since X.org 6.9, there's been a lot of bug fixes and improved code. So you're essentially using an obsolete codebase with a new protocol hacked on. The Security Team does not like code copies. Porters do not like patching the same software again and again, except with slight differences that make it impossible to reuse the same patches[0]. The Debian X Strike Force has lots of bugs that need to be dealt with, very likely because of a lack of time and manpower[1]. If your code is a fork of 6.9, then all those bugs that were dealt with previously (or are still present) are probably present in your code. Also, even though X2Go may provide security support for nx-libs, the Debian Security Team still has to issue DSAs and build packages on all of the release architectures independent of X2Go. [0] I have had the joy of assisting the kFreeBSD porters with patching every embedded and modified copy of libgc. [1] This is not a dig at the X Strike Force; they do a very good job with package maintenance and bug handling with the manpower they have. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
On 01/13/2012 11:04 AM, brian m. carlson wrote: > On Fri, Jan 13, 2012 at 12:57:37AM +0100, Mike Gabriel wrote: > >> On Fr 13 Jan 2012 00:37:57 CET Stefan Lippers-Hollmann wrote: >> >>> forked monolithic X.org 6.9 source tree. >>> >> This is indeed the case. >> > I can't speak for the ftpmasters and Security Team, but honestly I can't > see why they would allow this in the archive or in any stable release, > respectively. > I agree it wouldn't be a fit for SID or a release (considering what has been written in this thread earlier). But would you think it'd be acceptable to upload it in Experimental then? Thomas -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f0fc3dd.4010...@debian.org
Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Hi Brianm, On Fr 13 Jan 2012 04:04:38 CET "brian m. carlson" wrote: On Fri, Jan 13, 2012 at 12:57:37AM +0100, Mike Gabriel wrote: On Fr 13 Jan 2012 00:37:57 CET Stefan Lippers-Hollmann wrote: >forked monolithic X.org 6.9 source tree. This is indeed the case. I can't speak for the ftpmasters and Security Team, but honestly I can't see why they would allow this in the archive or in any stable release, respectively. >Most likely with little to no bug-/ security fixes since 2005 - or am >I missing anything vital in that packaging git? Likewise the current >debian/copyright appears to lack all copyright notices of the original >XFree86/ X.org code, which makes up, by far, most of the source. The X2Go upstream team will be open to security and feature patches and will love to be pointed at security issues discovered. In the very very very long run there might be someone (we are currently talking about people in Austria being interested in such a project) who refactors NX for latest Xorg code, but currently what we can provide is an active maintenance of NoMachine's code. I think you're missing the issue here. Since X.org 6.9, there's been a lot of bug fixes and improved code. So you're essentially using an obsolete codebase with a new protocol hacked on. The Security Team does not like code copies. Porters do not like patching the same software again and again, except with slight differences that make it impossible to reuse the same patches[0]. Thanks for pointing that out more explicitly. I have been basically aware of this but probably not to its full extent. And still, my basic (inner and outer) question is: 1. how can we enrol other people with our endeavour 2. what is needed to enrol people 3. is there anyonr in this discussion who can point us to next possible steps towards acceptance of the packages I see a great use case for having a low-bandwidth, high-latency remote desktop solution in Debian and the X2Go people are really willing to make an effort to make X2Go server inclusion in Debian happen. BTW: I got personal feedback from Marcelo Boveto Shima, FreeNX. The project has become silent, though not dead (as Stefan stated). I asked him to contribute to this thread... Thanks, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpk1JqnwITwW.pgp Description: Digitale PGP-Unterschrift
Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
brian m. carlson schrieb am Friday, den 13. January 2012: > On Fri, Jan 13, 2012 at 12:57:37AM +0100, Mike Gabriel wrote: > > On Fr 13 Jan 2012 00:37:57 CET Stefan Lippers-Hollmann wrote: > > >forked monolithic X.org 6.9 source tree. > > > > This is indeed the case. > > I can't speak for the ftpmasters and Security Team, but honestly I can't > see why they would allow this in the archive or in any stable release, > respectively. Indeed, we had this discussions a few years ago where I started the NX packaging group. NX in its current state with the embedded code copys won't be accepted by ftpmasters. That was stated clearly. Alex -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120113075517.gd4...@smithers.snow-crash.org
Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Hi all, On Fr 13 Jan 2012 06:40:45 CET Thomas Goirand wrote: On 01/13/2012 11:04 AM, brian m. carlson wrote: On Fri, Jan 13, 2012 at 12:57:37AM +0100, Mike Gabriel wrote: On Fr 13 Jan 2012 00:37:57 CET Stefan Lippers-Hollmann wrote: forked monolithic X.org 6.9 source tree. This is indeed the case. I can't speak for the ftpmasters and Security Team, but honestly I can't see why they would allow this in the archive or in any stable release, respectively. I agree it wouldn't be a fit for SID or a release (considering what has been written in this thread earlier). But would you think it'd be acceptable to upload it in Experimental then? Thomas Please note that we are implicitly discussing two code bases here... STEP 1: For SID and also a later stable wheezy we would love to upload nx-libs (LITE). This will update packages already in Debian. Nothing more. STEP X: What people in this thread have been contributed to is the handling of nx-libs (FULL). Of course many people would love to see nx-libs (FULL) in Debian and any derived distro, but I understand all your concerns and I know such a discussion would come up here and I am really seeking for a new approach here. Experimental upload would be one, maybe. Thanks, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpJB6qAYlKxG.pgp Description: Digitale PGP-Unterschrift
Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Hi Alex, On Fr 13 Jan 2012 08:55:17 CET Alexander Wirt wrote: brian m. carlson schrieb am Friday, den 13. January 2012: On Fri, Jan 13, 2012 at 12:57:37AM +0100, Mike Gabriel wrote: > On Fr 13 Jan 2012 00:37:57 CET Stefan Lippers-Hollmann wrote: > >forked monolithic X.org 6.9 source tree. > > This is indeed the case. I can't speak for the ftpmasters and Security Team, but honestly I can't see why they would allow this in the archive or in any stable release, respectively. Indeed, we had this discussions a few years ago where I started the NX packaging group. NX in its current state with the embedded code copys won't be accepted by ftpmasters. That was stated clearly. Alex Is that the code in nx-X11/extras? Or the full nx-X11 tree? Note that we have tested loads of different build variants against Xorg 7. The highest stability (which is virtually no session crashes anymore) we ever achieved is by the way we currently build the code as one monolith. Thanks, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgp7eItcXr9Yb.pgp Description: Digitale PGP-Unterschrift
Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Mike Gabriel schrieb am Freitag, den 13. Januar 2012: > Hi Alex, > > On Fr 13 Jan 2012 08:55:17 CET Alexander Wirt wrote: > > >brian m. carlson schrieb am Friday, den 13. January 2012: > > > >>On Fri, Jan 13, 2012 at 12:57:37AM +0100, Mike Gabriel wrote: > >>> On Fr 13 Jan 2012 00:37:57 CET Stefan Lippers-Hollmann wrote: > >>> >forked monolithic X.org 6.9 source tree. > >>> > >>> This is indeed the case. > >> > >>I can't speak for the ftpmasters and Security Team, but honestly I can't > >>see why they would allow this in the archive or in any stable release, > >>respectively. > >Indeed, we had this discussions a few years ago where I started the NX > >packaging group. NX in its current state with the embedded code copys won't > >be accepted by ftpmasters. That was stated clearly. > > > >Alex > > Is that the code in nx-X11/extras? Or the full nx-X11 tree? the latter. afair the first didn't existed to that time. > > Note that we have tested loads of different build variants against > Xorg 7. The highest stability (which is virtually no session crashes > anymore) we ever achieved is by the way we currently build the code > as one monolith. This is not about stability. It is about being able to distribute it. ftpmasters already said "no" to nx and I don't think anything changed since then. Alex -- Alexander Wirt, formo...@formorer.de CC99 2DDD D39E 75B0 B0AA B25C D35B BC99 BC7D 020A -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120113090028.ga8...@hawking.credativ.lan
Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Hi Alex, On Fr 13 Jan 2012 10:00:29 CET Alexander Wirt wrote: Note that we have tested loads of different build variants against Xorg 7. The highest stability (which is virtually no session crashes anymore) we ever achieved is by the way we currently build the code as one monolith. This is not about stability. It is about being able to distribute it. ftpmasters already said "no" to nx and I don't think anything changed since then. Yes, got that completely! And: I am searching for a new realm of possiblities here. Somehow some non-Debian binaries made it into Debian (by external download), for example. What new ways can be possible here is my question? Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpiXuSwEnt9u.pgp Description: Digitale PGP-Unterschrift
Bug#655618: [Pkg-x2go-devel] Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
On Fri, 2012-01-13 at 00:37 +0100, Stefan Lippers-Hollmann wrote: > Hi > > On Friday 13 January 2012, Mike Gabriel wrote: > > Package: wnpp > > Version: N/A; reported 2012-01-06 > > Severity: wishlist > > > > * Package name : nx-libs > >Version : 3.5.0.3 > >Upstream Author : Mike Gabriel, Oleksandr Shneyder, Reinhard Tartler > > * URL : wiki.x2go.org > > * License : GPLv2 > >Description : NX protocol libraries and binaries > [...] > >NX (redist) aka nx-libgs.git on: http://git.x2go.org > >http://code.x2go.org/gitweb?p=nx-libs.git;a=summary > >- full code base -> master branch > >- lite/client-only code base -> client-only branch > > This appears to still contain a full (according to its size and a short > look at your packaging git), forked monolithic X.org 6.9 source tree. > Most likely with little to no bug-/ security fixes since 2005 - or am > I missing anything vital in that packaging git? Likewise the current > debian/copyright appears to lack all copyright notices of the original > XFree86/ X.org code, which makes up, by far, most of the source. > > What are the plans for its future maintenance, given that NoMachine NX4 > appears to switch to a closed source development model and is likely to > abandon the NX 3.5 code base rather soon? In a similar fashion FreeNX > appears to be dead upstream since November 2008 (and already was dead > way before that). > > Wouldn't it make more sense to concentrate on filling the gaps to > re-use something like Red Hat's SPICE protocol for remote desktop uses? I am very concerned about the old X code, too and we are actively watching SPICE. SPICE has extraordinary potential but it is still slower than NX on WAN links - not much but enough to make a user noticeable difference. As SPICE improves, I think we should consider it seriously. Its cross platform support is very good which would no longer limit X2Go server to Windows only and the idea of an adaptive protocol is absolutely intriguing. I long for the day we can realistically do video playing on the virtual desktop across a WAN. Thanks - John -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1326417742.31393.305.ca...@denise.theartistscloset.com
Bug#655618: [Pkg-x2go-devel] Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Op 13-01-12 02:22, John A. Sullivan III schreef: > As SPICE improves, I think we should consider it > seriously. Its cross platform support is very good which would no > longer limit X2Go server to Windows only and the idea of an adaptive > protocol is absolutely intriguing. I long for the day we can > realistically do video playing on the virtual desktop across a WAN. X2go-server is not Windows-only, it even does not run on Windows. Not sure what you want to say. With regards, Paul. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f0feb91.8030...@vandervlis.nl
Bug#655618: [Pkg-x2go-devel] Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Hi Paul, hi John, On Fr 13 Jan 2012 09:30:09 CET Paul van der Vlis wrote: Op 13-01-12 02:22, John A. Sullivan III schreef: As SPICE improves, I think we should consider it seriously. Its cross platform support is very good which would no longer limit X2Go server to Windows only and the idea of an adaptive protocol is absolutely intriguing. I long for the day we can realistically do video playing on the virtual desktop across a WAN. X2go-server is not Windows-only, it even does not run on Windows. Not sure what you want to say. Note: we tend to get off-topic here. This thread is about packaging X2Go server / NX-libs for Debian. Please note by the To:/Cc: field, how many lists/people are involved in this discussion. Let us discuss X2Go (upstream) issues on x2go-...@lists.berlios.de and open a new thread on this topic there if you feel like it. Thanks, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpP20gFyVQHI.pgp Description: Digitale PGP-Unterschrift
Bug#655618: [Pkg-x2go-devel] Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
clone 655618 -1 retitle 655618 ITP: nx-libs-light --- NX Protocol client-only libraries and binaries retitle -1 ITP: nx-libs --- NX Protocol client/server libraries and binaries stop On Fr, Jan 13, 2012 at 10:20:15 (CET), Mike Gabriel wrote: > Hi Paul, hi John, > > On Fr 13 Jan 2012 09:30:09 CET Paul van der Vlis wrote: > >> Op 13-01-12 02:22, John A. Sullivan III schreef: >> >>> As SPICE improves, I think we should consider it >>> seriously. Its cross platform support is very good which would no >>> longer limit X2Go server to Windows only and the idea of an adaptive >>> protocol is absolutely intriguing. I long for the day we can >>> realistically do video playing on the virtual desktop across a WAN. >> >> X2go-server is not Windows-only, it even does not run on Windows. >> Not sure what you want to say. > > Note: we tend to get off-topic here. This thread is about packaging > X2Go server / NX-libs for Debian. Please note by the To:/Cc: field, how > many lists/people are involved in this discussion. I think the recipient list is appropriate. It includes everyone that should discuss the inclusion of this software into the Debian Archive. As some people raised concerns about including the x2go server into Debian, I'm there splitting this ITP into two parts, following to the way x2go provides its sources: At http://code.x2go.org/releases/source/nx-libs/ two tarballs of nx-libs are provided: one called 'lite' and one called 'full'. AFAIUI, the 'lite' tarball is a true subset of the 'full' tarball containing only the parts that are relevant for building the client parts of the NX stack. This is what bug #655618 is about from now on. The package is being prepared at http://anonscm.debian.org/gitweb/?p=collab-maint/x2go/nx-libs.git;a=tree and, from what I see, is appropriate for being uploaded to unstable. For clarity, I think we should rename the git repository from nx-libs.git to nx-libs-light.git. Mike, can you please handle that? For further discussion of the server parts (called "agent" in NX lingo), which AFAIUI is a heavily patched fork of the old XNest codebase linked against the Nomachine NX protocol libraries, please use the cloned bug. I agree that without the blessing of the release team the security team, it shouldn't go into unstable (or wheezy), but if the ftp-masters agree, then I think it could go into experimental, so that interested parties can start to have another serious look at it. If the project decides that the server becomes suitable for inclusion into unstable, it will then replace the 'nx-libs-light' package. As I understand from Mike's other posting in this thread, there are people looking at porting the agent to a newer codebase. But this is a rarther long-term option. As are the suggestions to port x2go to SPICE. As for the concerns with Nomachine, while it is true that NX 4.0 is no longer GPL licensed, the 3.x codebase has seen updates, which maintain its previous license, the GPLv3. I take this as indication that Nomachine still has an interest in maintaining the 3.x codebase, which included security fixes in the latest releases. Cheers, Reinhard -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ty3zc2sb@faui43f.informatik.uni-erlangen.de
Processed: Re: [Pkg-x2go-devel] Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Processing commands for cont...@bugs.debian.org: > clone 655618 -1 Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries Bug 655618 cloned as bug 655699. > retitle 655618 ITP: nx-libs-light --- NX Protocol client-only libraries and > binaries Bug #655618 [wnpp] ITP: nx-libs -- NX protocol libraries and binaries Changed Bug title to 'ITP: nx-libs-light --- NX Protocol client-only libraries and binaries' from 'ITP: nx-libs -- NX protocol libraries and binaries' > retitle -1 ITP: nx-libs --- NX Protocol client/server libraries and binaries Bug #655699 [wnpp] ITP: nx-libs -- NX protocol libraries and binaries Changed Bug title to 'ITP: nx-libs --- NX Protocol client/server libraries and binaries' from 'ITP: nx-libs -- NX protocol libraries and binaries' > stop Stopping processing here. Please contact me if you need assistance. -- 655699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655699 655618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655618 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132645068131830.transcr...@bugs.debian.org
Bug#655618: [Pkg-x2go-devel] Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Hi Reinhard, dear all, On Fr 13 Jan 2012 11:31:00 CET Reinhard Tartler wrote: http://anonscm.debian.org/gitweb/?p=collab-maint/x2go/nx-libs.git;a=tree and, from what I see, is appropriate for being uploaded to unstable. For clarity, I think we should rename the git repository from nx-libs.git to nx-libs-light.git. Mike, can you please handle that? Renamed! http://anonscm.debian.org/gitweb/?p=collab-maint/x2go/nx-libs-lite.git;a=tree As I understand from Mike's other posting in this thread, there are people looking at porting the agent to a newer codebase. But this is a rarther long-term option. As are the suggestions to port x2go to SPICE. Yes, we have still a casual but a discussion with an Austrian company that is heavily interested to provide some new NX'ish or similar technology. Very casual still, but yes. As for the concerns with Nomachine, while it is true that NX 4.0 is no longer GPL licensed, the 3.x codebase has seen updates, which maintain its previous license, the GPLv3. I take this as indication that Nomachine still has an interest in maintaining the 3.x codebase, which included security fixes in the latest releases. I have also had NoMachine contact before X-mas 2011 and they said that they would take a look at our patches. I have to update them about the location changes as they got informed about the Alioth Git. I will point then to X2Go Git now. We (i.e. Alex from X2GO) also have just added a xinerama patch to NX. ;-) From now on... using this ITP for client-only discussions. Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpyFwC08w3xp.pgp Description: Digitale PGP-Unterschrift
Bug#655618: [Pkg-x2go-devel] Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Le jeudi 12 janvier 2012 à 20:22 -0500, John A. Sullivan III a écrit : > I am very concerned about the old X code, too and we are actively > watching SPICE. SPICE has extraordinary potential but it is still > slower than NX on WAN links - not much but enough to make a user > noticeable difference. I am surprised NX is even considered for WAN usage. Our in-house tests showed that NX has a noticeable usability impact as soon as the latency reaches 10ms, while the figure goes up to 30ms for VNC - which is currently the only serious solution for WAN links. -- .''`. Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1326463427.3223.29.camel@pi0307572
Bug#655618: [Pkg-x2go-devel] Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Hi On Friday 13 January 2012, Mike Gabriel wrote: > Hi Reinhard, dear all, > > On Fr 13 Jan 2012 11:31:00 CET Reinhard Tartler wrote: > > > http://anonscm.debian.org/gitweb/?p=collab-maint/x2go/nx-libs.git;a=tree > > and, from what I see, is appropriate for being uploaded to unstable. For > > clarity, I think we should rename the git repository from nx-libs.git to > > nx-libs-light.git. Mike, can you please handle that? > > Renamed! > http://anonscm.debian.org/gitweb/?p=collab-maint/x2go/nx-libs-lite.git;a=tree [...] Thanks, this makes it a lot more reviewable (I stumbled into the full nx-libs in the master branch last night). nxcomp and nxproxy indeed don't pose the problems I mentioned last night. But I wonder, why do you need a merged source for this? The current versions of nxcomp and nxproxy, each built from their own upstream tarballs, is already at the 3.2 version state and should work (given that it's in the archive already) for client uses. If it's stability, as mentioned in some other string of this thread, that would be a mere - fixable - bug, but the only reason I can see is making the server parts buildable - and that's where my concerns of massive code duplication of the full X.org 6.9 source tree return. Yes, I'm aware of how well the NX protocol works over high latency and low bandwidth links, but I also know how much of a nightmare it is to work on that imake hell of the forked X.org 6.9, aka nx-x11, source. Regards Stefan Lippers-Hollmann -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201201131714.11684.s@gmx.de
Bug#655618: [Pkg-x2go-devel] Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries
Hi Stefan, hi all, On Fr 13 Jan 2012 17:14:08 CET Stefan Lippers-Hollmann wrote: Hi On Friday 13 January 2012, Mike Gabriel wrote: Hi Reinhard, dear all, On Fr 13 Jan 2012 11:31:00 CET Reinhard Tartler wrote: > http://anonscm.debian.org/gitweb/?p=collab-maint/x2go/nx-libs.git;a=tree > and, from what I see, is appropriate for being uploaded to unstable. For > clarity, I think we should rename the git repository from nx-libs.git to > nx-libs-light.git. Mike, can you please handle that? Renamed! http://anonscm.debian.org/gitweb/?p=collab-maint/x2go/nx-libs-lite.git;a=tree [...] Thanks, this makes it a lot more reviewable (I stumbled into the full nx-libs in the master branch last night). nxcomp and nxproxy indeed don't pose the problems I mentioned last night. :-) two different pair of shoes... Good that Reinhard cloned the original ITP into two (client-only and server/client). But I wonder, why do you need a merged source for this? The current versions of nxcomp and nxproxy, each built from their own upstream tarballs, is already at the 3.2 version state and should work (given that it's in the archive already) for client uses. If it's stability, as mentioned in some other string of this thread, that would be a mere - fixable - bug, but the only reason I can see is making the server parts buildable - and that's where my concerns of massive code duplication of the full X.org 6.9 source tree return. nx-libs (LITE) is a subset of folders of nx-libs (FULL). If there was acceptance or a strategy or a new realm of possiblities that would allow us uploading nx-libs (FULL) to Debian some time in the future, the transition would be smooth. Apart from that: nxproxy is just one compilation step. nxproxy is a similar binary wrapper for libxcomp3. So by content the two belong together, maintaining two source projects is a possibility but it was not our choice here (we as in X2Go upstream who is redistributing the NX tarballs). Note: the X2Go packaging team uses X2Go upstream as NX redistributor. And (being in a double role) X2Go upstream provides one tarball nx-libs lite/light (with applied patches). This is done, because the Debian packaging team shall have a patch-friendly upstream. Yes, I'm aware of how well the NX protocol works over high latency and low bandwidth links, but I also know how much of a nightmare it is to work on that imake hell of the forked X.org 6.9, aka nx-x11, source. Yes, it is a hell. I have been in it for the last four weeks (over X-mas, yeahhh...). But as I use X2Go for loads of projects from simple GUI based system administration to large schools with PXE X2Go boot environments (LDAP-based, PostgreSQL based), I really have a deep interest of providing that to others (i.e. to Debian). Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgptlSjmQHPFt.pgp Description: Digitale PGP-Unterschrift
