On 2010-09-12 12:32, Alessio Treglia wrote:
it's good to see this new release!
Just to clarify, I'm also an upstream developer of FluidSynth and was
the release manager for 1.1.2. I'm doing both that, and the current
packaging update, in my spare time (so it's not sponsored by Canonical).
You might want to know that --enable-ladspa causes a build error in
1.1.2. It is fixed in trunk, and I'm considering rolling a patch
release, but I wanted to see if there was any difficulties packaging it
first, so if there was, I would catch those as well in the patch release.
Things are going pretty well (nothing committed to alioth yet), but I
noticed that the CMake build system no longer has generates an .a file. I'm
not a linking expert, so - does this matter?
This means that upstream has decided to not compile static libraries anymore.
It's fine for me, I don't have any objection.
Okay, good to know.
dpkg-buildpackage: full upload; Debian-native package (full source is
Now running lintian...
W: fluidsynth source: debian-watch-file-in-native-package
W: fluidsynth source: native-package-with-dash-version
How do I avoid that?
By switching to format 3.0 (quilt) , which allows us to strip
upstream's debian directory without repacking the original tarball.
Hmm, upstream (as in the original 1.1.2 tarball) does not have a debian
Second theory, can this be related to that I never updated the
changelog? I was unsure of how to that with git-dch and all these
semi-automatic tools expecting things to be in a certain way. (will "dch
Third, Squeeze is now frozen. Can this version still go into unstable, or
does it have to go into experimental?
I see several changes, so experimental would be the right place .
There are several changes, although seen from my perspective, 1.1.2
contain quite important bug fixes, and I find it both more stable and
more tested than 1.1.1. Commenting on Launchpad bug #636473, I'm all for
having 1.1.2 in Maverick.
David Henningsson, Canonical Ltd.
pkg-multimedia-maintainers mailing list