next upload of jack
free at 64studio.com
Wed Feb 25 08:49:52 UTC 2009
|--==> 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.
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, and commit that
change along with the other actual source-code changes (possibly using
the same phrase for both the commit message and the newly inserted
debian/changelog entry), example:
2) commit only the changes to the actual source-code, using a
meaningful commit message (basically the same phrase you'd write in
the debian/changelog), and generate debian/changelog with git-dch just
before releasing the package, the last commit being the debian/changelog
git commit -m "Release version x.y.z-n)" debian/changelog
I tend to prefer 2), because it is easier to cherry-pick commits that
way as you'll avoid conflicts in debian/changelog (think to
maintainers of other distros wanting to apply a certain
patches). After all if we were dealing with regular upstream source
code we wouldn't probably modify the ChangeLog at every commit, we
would rather auto-generate it just before releasing.
More information about the pkg-multimedia-maintainers