Andreas Pakulat wrote:
>On 28.01.12 13:01:28, Scott Kitterman wrote:
>>
>>
>> Luca Beltrame wrote:
>>
>> >In data sabato 28 gennaio 2012 12:13:41, Scott Kitterman ha scritto:
>> >
>> >> but leaves open the question of what caused the incompatiblity and
>> >what
>> >> other packages might be
On 28.01.12 13:01:28, Scott Kitterman wrote:
>
>
> Luca Beltrame wrote:
>
> >In data sabato 28 gennaio 2012 12:13:41, Scott Kitterman ha scritto:
> >
> >> but leaves open the question of what caused the incompatiblity and
> >what
> >> other packages might be affected.
> >
> >As far as I can see
Luca Beltrame wrote:
>In data sabato 28 gennaio 2012 12:13:41, Scott Kitterman ha scritto:
>
>> but leaves open the question of what caused the incompatiblity and
>what
>> other packages might be affected.
>
>As far as I can see, SIP makes no ABI guarantees between versions, so
>that's
>the (u
In data sabato 28 gennaio 2012 12:13:41, Scott Kitterman ha scritto:
> but leaves open the question of what caused the incompatiblity and what
> other packages might be affected.
As far as I can see, SIP makes no ABI guarantees between versions, so that's
the (unfortunate) side effect. What used
We've run into an issue in Ubuntu where we had Sip4 4.13.1and PyQt 4.9 built
against Qt 4.7.4. PyKDE4 4.8.0 was built using this set of packages. All was
working well.
We rebuilt PyQt 4.9 against Qt 4.8.0 due to some packaging updates and had
problems. The primary Ubuntu bug is:
https://bug