Bug #21352
closedlibrados version should bump major number when ABI changes
0%
Description
Our dev team noticed that the librados2 version didn't bump even though luminous changed the ABI. We have binaries compiled against kraken which accepted to run with the librados2 from luminous, which then leads to a segfault.
Should we instead do librados12, etc. as is common?
Updated by Greg Farnum over 6 years ago
We suck at bumping librados versions. It probably needs to go into a pre-release checklist. :/
If you send a patch soon bumping the version I imagine it will go into 12.2.1.
Updated by Dan van der Ster over 6 years ago
Is it that simple? I imagine bumping to librados3 mid-release would cause untold mess downstream. Does this need to be coordinated with distros?
Updated by Josh Durgin over 6 years ago
Dan, which symbols are you seeing changed? Could you get a backtrace of the segfault? There shouldn't have been any incompatible changes with the C abi, though oversights are quite possible. The c++ abi on the other hand is more difficult to preserve, since things like switching compilation mode change the abi.
Updated by Kefu Chai over 6 years ago
- Status changed from New to Duplicate
Dan, please reopen this ticket if i am wrong.
Updated by Kefu Chai over 6 years ago
- Is duplicate of Bug #21573: [upgrade] buffer::list ABI broken in luminous release added