Bug#556392: jackeq does not start

[Felipe Sateler]

Adrian Knoth wrote:
> On Sun, Nov 15, 2009 at 04:52:10PM -0300, Felipe Sateler wrote:
> 
> Hi!
> 
>>> this link is created in the installation of new versions of libjack-0.100.0.
>> Hmm, the link is lost on sid and squeeze. I think we should put it back  
>> in the libjack0 package.
> 
> I'm not entirely sure about this. libjack-0.100 was a big mistake, and I
> guess we're all happy to leave it buried in the past.
> 
> The generic fix is to recompile jackeq against new jackd package. Since
> we know the entire set of jackified apps, I see no point in
> reintroducing this 0.100.0 thing, it would bite us in jackd2 again.

(Is jack2 API and ABI compatible with jack1?)

> 
> For keeping our packages simple and clean, I suggest to recompile. 

True. But I think the transition has been less smooth than it could have 
been (my bad, I didn't think there were apps that old, apparently). The 
thing is that now a mixed upgrade of jack and friends can leave 
applications in a broken state.

I see two possible ways out:

1. Detect which apps have not been uploaded since oldstable. These 
should be the problematic ones.
2. Make libjack Breaks: all those apps << a certain version (which we 
have to introduce).
3. Ask for binNMU's of those packages.

1. Add the symlink into the libjack0 package.

The libjack symlink can be left until squeeze, we ask for binNMU's 
before squeeze, and drop the link afterwards.