Hi<br><br> You are rigth Adrian... I'am making 2.0 Version of Musix distro... and i are using jackd from squeeze... <br><br>Best regards<br><br><div class="gmail_quote">2009/11/17 Adrian Knoth <span dir="ltr"><<a href="mailto:adi@drcomp.erfurt.thur.de">adi@drcomp.erfurt.thur.de</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Mon, Nov 16, 2009 at 12:07:25PM -0300, Felipe Sateler wrote:<br>
<br>
>> The generic fix is to recompile jackeq against new jackd package. Since<br>
>> we know the entire set of jackified apps, I see no point in<br>
>> reintroducing this 0.100.0 thing, it would bite us in jackd2 again.<br>
> (Is jack2 API and ABI compatible with jack1?)<br>
<br>
</div>Yes, it's a drop-in replacement, and users can decide whether they want<br>
to use jack1 or jack2. They also keep the command line syntax in sync.<br>
<div class="im"><br>
>> For keeping our packages simple and clean, I suggest to recompile.<br>
> True. But I think the transition has been less smooth than it could have<br>
> been (my bad, I didn't think there were apps that old, apparently). The<br>
<br>
</div>I still wonder how this bug got triggered. We already had a binNMU for<br>
jackeq, but the poster is using the old one (probably linked against<br>
libjackd-0.100). (the lenny version).<br>
<br>
The jackd version in lenny is 0.109, so we must be talking about some<br>
mixed system configuration, that is, a jackd version from<br>
unstable/testing and jackeq from lenny. (Daniel, please clarify)<br>
<br>
With jackeq from unstable/testing, there's no bug. With jackd from<br>
lenny, there's no bug.<br>
<br>
<br>
You also had the compat symlinks for a while:<br>
<br>
<a href="http://git.debian.org/?p=pkg-multimedia/jack-audio-connection-kit.git;a=commitdiff;h=a90b2dada36e66e3faf2dcfc769a8ff0967f01a0" target="_blank">http://git.debian.org/?p=pkg-multimedia/jack-audio-connection-kit.git;a=commitdiff;h=a90b2dada36e66e3faf2dcfc769a8ff0967f01a0</a><br>
<br>
<br>
Though it's not that hard to re-enable these two lines, I think we made<br>
everything right. I don't think we support mixed lenny/testing<br>
environments, we focus on squeeze. And for squeeze, we're done. ;)<br>
<br>
(I see this all the time: Ubuntu-8.04 too old for FFADO, too old for<br>
modern ardour, the new jackd requires celt-0.7.0 which got added to<br>
unstable last week... the whole pro-audio stuff is bleeding edge. It<br>
just doesn't make sense to run lenny with some parts from unstable.)<br>
<div class="im"><br>
<br>
> thing is that now a mixed upgrade of jack and friends can leave<br>
> applications in a broken state.<br>
<br>
</div>If you think we should support this scenario, I'd second your proposal<br>
of re-adding the 0.100 compat link.<br>
<div><div></div><div class="h5"><br>
<br>
<br>
Cheerio<br>
<br>
--<br>
mail: <a href="mailto:adi@thur.de">adi@thur.de</a> <a href="http://adi.thur.de" target="_blank">http://adi.thur.de</a> PGP/GPG: key via keyserver<br>
<br>
<br>
</div></div></blockquote></div><br>