Bug #3860 | RPM dependancies not met | ||
---|---|---|---|
Submitted: | 22 May 2004 20:57 | Modified: | 26 Aug 2004 12:43 |
Reporter: | Nathanael Noblet | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Packaging | Severity: | S3 (Non-critical) |
Version: | 4.0.20 | OS: | Tao-Linux (RHEL3 clone) |
Assigned to: | Lenz Grimmer | CPU Architecture: | Any |
[22 May 2004 20:57]
Nathanael Noblet
[28 May 2004 7:12]
MySQL Verification Team
I wasn't able for to repeat the behavior reported with the latest RPM source release: MySQL-4.0.20-0.src.rpm on Suse 9.1. Patrick: Could you please comment if it was introduced a fix or modification regarding version 4.0.18. Thanks in advance.
[28 May 2004 18:38]
Nathanael Noblet
I think this may just be a yum / MySQL problem. I recompiled the 4.0.20 src-rpm and got the same messages. I figure it must be a yum problem now, because I can install fine. It is only the yum update command that fails. If the dependancy wasn't being met, rpm -Uvh would fail as well. I'll go bother them, and post again if there is anything needed in the spec file.
[27 Jul 2004 12:27]
[ name withheld ]
I think it's just yum's output that is misleading. The dependencies that are not met are probably either in php-mysql or perl-DBI, depending on what packaged you re-compiled in the process of upgrading MySQL. Adding those packages to yum's exlude list fixes the problem.
[4 Aug 2004 4:27]
Ian Holsman
this can be resolved by having %package Max ... Requires: MySQL-server >= 4.0 instead of Requires: MySQL >= 4.0 ? FWIW.. perl-DBI doesn't require Mysql. # rpm -q --whatrequires MySQL MySQL-Max-4.0.20-0
[25 Aug 2004 20:35]
Patrick Galbraith
Lenz: what is your suggestion/opinion?
[26 Aug 2004 12:43]
Lenz Grimmer
Thanks for noticing this! Hmm, our MySQL-server package includes: Provides: msqlormysql mysql-server mysql MySQL So I would have assumed that this would fulfil the requirement. Anyway, I have now changed it to require "MySQL-server" instead. Fix was pushed into the 4.0 BK tree and will be included in future releases (4.0.21/4.1.4)
[26 Aug 2004 12:43]
Lenz Grimmer
Closing this bug now as fixed.