2011/12/17 Maarten Vanraes <al...@rmail.be>: > %mklibname works fine, Did you really have tests that if %mklibname works as expected? $ rpm -qp --obsoletes libmariadb18-5.5.18-0.bzr3169.20111216.2.mga2.i586.rpm libmysql18_< $ rpm -qp --provides libmariadb18-5.5.18-0.bzr3169.20111216.2.mga2.i586.rpm mariadb-shared-libs = 5.5.18-0.bzr3169.20111216.2.mga2 mariadb-shared = 5.5.18-0.bzr3169.20111216.2.mga2 libmysql18_= libmysqlclient.so.18 libmysqlclient.so.18(libmysqlclient_16) libmysqlclient.so.18(libmysqlclient_18) libmariadb18 = 5.5.18-0.bzr3169.20111216.2.mga2 libmariadb18(x86-32) = 5.5.18-0.bzr3169.20111216.2.mga2
Please notify the empty version string in provides and obsoletes after "=". > your issue was the bug that mysql-devel wasn't properly > obsoleted... I guess not, having versioned obsoletes makes it possible if we will revert to mysql at some time in the future. > problem is, that you've removed some provides now, so if packages will be > depending on lib64mysql18, it'll not be working now... I don't see any package have direct dep on lib64mysql18 as package name, in cauldron repository. > you also did a wrong obsolete with %{version}-%{release} > > also, if a package has a maintainer, i think policy (or at least common > courtesy) is to speak with maintainer about this? > > and why even submitting amarok, when mikala will bring new KDE soon? Because amarok is a package listed in meta-task, we should make sure most of them at least installing correctly. Due to new mariadb changes libmajor of libmysqld. > i'm resubmitting mariadb That leads to the problems as i said. > you should've just fixed the wrong obsoletes and vendor tag and missing > provides. > > regards,