Re: Debian maintainership, using Arch

Kristian Kvilekval <[email protected]> writes:

>> However, there would be some things that would make my live
>> significantly easier:
>> 
>> I'd like to put my debian stuff into my Arch repo (see
>> http://yi.org/rotty/Software#gnuarch). I already branched off
>> Kristian's cvstrunk branch and fixed the RTP parsing bug
>> (zinf--rotty--patch-3).
>> 
>> It would be very helpful if we could have:
>> 
>> 1) A --release--2.2 branch, for tagging releases (see
>>    http://regexps.srparish.net/tutorial-tla/symbolic-tags.html#Symbolic_Tags).
>>    I guess this is not really workable right now, since there is
>>    nothing to point 2.2.{0,1,2} (at least) to. Anyway, Kristian: is
>>    there a revision in --cvstrunk that "is" 2.2.5?
>
> Done.   Patch-6 was actually 2.2.5.  I've been meaning to do 
> what you are suggesting for some time now, so I am glad that you asked
> for it.
>
> [email protected]/zinf--release--2.2
>
> base-0 is actually 2.2.5 
> When we finally get to 2.3 then patches numbers will correspond to 
> release numbers. I don't have the time right now to try to 
> and re-create all the previous versions.
>
Fine.

>
>> 2) A branch for bugfixes. This would allow me to simply star-merge
>>    this branch into my (yet to be created) debian--2.2.5 branch. I
>>    will also only commit Debian-related bugfixes to my rotty branch,
>>    so there can be mutual star-merging to deal with Debian-related
>>    bugs.
>
> I am thinking we should have small branches for fixes for each release,
> which can then be merged into trunk every once in a while, but will
> keep arch history in the meantime.  To that end, another branch
>
> zinf--fixes--2.2.5
>
Cool. I branched zinf--debian--2.2.5 off my rotty branch and
join-branch'ed zinf--fixes--2.2.5. So a star-merge from
zinf--debian--2.2.5 into zinf--fixes--2.2.5 should give you the
.arch-inventory stuff, plus the one rtp:// fix. You might want to have
the .arch-inventory (zinf--rotty--0.1, patches 1+2) stuff in your main
branch (cvstrunk?) however.

>> To sum it up: it would be really nice to have bugfixes as clean
>> Arch changesets (see
>> http://regexps.srparish.net/tutorial-tla/exploring-changesets.html),
>> ideally including the Debian bug number they address in the log
>> message (see my log message for zinf--rotty--patch-3).
>> 
>> I don't know if this is really workable without having all developers
>> switching to Arch, however.
>
> Eventually I would like to move the archives back to sourceforge
> and possibly use tla-pqm http://web.verbum.org/arch-pqm/
> If you feel like to trying to cobble it together, please give
> it a go.  Currently it seem to have the required python and
> gpg so it might just work, but we would need tla running
> at least from a shell account.   I played around for
> a bit, to see if I could just mirror up on there, but
> I got some errors and didn't check what caused them.
>
>
Well, I've set up tla-pqm at merkel.debian.org for
guile-gobject[0]. Unfortunatly, merkel.d.o has currently restricted
access due to a pending kernel update. Otherwise, and if tla-pqm
supports per-archive keyrings already, it would easily be possible to
host the patch queue for zinf there, too. Information access to the
queue would look like can be found in [1].

[0] http://www.gnu.org/software/guile-gtk/docs/guile-gobject/
[1] http://mail.gnu.org/archive/html/guile-gtk-general/2004-02/msg00002.html

Regards, Andy
-- 
Andreas Rottmann         | Rotty@ICQ      | 118634484@ICQ | [email protected]
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

Say NO to Software Patents! -- http://petition.eurolinux.org/


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click