Bug#1021576: linphone-desktop: Core dumped: Program terminated with signal SIGABRT, Aborted.

[Bernhard Schmidt]

Hi,

>>> The change in 5.0.37-6 was tiny and I doubt it broke something.  But
>>> maybe you're running into #1021125: liblinphone10:amd64 5.0.37-6 is
>>> already linked against soci/4.0.3-1, but liblime0 5.0.37+dfsg-4 is
>>> still linked against soci/4.0.1-5 and there was an ABI break.  You'd
>>> have to downgrade to 5.0.37-5 and soci 4.0.1-5 and wait until either
>>> that bug gets fixed or lime will be rebuilt and reuploaded.
>>
>> Shall we just do a new upload of liblime0 then?
> 
> That would be nice.

no-change upload 5.0.37+dfsg-5 has been uploaded.

> 
>> liblime and linphone are the only reverse dependencies in the archive, and
>> linphone has already been rebuilt against the new version/ABI. I doubt one
>> can fix the soci ABI bump without breaking linphone again, so we could just
>> go forward and rebuild lime.
> 
> While it would make addressing #1021125 less urgent, that bug still
> needs to be fixed eventually for Bookworm.  Otherwise people might
> falsely assume they can stay on soci 4.0.1 while upgrading
> liblinphone10 and liblime0 to 5.0.37 (or their 5.1 successors).
> Having it fixed before the linphone-stack 5.1/4.4 uploads would save
> work.

I don't think that's a problem. soci does not ship .shlibs, so the 
autogenerated dependency is already bumped to the new upstream version 
 >= 4.0.3 on a rebuild. So right now liblime0 is depending on >= 4.0.1, 
and liblinphone on >= 4.0.3. You cannot upgrade to linphone 5.0.37-6 
while staying on libsoci 4.0.1.

Bernhard