[MONGOCRYPT-460] ABI/API breakage in 1.5.x Created: 18/Jul/22  Updated: 25/Jul/22  Resolved: 25/Jul/22

Status: Closed
Project: Libmongocrypt
Component/s: None
Affects Version/s: 1.5.0, 1.5.1
Fix Version/s: None

Type: Bug Priority: Unknown
Reporter: Remi Collet Assignee: Kevin Albertson
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

According to abi-compliance-checker, 4 symbols were removed from the library

 

See https://rpms.remirepo.net/compat_reports/libmongocrypt/1.4.1_to_1.5.1/compat_report.html

  • mongocrypt_csfle_version ( mongocrypt_t const* crypt )
  • mongocrypt_csfle_version_string ( mongocrypt_t const* crypt, uint32_t* len )
  • mongocrypt_setopt_append_csfle_search_path ( mongocrypt_t* crypt, char const* path )
  • mongocrypt_setopt_set_csfle_lib_path_override ( mongocrypt_t* crypt, char const* path )

 

So, following common practices, the soname should have changed from .0 to .1



 Comments   
Comment by Kevin Albertson [ 25/Jul/22 ]

Thank you for the report. Those symbols were renamed as part of a shared library renamed in MONGOCRYPT-434 to the following:

mongocrypt_csfle_version => mongocrypt_crypt_shared_lib_version
mongocrypt_csfle_version_string => mongocrypt_crypt_shared_lib_version_string
mongocrypt_setopt_append_csfle_search_path => mongocrypt_setopt_append_crypt_shared_lib_search_path
mongocrypt_setopt_set_csfle_lib_path_override => mongocrypt_setopt_set_crypt_shared_lib_path_override

Including them in a release was a goof on our part. But we are confident there are no consumers relying on those symbols.

Generated at Thu Feb 08 09:08:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.