[helix-maintainers] Sarge debs & new repo

[Wouter van Heyst]

On Wed, Aug 25, 2004 at 06:32:31PM +0200, Thomas Maurer wrote:
> Jap, the generation of the Sources.gz file seems to take the wrong path.
> Will fix that tomorrow (after my last exam :)).

How did your exam go?
> 
> > Looks like something went wrong in the transition from a flat archive. In the meantime, I've just downloaded by hand.
> > Some questions:
> > 
> > 	- Do you have a strategy for branching sarge/sid versions? (Oh dear, I might have already said it :)
> 
> What do you mean with 'branching sarge/sid versions'? I think we build
> all our debs twice: one for sid, one for sarge. Or did you meant
> anything else? =)

Yes, but I mean keeping track of the changelogs in cvs, HEAD being sid
and a branch for sarge or so?

> > 	- How about building from cvs?
> 
> The server + producer are currently CVS versions (branch HEAD). I think
> I missed your point, though ;).

Heh, using debian/ from helix.alioth.debian.org cvs :)

> > 	- Should the buildrc end up in the debian package as it does now?
> 
> I think yes, otherwise ribosome isn't happy. I could be wrong, but if
> it's not needed, we drop it.

I think it's not needed after the build. Will have a go at removing it.
> 
> > 	- What exact orig tarball are we using? A recently downloaded tarball from
> > 		https://player.helixcommunity.org/2004/downloads/ gives
> > 		33f8229dd841a7e305228a2aadc000cc  helixplayer1.0-gold-source.tar.bz2
> 
> The current tarball is generated by the scripts I sent you some time
> ago. It's just a clean download of the bingo-gold branch via ribosome.

Hmkay, there is still activity in upstream cvs, we're not tracking that,
are we?

Wouter