Re: New libmysqlclient transition necessary
Hello
On 2006-03-16 Steve Langasek wrote:
> > > > During the last month I have build my libmysqlclient15 with
> > > > shared symbols that looked in "objdump -T" like:
> > > > 0013a154 g DO .bss 00000004 MYSQL_5.0 my_dont_interrupt
> > > > 00026d70 g DF .text 000002fa MYSQL_5.0 my_strntoll_8bit
> > > > 00015730 g DF .text 00000025 MYSQL_5.0 my_no_flags_free
>
> > > > Now MySQL finally closed my bug report to them and provides symbols
> > > > in their upstream source. Sadly they look like:
> > > > 0000f280 g DF .text 0000000b libmysqlclient_15 mysql_row_tell
> > > > 0000f4d0 g DF .text 00000043 libmysqlclient_15
> > > > mysql_escape_string 0000da30 g DF .text 000000e1
> > > > libmysqlclient_15 mysql_slave_send_query
> > ...
> > > Yes, this is a backwards-incompatible ABI change. If libmysqlclient15
> > > had been present in sarge, such a change without a rename of the
> > > library package would be a release-critical bug for etch; since it
> > > wasn't, it's only severity: important, but either way all packages
> > > built against the previous symbol versions would have a
> > > release-critical bug requiring a rebuild.
The source package mysql-dfsg-5.0 5.0.19-2 is now in unstable and build on
all archs except m68k. It's now your turn to schedule the binNMU mechanism,
right?
The resulting binaries should end up linked against "libmysqlclient15off".
bye,
-christian-
Reply to: