[pkg-squid-devel] Bug 791117: libecap vs libstdc++6 transitions

[Amos Jeffries]

On 4/08/2015 10:57 p.m., Amos Jeffries wrote:
> On 4/08/2015 10:36 p.m., Luigi Gangitano wrote:
>> Hi Amos,
>>
>> I’m preparing the upload. To clarify some details:
>>
>> - did you already rebuild libecap with GCC5.0? Are there symbols matching __cxx11 or B5cxx11 and thus is a transition needed?
> 
> I did. There are.
> 
> BUT, in this particular circumstance do we actually need a full transition?
> 
> * squid 3.5 is the only thing using libecap3.
> 
> * squid 3.5 is not yet in stretch.
> 
> IMHO ...
> 
> If both rebuild together (depends on cppunit availability) together
> there should not be any noticable issues. What hits stretch will be the
> v5 versions of both packages.
> 
> A "Breaks: libecap3 (<= 1.0.1-1)" on libecap3 should prevent people
> having a partial upgrade in sid.

No that wont work. Would need to be "Breaks: squid (<3.5.7)".

> 
> 
>> - there is no SONAME change in upstream, so I’m going with libecap3v5 it this is ok for you. I don’t want to mess with upstream SONAME.
>>
> 
> You're the boss. :-)
> 
> I just think the *v5 bit looks ugly and we're not exactly dealing with
> pre-existing uses of the library.
> 

Amos