next upload of jack
siretart at tauware.de
Wed Feb 25 08:58:11 UTC 2009
Free Ekanayaka <free at 64studio.com> writes:
> Hi Reinhard,
> |--==> On Tue, 24 Feb 2009 23:12:56 +0100, Reinhard Tartler <siretart at tauware.de> said:
> RT> Hi Free,
> RT> jack needs to be rebuilt because of the libraw1394 transition. Other
> RT> packages are already waiting for jack to be rebuilt. I've been doing
> RT> some work in the git repo. could you perhaps have a look at it and
> RT> upload it to unstable?
> RT> if it helps you, I can also build&upload it, I just cannot test it
> RT> properly (besides installing the packages in my chroot).
> I've reviewed the changes, very nice work, thanks for the clean up! Please
> just feel free go a ahead with the upload.
ok, will do.
> Just a question about how the team uses git. I now see two approaches
> for inserting entries in debian/changelog:
> 1) write the entry manually in the debian/changelog [...]
> 2) commit only the changes to the actual source-code [...] and
> generate debian/changelog with git-dch just before releasing the
> package [...]
> I tend to prefer 2)
I have to admit that I havn't given the issue much attention so far,
because I was used to using 'debcommit', which grabs comment from
debian/changelog (which implements 1). However I agree that in a
decentralized setting like git, 2) causes less pain when merging
I'll do 2) in future for git branches, and 1) for svn branches (until
they are converted to git.
A small note with 2). After an upload, a new changelog upload with the
proposed next version should be created and committed nevertheless, so
that testbuilds are easy without using an (uncommitted)
debian/changelog. Otherwise the testbuilds will have the old version
okay for everyone?
Reinhard Tartler, KeyID 945348A4
More information about the pkg-multimedia-maintainers