[Pkg-x2go-devel] [X2go-dev] Starting to get x2go into Ubuntu Oneiric
Stéphane Graber
stgraber at ubuntu.com
Thu May 19 15:36:32 UTC 2011
On Thu, 2011-05-19 at 16:56 +0200, Mike Gabriel wrote:
> Hi Stèphane,
>
> [Sorry, but resending this mail to all to include Jonas Smedeguard
> (via pkg-x2go-devel in this thread. May I suggest switching
> communication there???]
Ok, removed x2go-dev from the recipients and subscribed to
pkg-x2go-devel.
> On Do 19 Mai 2011 15:56:19 CEST Stéphane Graber wrote:
>
> > Hello,
> >
> > Last week in Budapest at the Ubuntu Developer Summit, we discussed the
> > next steps for WebLive[1] in Ubuntu.
> >
> > One of the things we identified as really important is to move away from
> > FreeNX and use X2go instead as it's a much more active project.
>
> GREAT!!!!
>
> > Last week I already got our application servers running with both FreeNX
> > and X2go and I have some experimental integration code for the Ubuntu
> > Software Center that I'll continue working on over the next few weeks.
> >
> > One of the things we need to do before we can use x2go by default for
> > WebLive is getting it into the Ubuntu archive and at least for the
> > client part into the "main" component (supported set of packages).
>
> Basically, our approach of getting X2go into Ubuntu is an open ITP for Debian:
> http://bugs.debian.org/465821
>
> For this project a pkg-x2go team has formed on Alioth:
> https://alioth.debian.org/projects/pkg-x2go/
>
> Everything around packaging for Debian (and subsequently Ubuntu) we
> should discuss on the related mailing list
> (pkg-x2go-devel at lists.alioth.org):
> https://alioth.debian.org/mail/?group_id=100595
Oh, that's great news, for some reason I forgot to look for an ITP :)
As we need the package in Ubuntu really soon to start testing and
getting it through the MIR process, I'm probably going to upload
python-x2go directly in Ubuntu.
The package should be mostly identical to what should enter in Debian,
so it should be really easy for it to be uploaded in Debian and once
it's in unstable, sync it in Ubuntu so we make sure we have the same
packages in both distros.
For all the other x2go packages, as it's less urgent for me, I can
definitely wait to have it in Debian and then just request a sync.
Depending on the time I have, I might help getting the packages in shape
for an upload in Debian (will just need someone to do the actual
upload).
> > Today, I'm working on updating our nxproxy, libxcomp and libxcompshad
> > packages to their latest upstream releases (3.5.0), merging the
> > excellent packaging work the x2go team has been doing.
>
> Please take a look at our Git on code.x2go.org. I have just today
> improved installation from Makefile and cleaned up the packages. We
> should definitely make sure that we do not induldge in redundant
> effort here.
Current plan for python-x2go is to look at what you have in the PPA and
get something uploadable in Ubuntu from that (which should basically
meet the same criteria as for Debian), then feed back whatever changes I
had to make, so we don't end up with two different packaging.
> I have not known about NX 3.5 yet (DAMN!!!) Is there an active
> community around NXv3 alive somewhere else apart from the X2go
> community??? For Debian we will provide upstream NX. That should be
> the same for Ubuntu (if you start uploading packages to Ubuntu before
> we do so for Debian).
The packages in Debian and Ubuntu (same one) are quite outdated.
Updating them is quite trivial, so I'm currently doing it in Ubuntu and
will send the new packaging back to Debian once I'm done, so hopefully
we can have both up to date and in sync.
> DO you think you can work on our NX code base and do the changes
> there? Work on each Git project (nxcomp, nxcompext, nxcompshad) could
> start in a Git branch first.
I'm currently using the upstream tarballs from
http://www.nomachine.com/sources.php and updated the packaging based on
what's in the x2go PPA and in Debian. Resulting packaging should
probably end up in Debian and then be synced in Ubuntu.
I'll have a look at the git branches on code.x2go.org to see if I missed
anything and will propose patches or merge proposal (if I end up reading
about using git ;)) for any change I needed to do.
My current goal is really to get something in Ubuntu as soon as possible
so other teams can start using it but I really don't want to end up
having to maintain my own packaging.
So as soon as the same version (or newer version) enters Debian, I'll
get a sync done so Ubuntu drops its own packaging and uses Debian's
(which hopefully will be close to identical).
> The question is, if it is advisable to update to NX 3.5 first and then
> packaging for Ubuntu. My recommendation is to get packages into
> Debian/Ubuntu first and then start working on NX 3.5. But I do not
> have a clue how dramatic the changes are.
For nxproxy, which is the only one I looked at so far, the changes are
close to non-existent.
Current packaging (for 3.4) worked as-is and the patch that Debian
carries (allowing stdin as input) applied without any change.
> Do you have a clue how intense the effect on x2goagent (formerly
> x2goagent) will be???
I haven't started working on the libraries yet, I'm guessing that's
where the changes might be a bit more substantial and so might break
x2go. If that's the case, I'll use 3.4 instead and we can deal with 3.5
later :)
> > Next on my list will be to get python-x2go into the Ubuntu archive as
> > that's what we'll be using for our client integration (Ubuntu Software
> > Center is in python) and finally I'll be working on getting the
> > x2goserver itself in the repository (lower priority than the rest) so we
> > don't need a PPA to build our servers.
>
> Again, how about working on Debian inclusion. I am not involved with
> Ubuntu policies too much. Will there be syncs between Oneiric and
> Debian sid in the future? Or is that pathway already closed?
Ubuntu is currently in auto-sync from Debian unstable until the
Debian-Import-Freeze on 16th of June. After that I can easily file
manual sync requests that get processed daily, until our Feature Freeze
on the 11th of August.
So my current plan is:
- Get python-x2go, nxproxy and libxcomp3 in their latest version in
Ubuntu and get people to test it (enable integration in Software Center)
- File the required MIR (Main Inclusion Request) to get these into the
"main" component which is a requirement for Ubuntu to ship it by default
(needs to go through a security review which can take a while)
- Have any packaging change forwarded to x2go PPA and Debian
- Depending on the time I have, help getting the packages ready for
upload in Debian.
- Check the state in Debian and as soon as the same versions are there,
sync from Debian and drop the Ubuntu packaging entirely. After that,
whenever possible packaging changes will happen in Debian only and get
synced in Ubuntu.
> If closed then I suggest you do your work for Oneiric but for the
> Ubuntu p-series we count on Debian sid? What do you think?
I hope we'll already get Debian and Ubuntu in sync for Oneiric, we still
have time so it's perfectly doable.
> > I hope to have most packages built for Oneiric in my test PPA
> > (https://launchpad.net/~stgraber/+archive/experimental) so I can do some
> > tests to make sure these don't break anything (including FreeNX/qtnx)
> > and if everything looks good, I'll be pushing these into the archive
> > later this week.
>
> Stéphane! Couldn't we arrange that you commit the work you perform to
> our Git which then will be synced to our PPAs (lauchpad.net/~x2go) and
> from there you upload to Ubuntu main????
I can certainly upload my changes directly to git instead of sending
patches.
So far, working on nxproxy, the only changes I "think" I had to do was
switch to a non-native package and re-apply the current patches in
Debian.
I was planning on sending an e-mail today or tomorrow with the changes I
had to make to nxproxy and libxcomp3 when updating to 3.5 and preparing
for Ubuntu, including description of the changes and patches when
relevant. If you prefer I commit that to git directly, I can certainly
do it.
> This would make much more sense to me. Please apply for team
> membership, so that Heinz can give you edit-access to
> launchpad.net/~x2go.
It's a restricted team so I can't apply, someone needs to add me.
> I would really appreciated to go this way!!!!
>
> > Once I'm done and everything works for me, I'll be forwarding the list
> > of packaging changes I had to do (if any) so we can ensure your
> > dailybuilds and the "official" Ubuntu packages are in sync.
>
> Again, why not join the X2go team???
Just waiting for someone to add me ;)
> > Thanks for the great work and looking forward to working more with you.
>
> :-)
>
> Greets + looking forward to further exchange (as started in the Debian
> Edu / Edubuntu cooperation!!!!)
> Mike
> PS at list: Stéphane Graber and Johnathan Carter are also heavily
> involved in EduBuntu development and we have just last week met for an
> online meeting dealing about intenseive cooperation between EduBuntu
> and DebianEdu. Great that we overlap in the area of X2go as well
> (X2go has an active cooperation running with Skolelinux/DebianEdu
> Germany!!!)
--
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-x2go-devel/attachments/20110519/70cd5c0f/attachment-0001.pgp>
More information about the Pkg-x2go-devel
mailing list