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, - 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_BADTYPE, + DBI_ERROR_BADIDX, + DBI_ERROR_BADNAME, + DBI_ERROR_UNSUPPORTED, + DBI_ERROR_NOCONN, + DBI_ERROR_NOMEM, + DBI_ERROR_BADPTR, + DBI_ERROR_NONE = 0, + DBI_ERROR_CLIENT } 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.
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 */ BADOBJECT, UNSUPPORTED BADOBJECT, UNSUPPORTED,
typedef enum {
- DBI_ERROR_USER = -1, DBI_ERROR_NONE = 0, DBI_ERROR_DBD, DBI_ERROR_
- DBI_ERROR_BADTYPE, DBI_ERROR_BADIDX, DBI_ERROR_BADNAME, DBI_ERROR_
,
- 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_
+ DBI_ERROR_BADTYPE,
+ DBI_ERROR_BADIDX,
+ DBI_ERROR_BADNAME,
+ DBI_ERROR_
+ DBI_ERROR_NOCONN,
+ DBI_ERROR_NOMEM,
+ DBI_ERROR_BADPTR,
+ DBI_ERROR_NONE = 0,
+ DBI_ERROR_CLIENT
} 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.