[Pkg-x2go-devel] [X2go-dev] Starting to get x2go into Ubuntu Oneiric

[Mike Gabriel]

Hi Stéphane,

On Do 19 Mai 2011 20:25:22 CEST Stéphane Graber wrote:

>> Please register at Alioth and let me know your login name. I will add
>> you to the pkg-x2go team.
>
> "stgraber-guest" should work.

Ok, added.

>> Before this Baikal release (a recommended set of package versions
>> bundled together as _the X2go Software), I would like to stay away
>> from NX 3.5 if it does not work out of the box. (We have to look at
>> the related patchset 3.4 -> 3.5, too).
>
> Yeah, that's something that I noticed earlier today and that seems weird
> to me.
> From my point of view (maybe I'm wrong) it seems like x2go is kind-of
> forking the "upstream" NX code but at the same time tries to follow
> their versioning and keep the same names.

> This could become a real problem if x2go's version of nxproxy, libxcomp*
> end up being somehow incompatible with NoMachine's as people won't
> really know what they're installing.

Hmmm... I guess we originally thought about continuing NX libs  
upstream in the X2go context. But your point about guaranteeing to all  
other NX lib based projects that we will not break anything is a  
responsibility beyond our scope, I guess. So, we basically really have  
to thing about renaming those libs and making it a real fork.

> At least for Ubuntu, I'm going to consider NoMachine as the upstream of
> everything that's listed on this page:
> http://www.nomachine.com/sources.php

Ok, but for Debian this might not work, as it seems to be  
unmaintained. Maybe I am wrong in this point.

> And if x2go needs some specific changes (I'm going to have to go through
> git to figure that out), then it should be applied through documented
> patches in debian/patches and tested for compatibility with everything
> using the same libraries (qtnx being one of them).

Got that!

> So far, my tests show that I can easily get a FreeNX + X2go server
> working and can easily get python-x2go/x2goclient and qtnx working using
> the same libraries.

What is needed is that the x2goagent fork of nxagent works together  
with whatever nxproxy we use. Same for the libs used by x2goagent...

> I perfectly understand that NoMachine isn't a great upstream and that
> there's bug fixes that need to be applied, but I still prefer carrying
> these as well separated patches in the package rather than using a
> different upstream.

Got that, too!

> In an ideal world (to me), x2go would be maintaining a list of
> recommended patches on top of NoMachine's source code, that I could
> easily pull and integrate in the Debian package (as debian/patches/
> files).

Jonas once warned me that maintaining to many patches for a project  
lets the DD become an upstream fork maintainer... (I hope I got that  
right...) ;-). There should be communication possible with whatever  
upstream there is, shouldn't it?

> It really is an issue to have two "upstreams" for the same "project" ...
> I'm really reluctant to use x2go as the "upstream" for anything that's
> at http://www.nomachine.com/sources.php

Again: got that! We have to discuss it with Heinz, Alex, Morty, Arw  
and Reinhard from X2go upstream.

> I usually prefer re-testing and fixing stuff to work with the lastest
> "stable" release from the current upstream as unfortunately I can't
> guarantee that someone else will push 3.5 to the Ubuntu archive.
> We don't have per-package maintainers in Ubuntu so someone else can
> perfectly decide to push a new upstream release at any time before
> Feature Freeze. People usually ask the last uploader if there's any
> reason to stick with an old version, but not always, therefore if it
> works with 3.5, I prefer to go with it.

Ok... With X2go there are always many unknown variables... There has  
been an experience that changing too many things at once gives you  
trouble when finding bugs...


> Done. I have mix of old dh, dh7 and cdbs packages that I upload quite
> regularly, so I don't particularly mind, though I tend to use dh7 for
> most new packages.

Brilliant!

>> I am speaking of the human beings team, not only the launchpad/~x2go
>> team... :-)
>
> I will certainly contribute patches whenever I need to patch something
> and will help with Debian packaging if I find some time.

Brilliant, too!!!

> I unfortunately have to multi-task on quite a few upstream projects +
> actual distribution work :(

That's normal!!!

>> Greets,
>> Mike
>
> Thanks

Fine+Thanks,
Mike


-- 

DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419

GnuPG Key ID 0xB588399B
mail: mike.gabriel at das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.alioth.debian.org/pipermail/pkg-x2go-devel/attachments/20110520/237a5303/attachment.pgp>