Quoting Matthew Gabeler-Lee (2019-08-26 15:42:32) > Indeed, this package needs its dependency on libleveldb1d bumped.
This problem happened while there was no change to bitcoin-qt and while libleveldb1d was upgraded to a newer upstream version. The cause of this problem is therefore likely that libleveldb1d failed to bump its soname. Only if bitcoin-qt is linking beyond the public API of libleveldb1d is bitcoin-qt to blame for this failure. I see no need for bumping any dependencies: A simple rebuild made the package work again, which to me indicates that this is a bug in libleveldb1d. > Updating that package to the version in bullseye/sid fixes this issue. Thanks for the confirmation. > Given its a symbols related issue, arguably that package needs its > soversion bumped? If you mean bumping SOVERSION of bitcoin-qt, then I disagree, and ask you to please elaborate why you think that should be done. If you mean bumping SOVERSION of libleveldb1d then I agree. > #933908 is a dupe of this for the bitcoind binary package. Agreed. Merged now. Thanks! > Given this makes the daemon not launch, it probably merits a severity > bump. Raising severity beyond "important" practically means "if this issue isn't fixed then better to remove the package from the arcive" which arguably doesn't make sense for bitcoin-qt (it works when only the right library is available) but certainly makes sense if reassigned to libleveldb1d (it is suspected that this issue affects other applications too). I have not had time to investigate closer if relevant to reassign, and prefer for now to leave this open but at non-fatal severity, as it is does not affect the 0.18.1~dfsg-1 release. Help investigating closer would be much appreciated. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
