[Pkg-ltsp-devel] pkg-ltsp bzr repository status and more.

[Gustavo Franco]

On 1/29/06, Petter Reinholdtsen <pere at hungry.com> wrote:
>
> [Gustavo Franco]
> > Hi list,
> >
> > There's a pkg-ltsp "official" repository being prepared right now to
> > host the branch(es) that we should use to do the upcoming ltsp Debian
> > package uploads.
>
> Sounds good.  But until that is ready, I'll try to get a new release
> out based on my old branch.

Sure, but if you won't release today i think we can start branching
out from our official repository soon.

> > We used mdz as a start point and it's already available[0], but you
> > *don't* want to branch out from that tree yet. claviola converted both
> > vagrant and pere repositories from baz to bzr and otavio merged them
> > over pkg-ltsp branch in a different location[1].
>
> When will this be ready to branch from?  Can I get a branch of my old
> branch with a common anchestor with Matt and Oliver?

If you think the repository is ok, and with ok i mean: mdz is the
ancestor, and there are almost any patch that you and vagrant applied,
it's ok. You can branch out from that and ask Otavio how you can
"push" back your changes to the official repository since we aren't
going with a pqm right now. Btw, we need to take care about the
Maintainer and Uploaders field.

> > What needs to be done before the first pkg-ltsp upload:
> >
> > * You can review [1] and let us if there's something weird there;
>
> There is.  There are typos in ltsp-build client:
>
> (...)

Good, is that hunk against our branch at alioth? That kind of review
we were talking about. If you've others let me know.

>
> I have not figured out how to push my branch to a public site yet, so
> I provide the patch instead. :)

That's ok, i think you should put out the missing bits here before
branch out from pkg-ltsp. Btw, you can publish a branch doing:

Installing bzrtools package
cd branch
bzr push username at coolhost.foo:/home/username/public_html/branch/


> I also noticed that the uploaders list in debian/control was wrong, so
> I wonder if this is really based on my branch or not.

It needs review as i said above, but the repository is mdz with your
and vagrant patches over. I need to take a look, but maybe Otavio
patched some stuff to. You can check the log history.

> > * Otavio will "replace" pkg-ltsp repository[0] content with [1], at
> > this point we will have mdz + pere + vagrant in place. It will be
> > the pkg-ltsp start point in terms of repository;
>
> OK.

I think he already did that.

> > * ogra changes. We need to hear his feedback, and see what we can
> > merge back from his branches
>
> We imediately want his sound support patches, and probably a few
> others.

*sounds* cool. Let us clean pkg-ltsp branch and branch out from that.
I think that we can release the next upload already under pkg-ltsp
name. Carlos was going to work in ogra' stuff after the first release,
but i'm sure he can help with the sound support right now.


> > * pqm[2]. Each person involved will maintain at least one branch and
> > we will have a central one at alioth, it would be good use a patch
> > queue manager. The main idea behind that, is ask for merges by mail,
> > and let the script handle some of the workload in the central
> > repository.
>
> What is the alternative to this?  Earlier, we just picked one branch
> as the "official" branch, and used it to release.  Matts branch (and
> now Olivers branch) was used for ubuntu, and mine was used for Debian.
> Is that a working alternative?

It seems that we will still have Ubuntu's branches (with ogra stuff)
and pkg-ltsp' branch (that in the future can be more than one). Each
pkg-ltsp member should branch out from pkg-ltsp repository and work on
whatever he wants (coordinating through the list). It's what we can
have without too much work and pain.

--
Gustavo Franco