Re: [X2go-dev] [PATCH] x2goclient 3.0.1.18 fails due to missing files + workaround
V Sat, 21 May 2011 20:24:17 +0200 Mike Gabriel mike.gabr...@das-netzwerkteam.de napsáno: Hi Milan, Hi Mike, this is already fixed in the x2goclient Git project on code.x2go.org. However, no new version has yet been tagged as a release. You may draw the latest code from Git anyway. Currently, the HEAD of the master branch should be fine. From today's Git: x install failed due to missing x2goclient.desktop (which is in desktop subdir). Patch to the Makefile is attached. x compilation fails due to missing qmake-qt4, which on Archlinux is called simply qmake. I assume that this is distro specific. Having been corrected for the above matters, it compiled cleanly. regards, Milan -- http://www.milan-knizek.net/ About linux and photography (Czech only) O linuxu a fotografování (pouze česky) From 34db0c1008490cd8c2ef457fb0d679e966c37f58 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Milan=20Kn=C3=AD=C5=BEek?= kni...@volny.cz Date: Sun, 22 May 2011 16:46:53 +0200 Subject: [PATCH] Correct path for x2goclient.desktop installation --- Makefile |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Makefile b/Makefile index 04c0676..3348a4b 100755 --- a/Makefile +++ b/Makefile @@ -53,7 +53,7 @@ install_client: $(INSTALL_DIR) $(DESTDIR)$(SHAREDIR)/icons/hicolor/64x64/apps $(INSTALL_DIR) $(DESTDIR)$(SHAREDIR)/icons/hicolor/32x32/apps $(INSTALL_PROGRAM) $(CLIENT_DIR)/x2goclient $(DESTDIR)$(BINDIR)/x2goclient - $(INSTALL_FILE) x2goclient.desktop$(DESTDIR)$(SHAREDIR)/applications/x2goclient.desktop + $(INSTALL_FILE) desktop/x2goclient.desktop$(DESTDIR)$(SHAREDIR)/applications/x2goclient.desktop $(INSTALL_FILE) icons/x2goclient.xpm $(DESTDIR)$(SHAREDIR)/x2goclient/icons/x2goclient.xpm $(INSTALL_FILE) icons/128x128/x2goclient.png $(DESTDIR)$(SHAREDIR)/x2goclient/icons/x2goclient.png $(INSTALL_FILE) icons/128x128/x2gosession.png $(DESTDIR)$(SHAREDIR)/x2goclient/icons/x2gosession.png -- 1.7.5.1 ___ X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2go-dev] [PATCH] x2goclient 3.0.1.18 fails due to missing files + workaround
Hi Milan, On So 22 Mai 2011 16:57:37 CEST Milan Knížek wrote: V Sat, 21 May 2011 20:24:17 +0200 Mike Gabriel mike.gabr...@das-netzwerkteam.de napsáno: this is already fixed in the x2goclient Git project on code.x2go.org. However, no new version has yet been tagged as a release. You may draw the latest code from Git anyway. Currently, the HEAD of the master branch should be fine. From today's Git: x install failed due to missing x2goclient.desktop (which is in desktop subdir). Patch to the Makefile is attached. This one I have just committed... About the qmake-qt4 issue you reported I have to think about how to handle it in the Makefile... Greets, 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 pgpFcNhzfRDiN.pgp Description: Digitale PGP-Unterschrift ___ X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
[X2go-dev] suidperl depreciated upstream?
Hello List! perl-suid is the run-time dependency of x2goserver from the current Git. I have spent some time searching for a package (or PKGBUILD script) for Arch Linux and have not succeeded. Having also checked the current source code of Perl, I found the reason for it - the INSTALL file reads: - suidperl suidperl was an optional component of earlier releases of perl. It is no longer available. Instead, use a tool specifically designed to handle changes in privileges, such as sudo. - (I am aware about the sudo vs suidperl discussion held in February this year on the mailing list.) Is there any solution for those running the most recent perl (and for future in general)? Regards, Milan -- http://www.milan-knizek.net/ About linux and photography (Czech only) O linuxu a fotografování (pouze česky) ___ X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2go-dev] nxproxy and nxcomp uploaded to Ubuntu Oneiric
On Sat, May 21, 2011 at 20:43:18 (CEST), Mike Gabriel wrote: Hi Reinhard, We have to distinguish current code bases properly: code.x2go.org - X2go upstream (currently containing sort of upstream NX'ish code forks, which is a non-optimal redundancy now that NoMachine has brought up some recent work of NX again) collab-maint on Alioth - package preparation for Debian (pkg-x2go-devel team) Launchpad.net/~x2go- build engine for Ubuntu (provided by X2go upstream) packages.x2go.org - build engine for Debian (provided by X2go upstream) On Sa 21 Mai 2011 17:13:33 CEST Reinhard Tartler wrote: o drop nxcomp (and later nxcompext, nxcompshad) from code.x2go.org (X2go upstream), same with nxproxy (the code is not a real fork...) What problem would that solve? AFAIUI this step would break the PPA and leave users of released versions of ubuntu in the cold As discussed on pkg-x2go-devel, for Debian the Debian maintainers of X2go will have to use NoMachine as upstream for nxlibs + nxproxy. So, there is no point of hosting NX code on code.x2go.org. For the X2go Launchpad PPA (build engine) I would then draw in the code from collab-maint Git (instead of drawing in the code base from code.x2go.org / X2go Git). But that's exactly my point, there is really no need for breaking the current setup before we have a something that can replace it. And now you propose to move the current known-to-work branches to something that doesn't even exist yet. IOW: Go ahead and do whatever you want to do on alioth. When it's ready, we can reconsider if it's worth moving there, but currently, I really don't see any benefit in breaking the current infrastructure. And for Stéphane's work, well, what's the problem with integrating it in the *current* infrastructure on code.x2go.org? o provide X2go-specific patches for NX 3.5 upstream on X2go upstream that are recommended to be incorporated by package maintainers did you already look at those 'patches'? This might be a misunderstanding. No, it's not. Please have a look at them. [...] o draw Stéphanes work to collab-maint on Alioth Why not on code.x2go.org? Because code.x2go.or is intended for X2go upstream development. Not for building Debian packages. I don't know what to say here, I'm speechless. On Alioth's collab-maint workspace all Debian developers have write access by default. That's my main reason for hosting the packaging code there. Still, so far you have found exactly one DD (i.e., me) willing to work on x2go upstream. Just granting access to everybody is unlikely to improve the situation. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
