On Mon, 2017-07-03 at 15:12 +0200, Michal Schorm wrote: > Hello everybody! > > Since MariaDB 10.2 is finally stable and I resolved all issues that blocked > it for Fedora, I'd like to propose an update for Rawhide. > > Current version of MariaDB: 10.1.24 > Update planned to: 10.2.6 (or newer) > > *This change introduces change of library name from "libmysqlclient.so" to > "libmariadb.so".* > *There are many dependant packages affected.* > > The current (optimistic) plan is to deliver the update before Fedora 27 mass > rebuild <https://fedoraproject.org/wiki/Releases/27/Schedule> at 12.7.2017. > Either the rebuild of all depending packages is inevitable. > > - > > We actively track the issue here > <https://bugzilla.redhat.com/show_bug.cgi?id=1467297>. There is also a list > of affected packages. > We have a work repository in COPR, where you can find builds of your > packages here > <https://copr.fedorainfracloud.org/coprs/g/db-sig/mariadb-10.2/packages/>. > > We go through all of the issues and we are trying to solve all of those, > which are caused by the library change. More information will appear in > bugzillas connected to the tracker. > > Issues are also consulted with MariaDB upstream. > I was told, that there should be strong API and ABI compatibility. > > - > > Notes: > - this means also drop of symlinks to "libmysqlclient.so.18.0.0" library. > - the version of the library in MariaDB 10.2.6 is "mariadb.so.3", however > in mariadb-connector-c it is only "mariadb.so.2". That should sync in next > big update in about a month, I believe. > > - > > Feel free to ask any questinos here or in tracker BZ, I'll try to search > for all answers. So this is now happening, but I'm a bit confused - specifically about these two bits from the text: "Either the rebuild of all depending packages is inevitable." "this means also drop of symlinks to "libmysqlclient.so.18.0.0" library" However, the recent mariadb package builds by mschorm - mariadb-10.2.6- 1.fc27 and mariadb-10.2.6-2.fc27 - included symlinks from 'libmariadb.so' to 'libmysqlclient.so' and 'libmysqlclient.so.18'. Which seems to imply that the library *should* still be ABI-compatible with libmysqlclient.so.18 and that things built against that library should *not* need rebuilding. The libmysqlclient.so.18 symlink was initially put in the -devel subpackage, which was clearly wrong, and after discussion with mschorm I moved it to the -libs subpackage. But after reading some more on this I'm really not at all clear on why this symlink exists, whether it was intended to, whether it's *correct* that it exists, whether it's only a temporary stopgap, etc. etc. So I thought I'd send out a mail about the situation so we can discuss it on the public record. There's still a problem with the -3 build I did, with the symlink moved: the -libs package does not automatically get a Provides: for the libmysqlclient.so.18 symlink, for some reason. I *could* do a rebuild with the Provides: manually added, but now I'm unsure whether that's the right thing to do. This is a bit of a problem because it prevents various things from building; the one that got me into this mess is initial-setup , which needs rebuilding to fix a blocker bug, but the build failed because somehow on s390 (only) initial-setup build requires net-snmp and net- snmp requires libmysqlclient.so.18... Can we sort this out, one way or another? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
