Bug 113681
Summary: | Mysql not current on ES 3? | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Peter Collinson <pc> |
Component: | mysql | Assignee: | Patrick Macdonald <patrickm> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-01-29 15:16:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Peter Collinson
2004-01-16 15:00:11 UTC
mysql-3.23.58 is the most current version of mysql that Red Hat ships. Why do you think ES3 is not current? It seems reasonable to assume that mysql-3.23.58-1.73 was a later revision than mysql-3.23.58-1. If this is not the case, then fine and I obviously need a lesson in the numbering scheme. I seem to recall that there were several changes to mysql on 7.3 and wondered if they had been applied to the version shipped with ES. Also, on 7.3 mysql runs as several processes - whilst on ES it is a single process - it was this aspect that I was wondering about. I see the confusion. On packages for supported (but not current) OS levels, we postfix with the OS level. mysql-3.23.58-1.73 is mysql-3.23.58-1 for RHL 7.3. Both have been built using the same spec file with the same switches. OK - many thanks for your time. |