Bug#759309: [debian-mysql] Bug#759309: Bug#759309: Must not Provide: libmysqlclient-dev
Package: libmariadbclient-dev 2014-08-26 15:52 GMT+03:00 Kristian Nielsen kniel...@knielsen-hq.org: But if I understand correctly, now it is possible to install packages libmariadbclient and package libmysqlclient-dev at the same time. So the problem should no longer apply. Yes, libmysqlclient-dev is co-installable with libmariadbclient18. The package libmysqlclient-dev (and by extension also libmysqld-dev) is not co-installable with libmariadbclient-dev. Also note that the MariaDB LGPL client version passed the NEW queue yesterday and now these new pacakges are available in experimental: libmariadb-client-lgpl-dev, libmariadb-client-lgpl-dev-compat, libmariadb2 I have decided to simply remove the Provides line as requested, and despite mariadb-client-lgpl in experimental now, I will not haste to remove the mariadb-5.5 source package generated libmariadbclient package completely yet. I also removed the identical Provides line in libmariadbd-dev with the same motivations described in this bug report. The fix is now committed in: http://anonscm.debian.org/cgit/pkg-mysql/mariadb-5.5.git/commit/?id=bc637404c6d7bd30803f08013615d1fec160b049 Note: My sponsor hasn't responded to e-mail for some days now and seems busy -- if you are a DD following this issue and think it really is grave, feel free to do a non-maintainer upload of 5.5.39-2 to get the fix out quickly. The source repo is listed above and the packaging release process documented in debian/README.Maintainer if you are unfamiliar with this git repo layout. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759309: [debian-mysql] Bug#759309: Bug#759309: Must not Provide: libmysqlclient-dev
Otto Kekäläinen o...@seravo.fi writes: Upstream MariaDB only ships with libmysqlclient.so, while I have changed the Debian version to ship the library using the name libmariadbclient.so, because I got feedback that it is not good policy for the MariaDB package to ship a so name that also exists in another It seems to me that based on this, it would be reasonable to drop the Provides: libmysqlclient-dev for the native Debian packages of libmariadbclient-dev. If a Debian package wants to build with the MariaDB client library, it can use libmariadbclient-dev as a build dependency. If it wants to use the Oracle/MySQL client library, it can use libmysqlclient-dev instead. It actually seems to be wrong for one -dev package to Provide: the other, doesn't it? In the third-party repository packages, we had the Provides: libmysqlclient-dev. This was necessary, because the real libmysqlclient-dev package was not co-installable with libmariadbclient. So it became impossible to build any package that depended on libmysqlclient-dev without uninstalling the MariaDB server; the Provides: libmysqlclient-dev solves this. But if I understand correctly, now it is possible to install packages libmariadbclient and package libmysqlclient-dev at the same time. So the problem should no longer apply. (libmariadbclient-dev and libmysqlclient-dev are not co-installable, but it is my understanding that this is not a problem as such, as it is only a build dependency, not a runtime dependency). Hope this helps, - Kristian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759309: [debian-mysql] Bug#759309: Bug#759309: Must not Provide: libmysqlclient-dev
On Tue, Aug 26, 2014 at 02:52:34PM +0200, Kristian Nielsen wrote: Otto Kekäläinen o...@seravo.fi writes: Upstream MariaDB only ships with libmysqlclient.so, while I have changed the Debian version to ship the library using the name libmariadbclient.so, because I got feedback that it is not good policy for the MariaDB package to ship a so name that also exists in another It seems to me that based on this, it would be reasonable to drop the Provides: libmysqlclient-dev for the native Debian packages of libmariadbclient-dev. If a Debian package wants to build with the MariaDB client library, it can use libmariadbclient-dev as a build dependency. If it wants to use the Oracle/MySQL client library, it can use libmysqlclient-dev instead. It actually seems to be wrong for one -dev package to Provide: the other, doesn't it? Definitely, *unless* you're actually providing a cleanly compatible implementation in all respects - headers, libraries, API and ABI. If you're not, then don't pretend to be in the packaging system. -- Steve McIntyre, Cambridge, UK.st...@einval.com Support the Campaign for Audiovisual Free Expression: http://www.eff.org/cafe/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
