[MDEV-13314] Fedora libmariadb.so.3 issues tracker Created: 2017-07-13  Updated: 2020-12-08  Resolved: 2017-11-10

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.2.6, 10.2.7
Fix Version/s: 10.2.10

Type: Bug Priority: Critical
Reporter: Michal Schorm Assignee: Georg Richter
Resolution: Fixed Votes: 0
Labels: None
Environment:

Fedora Rawhide (27)


Issue Links:
Relates
relates to MDEV-13327 my_getopt.h includes my_default.h , b... Open

 Description   

Hello!
I will use this ticket as a tracker of problems and issues we'll meet when packing MariaDB 10.2 into Fedora.

The library update creates number of issues in many packages that depends on it and that's what we are solving now.

Currently we work with 10.2.6, but 10.2.7 update is planned in days.



 Comments   
Comment by Michal Schorm [ 2017-07-13 ]

First one:
It seems, you stopped exproting the "my_init()" symbol. Is that expected?
Is it true that its functionality is now provided by mysql_init ?

Solving this one here rhbz#1470642, take a look at the attachement.

Comment by Honza Horak [ 2017-07-13 ]

Another question is about load_defaults symbol – my understanding is that people used load_defaults basically for loading additional groups in most cases, which is correctly done by mysql_options(conn, MYSQL_READ_DEFAULT_GROUP, "<mygroup>"); now – is that explanation correct or at least close to correct?

Comment by Adam Williamson [ 2017-07-14 ]

The load_defaults / my_load_defaults thing actually seems rather odd to me: those symbols aren't documented as having been removed in 10.2, AFAICS, and they're in the same header file in 10.1 and 10.2 (private/my_default.h) . Yet somehow they're available when building against 10.1 and not when building against 10.2.

(also, my_getopt.h - which is a public header - includes my_default.h - which is a private header...I filed MDEV-13327 on that).

Comment by Sergei Golubchik [ 2017-10-04 ]

Yes, the patch (from the rhbz#1470642 comment 10) looks correct.

mschorm, shall I keep this issue open for more Fedora libmariadb.so.3 issues? Or it's ok to close it?

Comment by Michal Schorm [ 2017-11-08 ]

At this point, Fedora bug tracker for libmariadb.so.3 issues has been fully resolved and closed.
I still have an open tracker for Fedora change - using library from C/C instead of server one (using separate packages) and I have very few issues open there, which could be potentialy related.

I'd suggest either to:
drop this JIRA issue priority to Minor and leave it open
or
close this issue and if I'd hit some, I'll open a new issue.

I'm equally fine with both. The issues seems to be fixed, but I still have work for weeks ahead, which could be pontentialy related.

Generated at Thu Feb 08 08:04:36 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.