Bug#791080: jackd2: library transition may be needed when GCC 5 is the default

[Adrian Knoth]

On 08/03/15 18:58, Felipe Sateler wrote:

>>>> Control: tags -1 + confirmed patch
>>>> Control: retitle -1 jackd2: library transition is needed when GCC 5 is the default
>>>>
>>>> needs build dependencies to transition first. patch at
>>>> http://launchpadlibrarian.net/213139914/jackd2_1.9.10%2B20140719git3eb0ae6a~dfsg-2ubuntu1_1.9.10%2B20140719git3eb0ae6a~dfsg-2ubuntu2.diff.gz
>>>
>>> This doesn't look correct to me. Jack1 and Jack2 are supposed to be
>>> drop-in alternatives, and jack1 is a C API. So either the shlibs file
>>> is wrong, or jack2 doesn't need transition.
>>
>> I didn't rename the package for the C API.
>>
>>> Matthias, how did you verify a transition was needed?
>>
>> see the new symbols at
>> https://people.debian.org/~doko/logs/gcc5-20150701/jackd2_1.9.10+20140719git3eb0ae6a~dfsg-2_unstable_gcc5.log
>>
>> note, this was already mentioned in the original report.
>
> I'm sorry if I was unclear. The *only* public API is supposed to be
> the C one. Everything else is not in the published headers, and no
> client should use that.
>
> Either my statement is wrong or the shlibs file is wrong.
>
> If I'm correct, then there is no need to do a transition, all users of
> the C++ parts come from the same source and have strict dependencies.

Felipe is right. Only the C API matters, and you can freely swap
libjack0 (C) for libjack-jackd2-0 (C++) without recompiling anything.

We even compile every package in Debian against the C lib. From my
perspective, there's no need to transition jackd2.



Cheers