Bug #34231 | libmysqlclient contains libz in MySQL-devel-community-5.1.22-0.rhel3.i386.rpm | ||
---|---|---|---|
Submitted: | 1 Feb 2008 14:29 | Modified: | 19 Mar 2008 16:36 |
Reporter: | Helmut Wirth | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server: Packaging | Severity: | S2 (Serious) |
Version: | 5.1, 5.0, 6.0 | OS: | Linux |
Assigned to: | Alexander Nozdrin | CPU Architecture: | Any |
[1 Feb 2008 14:29]
Helmut Wirth
[13 Feb 2008 15:52]
Susanne Ebrecht
Verified as described using bk tree for MySQL 5.0.58, 5.1.24-rc and 6.0.5
[19 Mar 2008 15:12]
Georgi Kodinov
I think it's a good idea to use a specific zlib version for stability and compatibility reasons. And since it's not complicated to build from source (and use another value for --with-zlib-dir) I don't think we're going to change the way we build our binaries.
[19 Mar 2008 16:30]
Helmut Wirth
But so the main issue remains - rebuilding php on RHEL5 / CentOS5 (even from the original distribution src rpms) will fail when the original mysql-devel-community packages are installed. I'm aware that this could be fixed through changing the php build configuration, but is this really the way to go (breaking the default build of distribution packages?)
[19 Mar 2008 16:36]
Helmut Wirth
But so the main issue remains - rebuilding php on RHEL3 / CentOS3 (even from the original distribution src rpms) will fail when the original mysql-devel-community packages are installed. I'm aware that this could be fixed through changing the php build configuration, but is this really the way to go (breaking the default build of distribution packages?)
[15 Jul 2008 17:39]
Kevin Regan
We are running into the same issue when compiling the MySQL++ package. It seems like a bad idea to force all downstream packages to change the way they build.
[15 Jul 2008 17:51]
Daniel Fischer
I'm sorry, but we can't influence how dependent packages are built. If you find that a package that depends on MySQL doesn't work, please report a bug to its maintainer. We have been including libz for a long time now, this isn't something that has changed overnight three months ago.
[15 Jul 2008 17:55]
Kevin Regan
Well, 5.0.45 works, whereas later versions don't. That does seem like an overnight change. This is going to cause a lot of pain to a lot of people.
[15 Jul 2008 18:02]
Kevin Regan
Actually, the 5.0.51a version was working for us as well. The current version on your website is 5.0.51b. So, it is quite likely that folks won't notice this until you bump up the 5.0.x community addition to the version that contains this issue (we are seeing it in 5.0.64).