[Pkg-kde-extras] Maintaining debian/changelogs with mutiple maintainers under svn.debian.org

[Achim Bohnet]

On Thursday 22 September 2005 20:27, Mark Purcell wrote:
> Achim,

Hi Mark!

> Just wanted to ping you over change logs.
> 
> I noticed you wanted to Preseve the ' -- Debian KDE Extras Team 
> <pkg-kde-extras at ..' line! Also sorry about the 0beta stuff, don't know what I 
> was thinking :-(

;)  It's not easy to spot.  I just realized it last night.
> 
> In my other team we leave the changelog entry to the last person who made the 
> changes (Means you don't have to build with the -k).

Well, I think, it's really good way to make the 'kde extra team' visible.
I mentioned and offered a lot of people on IRC about the kde-extra repo
but without success yet.

I'm not really happy with the changelog format either way. From a user point
of view  section grouped by commiter are less helpfull.  I guess right now
my favorite would be a combination of debian-kernel aka (full name) at the
end of every item and openoffice2.org. AFAIR OOo uses  user relevant stuff
first then, then all the pkging specific changes (I need them badly because
I tend to forget the _why_ of a change very quickly.)  But I'm not really
sure what's best (if it exists;)


> I don't know if you are using the updated debchange(1), but that now has 
> multi-maintainer support as of debscripts >2.9.  This also sort of relies on 
> the last person entry being the change log entry:
>   * debchange: support generating multi-developer changelogs, currently only
>     supporting the format used in this changelog entry. If multiple developers
>     are detected it will automatically add [ Full Name ] lines to disambiguate
>     who did what.

I stopped using using dch when we introduce the team.  I still have not tried
all the ENV settings do get what I imagine it to do :(

Btw. did you ask Paul for his okay to set maintainer to team.  I doubt that
he refuses, but we should ask nevertheless.
> 
> I find this very helpful, also with the recent addition of debcommit(1) to 
> devscripts.  I would be interested in hearing how others are using svn/ 
> devscripts as I find I can work fairly well by the following:

I admit that I use svn-buildpackage rarely.  But this is mostly due to the
fact that you are doing the final pkging ;)  I use debuild -i and dch.
Ah, debi  I always missed. Great to know it available.  I 'll look into
debcommit and your workflow at the next opertunity.  Thx from a quick
look it looks like there's something to learn from.

I also have some kde-extras/README several additions on my TODO. 
Okay with you if I change you parallel pkging handling from tag to branch?
As I wrote earlier, working on  tag/* makes me somehow cry and feeling bad.


When we are at it, would you agree to sponsor wlassistant when ready (not yet)?
Stan is quite new to pkging and I try to help/teach instead of just doing
it myself so it may take quite some time until I'm happy with wlassistant
pkging.


Achim
> cd package/trunk
> edit files under debian/xxx
> dch 'I changed this' --closes xxxxx ;Fixed a bug
> svn-buildpackage -rfakeroot --svn-ignore --svn-lintian --svn-move
>     ; check everything works
> debc
> su
> debi ; if works ok then commmit
> debcommit
> 
> edit more files under debian/xxx
> dch 'I changed something else' --closes xxxxx ;Fixed another bug
> svn-buildpackage -rfakeroot --svn-ignore --svn-lintian; check everything works
> debcommit
> 
> svn-buildpackage --svn-export ; want to do some heavy duty work
> cd ../build-area/package-version/
> optional dpatch-edit-patch new-patch ; if you are using dpatch
> patch < ~/patch.diff
> debuild  ; make sure everything is fine
> cd ../../trunk/
> cp ../build-area/package-version/debian/patches/patch.diff debian/patches/
> svn add debian/patches/patch.diff
> dch 'Encorporated patch' --closes xxxx ; 
> svn-buildpackage -rfakeroot --svn-ignore --svn-lintian; check everything works
> debcommit
> 
> ; lets make a release
> dch -r 
> debcommit
> svn-buildpackage -rfakeroot --svn-lintian --svn-move; check everything works
> Passphrase: sign packages
> debrelease ; upload to ftp-master.debian.org
> svn-buildpackage --svn-only-tag
> debcommit ; NOT Yet Released
> 
> Mark
> 
> _______________________________________________
> pkg-kde-extras mailing list
> pkg-kde-extras at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
> 
> 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- reddy at lion.austin.ibm.com