[Pkg-x2go-devel] Fwd: Re: Bug#609806: nxproxy prepared for build on Alioth

[Reinhard Tartler]

On Thu, Jun 30, 2011 at 14:02:27 (CEST), Mike Gabriel wrote:

> Hi Jonas, hi all, hi Matthew,
>
> @Matthew: in a nutshell: do you have any VCS container that documents
> your past work on pkg-nx? All I could find dates back to version 2.0.0
> (svn.debian.org). If so, could you provide information, download
> location etc.? THANKS!

http://lists.alioth.debian.org/pipermail/pkg-x2go-devel/2011-February/000007.html

> On Di 07 Jun 2011 22:29:03 CEST Jonas Smedegaard wrote:
>
>> I do not suggest hunting down development VCS used by Matthew.  I
>> suggest to do this:
>>
>>  a) Bootstrap from upstream pristine source:
>>
>>  a1) if project exist in Debian with pristine-tar tracking, use
>>      "git clone ..."
>>
>>  a2) if project exist in Debian without pristine-tar, use
>>      "git-import-dscs --debsnap --pristine-tar --sign-tags ..."
>>
>>  a3) if project does not exist in Debian, use
>>      "git-import-orig --pristine-tar --sign-tags ..."
>>
>>  b) Optionally mixin alternative Debian VCS if available:
>>
>>     Rewrite history to apply upstream source and packaging commits
>>     in proper order using "git rebase ..."
>>
>>     It is tricky to do right, and I often skip it.
>>
>>  c) Cherry-pick additions from external VCS:
>>
>>     Prepare each external VCS source as a git (e.g. "git clone ...",
>>     "git svn clone --stdlayout ..." "git cvsimport" etc.), add each
>>     with "git remote add somegit ../somegit", cherry-pick minimal
>>     relevant commits onto the master branch, and make sure to remove
>>     any temporary local branches before pushing the results.
>
> What I could find on vasks.debian.org is an SVN repos that contains  VCS
> information till version 1.5.0.something (including upstream  code). For
> NX packages v2.0.0 there are some /debian folders only, but  no upstream
> code.

That's a common mode that svn-buildpackage suggests.

> On archives.debian.org I could not find any NX packages up to Debian
> etch. Neither for Debian lenny in oldstable (which I find weird, as
> there was nxcomp and nxproxy in Debian lenny IMHO).

There is no archives.debian.org. The history of the packages can be seen
in the PTS:

http://packages.qa.debian.org/n/nxcomp.html
http://packages.qa.debian.org/n/nxproxy.html
http://packages.qa.debian.org/q/qtnx.html

> So indeed (as Reinhard mention in an earlier posting) the greatest
> (recent/relevant) history is in the nx lib packages on the X2go Git
> site:
>
> http://code.x2go.org/gitweb?p=nxcomp.git;a=summary
> http://code.x2go.org/gitweb?p=nxproxy.git;a=summary
>
> Never packaged before in Debian (AFAIK):
> http://code.x2go.org/gitweb?p=nxcompext.git;a=summary
> http://code.x2go.org/gitweb?p=nxcompshad.git;a=summary

These are only required for the NX server. Like all other NX Clients,
QtNX only needs nxcomp and nxproxy

> Reinhard has furthermore already prepared X2go Git updates NX v3.5.0-x.
>
> However, there are some problems with that:
>
>   o no pristine-tar

trivial to import

>   o patches from Debian/Ubuntu applied to code directly

Indeed.

>   o X2go is not upstream source

How is that a problem?

> So, options may be:
>
>   o find a VCS that contains the Debian packaging history of NX packages
>   o find a comprehensive pool of former Debian packages (.dsc,
>   tarballs)

We have http://snapshot.debian.org for that

>   o start from X2go Git for documentation of history and modify/rebase
>   o start from scratch...
>
> Any help/comments appreciated!!!


If this were to vote, I'd vote 'start from X2go Git' over 'start from
scratch'.


-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4