registry team mailing list archive

[Clint Byrum <clint@xxxxxxxxxx>]

After discussing this at length with Mathias Gug today, we've agreed
that this is too much change for very little benefit this close to the
release.

The only risk is that developers who compile 3rd party apps on lucid,
apps that use the error enums, may get unexpected results on maverick,
and vice versa.

As such, well be leaving libdbi 0.8.3 in Maverick, and suggesting a
release note be added so developers can be informed of the issue.


** Description changed:

+ RELEASE NOTE FOR MAVERICK
+ 
+ ===
+ 
+ The version of libdbi (0.8.3) has a known ABI incompatibility with
+ earlier versions of libdbi that have been distributed with past versions
+ of Ubuntu and Debian. As such, any software linked against libdbi.so.0
+ may give unexpected results if they utilize the 'dbi_error_flag' enum.
+ Recompiling these applications will resolve this issue.
+ 
+ ===
+ 
  This was found in Debian this past week, and affects our 0.8.3 package
  as well.
  
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594607
  
  From the debian bug report:
  
  The diff between libdbi 0.8.2 and 0.8.3 includes this:
  
-  /* other type definitions */
-  typedef enum {
- -  DBI_ERROR_USER = -1, DBI_ERROR_NONE = 0, DBI_ERROR_DBD, DBI_ERROR_BADOBJECT, 
+  /* other type definitions */
+  typedef enum {
+ -  DBI_ERROR_USER = -1, DBI_ERROR_NONE = 0, DBI_ERROR_DBD, DBI_ERROR_BADOBJECT,
  -  DBI_ERROR_BADTYPE, DBI_ERROR_BADIDX, DBI_ERROR_BADNAME, DBI_ERROR_UNSUPPORTED
- , 
+ ,
  -  DBI_ERROR_NOCONN, DBI_ERROR_NOMEM, DBI_ERROR_BADPTR
  +  DBI_ERROR_USER = -10, /* must be the first in the list */
  +  DBI_ERROR_DBD = -9,
- +  DBI_ERROR_BADOBJECT, 
+ +  DBI_ERROR_BADOBJECT,
  +  DBI_ERROR_BADTYPE,
  +  DBI_ERROR_BADIDX,
  +  DBI_ERROR_BADNAME,
- +  DBI_ERROR_UNSUPPORTED, 
+ +  DBI_ERROR_UNSUPPORTED,
  +  DBI_ERROR_NOCONN,
  +  DBI_ERROR_NOMEM,
  +  DBI_ERROR_BADPTR,
  +  DBI_ERROR_NONE = 0,
  +  DBI_ERROR_CLIENT
-  } dbi_error_flag;
+  } dbi_error_flag;
  
  which changes the values of various error constants.  That's an
  incompatible ABI change, and should therefore have come with a SONAME
  change, AFAICT.

-- 
libdbi0: ABI breakage without package name change
https://bugs.launchpad.net/bugs/625882
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.