[Pkg-ltsp-devel] sarge-backport branch

[Gustavo Franco]

On 1/30/06, vagrant at freegeek.org <vagrant at freegeek.org> wrote:
> well, i've put up a sarge-backport branch:
>
>
> http://llama.freegeek.org/~vagrant/bzr-archives/sarge-backport
>
>
> it only contains two patches not in the pkg-ltsp main branch so far, but
> maybe we'll want more in the future.
>
> one patch is a simple 4-line patch to have gnomecanvas and gnome.canvas
> working for both sarge and newer versions of python.
>
> the other patch is merely merged from pere's ltsp-main branch, to add
> subprocess.py back into the ldm package.

I think we should try keep the main branch, sid and sarge compatible.
If it can't be possible right now, we should maintain two official
branches: one for unstable packages and a second to sarge, both in our
alioth repository. Of course vagrant, me, otavio and others should
keep their own branches having pkg-ltsp main and pkg-ltsp sarge as
ancestors. Comments ?

> and while on the subject of sarge backports, if folks could upload a good
> backport of bzr 0.7 and a compatible bzrtools packagetobackports.org(or some other trustworthy place), that would be very nice.
>
>
> learning how to sort of hack together bzr and related tools to work with
> sarge has taken up more time for me than actual ltsp development.
>

You should talk with Aaron Bentley. He knows a lot about bzr and is
the bzrtools upstream. Btw, i'm the bzrtools maintainer and there's no
bzrtools 0.7 yet, but it's coming. FYI, in Ubuntu Dapper and Debian
sid there's already bzr 0.7 but bzrtools 0.6-2 won't install.

--
Gustavo Franco