EDR> It's not a matter of debian developer laziness ... the ardour in sid
EDR> needs patches to _upstream_ libraries. If/when those upstream libraries
EDR> accept the patches the ardour devs need, then those libraries can get
EDR> into debian and ardour can use the debian packaged versions rather than
EDR> it's own forked versions.
100% agreed, ardour not in lenny is a Real Pity (TM). To recap
happened:
0) the ardour package was built against some 3rd party libs shipped
inside the upstream tarball, this raised an RC bug
1) that bug was around for a long time, there were no easy fix for
that, but eventually all of the patches made it the 3rd party upstream
projects, which in turned made it to si
2) I've fixed RC bug in ardour in version 2.7.1-2
http://packages.debian.org/changelogs/pool/main/a/ardour/ardour_2.7.1-2/changelog
It was on Dec 18th, that means nearly 2 months before lenny got
release. At this point ardour was RC-free BUT..
3) It was depending on jackd 0.109.2, uploaded a few days before. Note
that jack 0.109.2 was a very important release because it fixed
important bugs in version 0.106, which had been around for almost one
year.
Unfortunately lenny was already freezed by that time, and although
both of the above updates were really safe (IMO) and despite all the
efforts I and especially Reinhard put into convincing the release
managers, we are unable to convince them to accept the updates in
lenny.
I personally felt very disappointed by all this, especially
considering that lenny got out *2* months later.