Assigning to all packagers collectively, since the registered maintainer for this package is currently unavailable.

CC'ing the registered maintainer.

If anyone starts working on this: note that there are currently four more bug reports against mariadb
https://bugs.mageia.org/buglist.cgi?f1=cf_rpmpkg&list_id=85585&o1=substring&query_format=advanced&resolution=---&v1=mariadb

Assignee: bugsquad => pkg-bugs
CC: (none) => alien, marja11

Lets see if I can do this. The other bugs are a bit difficult.

CC: (none) => jackal.j
Assignee: pkg-bugs => jackal.j

Added an jira issue because of the compiling issue:
https://jira.mariadb.org/browse/MDEV-14640

issue confirmed

@Jack M: until we have a new version of mariadb, you can add a patch to disable pcre check, so we can compile this version.

I see Fedora has some SPEC adjustments in the update 10.1.29 due to PCRE, and PCRE is preventing me from updating the 10.0.x and 10.1.x branches for Mageia 5 and Mageia 6.  Maybe you can help?

Well, I don't know what to say.. I just helped and/or corrected some pkg'ing issues I saw for unmaintained pkg and now I'm assigned to mariadb bugs. :)

Of course I can try to help with pkg'ing mariadb, but I have very limited knowledge about mariadb and how it should work etc. I can probably provide pkg that builds, but that's all.

Because of all the things I mentioned I'd like to suggest that this bug will be assigned to someone else than me.

Assignee: jani.valimaa => bugsquad

wally: this one is just about packaging. I've verified your latest build, it's ok and as far as tested mariadb works as expected. Just close the bug as you say the packaging is good.

@wally: due to the renaming of the library some packages have to be rebuilt. Since the old package is not available on the mirror anymore, I can't query urpmi --whatrequires 
But on rebuilding php I git the error for devel(libnet-snmp)

You've pushed the updated lib naming to mga6 too. May we get some updating problems here? How do we query what needs a rebuilt?

Rebuilds aren't needed because of the pkg'ing changes I made, but because upstream changed lib major and/or SONAME (which will also affect to lib pkg names). Pkgs would have needed rebuilds even without my changes.

'urpmf --requires libfoo.so.1' tells what pkgs are needing libfoo.so.1. One can use urpmf with old lib names to find out pkgs needing rebuild. Or use http://check.mageia.org/cauldron/dependencies.html.

right, is there option to force rebuild of dependent packages? In my case e.g. the rebuild failed because of another devel package which depended on libmysqlclient.
It would be nice, if it is possible to trigger a rebuild in such a case. It is bunch of packages affected by this.

It would be nice, yes, but basically all pkgs must be done by hand.

I know there're some autobuild scripts to push pkgs automatically, but haven't seen such in public.

Fixed for mga7

Resolution: (none) => FIXED
Status: NEW => RESOLVED