MySQL5 and associated packages are now available in the c4-testing repository for i386 and x86_64. It should be fully compatible with current centos4 packages requiring mysql, such as php-mysql etc. Feedback is appreciated.
c4-testing repository located here -> http://dev.centos.org/centos/4/
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Fri, 2005-12-02 at 11:58 -0500, Jim Perrin wrote:
MySQL5 and associated packages are now available in the c4-testing repository for i386 and x86_64. It should be fully compatible with current centos4 packages requiring mysql, such as php-mysql etc. Feedback is appreciated.
c4-testing repository located here -> http://dev.centos.org/centos/4/
does this include the perl, python and php mysql/db modules?
-sv
On 12/2/05, seth vidal skvidal@phy.duke.edu wrote:
On Fri, 2005-12-02 at 11:58 -0500, Jim Perrin wrote:
MySQL5 and associated packages are now available in the c4-testing repository for i386 and x86_64. It should be fully compatible with current centos4 packages requiring mysql, such as php-mysql etc. Feedback is appreciated.
c4-testing repository located here -> http://dev.centos.org/centos/4/
does this include the perl, python and php mysql/db modules?
As far as I've tested, yes. The updated mysqlclient* rpms seem to be doing a fine job of making things work. If something breaks I'd like to know about it.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Fri, 2005-12-02 at 13:08 -0500, Jim Perrin wrote:
On 12/2/05, seth vidal skvidal@phy.duke.edu wrote:
On Fri, 2005-12-02 at 11:58 -0500, Jim Perrin wrote:
MySQL5 and associated packages are now available in the c4-testing repository for i386 and x86_64. It should be fully compatible with current centos4 packages requiring mysql, such as php-mysql etc. Feedback is appreciated.
c4-testing repository located here -> http://dev.centos.org/centos/4/
does this include the perl, python and php mysql/db modules?
As far as I've tested, yes. The updated mysqlclient* rpms seem to be doing a fine job of making things work. If something breaks I'd like to know about it.
Happen to have run repoclosure against centos 4.2 + these packages to see if we have any unresolved deps?
-sv
On 12/2/05, seth vidal skvidal@phy.duke.edu wrote:
On Fri, 2005-12-02 at 13:08 -0500, Jim Perrin wrote:
On 12/2/05, seth vidal skvidal@phy.duke.edu wrote:
On Fri, 2005-12-02 at 11:58 -0500, Jim Perrin wrote:
MySQL5 and associated packages are now available in the c4-testing repository for i386 and x86_64. It should be fully compatible with current centos4 packages requiring mysql, such as php-mysql etc. Feedback is appreciated.
c4-testing repository located here -> http://dev.centos.org/centos/4/
does this include the perl, python and php mysql/db modules?
As far as I've tested, yes. The updated mysqlclient* rpms seem to be doing a fine job of making things work. If something breaks I'd like to know about it.
Happen to have run repoclosure against centos 4.2 + these packages to see if we have any unresolved deps?
-sv
I did. They're clean. A wee bit distrusting are we? :-P
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Fri, 2005-12-02 at 14:13 -0500, Jim Perrin wrote:
On 12/2/05, seth vidal skvidal@phy.duke.edu wrote:
On Fri, 2005-12-02 at 13:08 -0500, Jim Perrin wrote:
On 12/2/05, seth vidal skvidal@phy.duke.edu wrote:
On Fri, 2005-12-02 at 11:58 -0500, Jim Perrin wrote:
MySQL5 and associated packages are now available in the c4-testing repository for i386 and x86_64. It should be fully compatible with current centos4 packages requiring mysql, such as php-mysql etc. Feedback is appreciated.
c4-testing repository located here -> http://dev.centos.org/centos/4/
does this include the perl, python and php mysql/db modules?
As far as I've tested, yes. The updated mysqlclient* rpms seem to be doing a fine job of making things work. If something breaks I'd like to know about it.
Happen to have run repoclosure against centos 4.2 + these packages to see if we have any unresolved deps?
-sv
I did. They're clean. A wee bit distrusting are we? :-P
no distrusting of you. :) distrusting of stuff not breaking :)
-sv
seth vidal wrote:
On Fri, 2005-12-02 at 11:58 -0500, Jim Perrin wrote:
MySQL5 and associated packages are now available in the c4-testing repository for i386 and x86_64. It should be fully compatible with current centos4 packages requiring mysql, such as php-mysql etc. Feedback is appreciated.
c4-testing repository located here -> http://dev.centos.org/centos/4/
does this include the perl, python and php mysql/db modules?
Hi Seth,
No, these pkgs do not contain the perl, python, php etc mysql/db modules - but we've rebuilt and updated the libmysqlclient libraries that the mysql/db functions in these languages use - so that we can maintain compatibility without having to rebuilt pretty much everything!
Maybe some details here might come in handy : http://bugs.centos.org/view.php?id=1124
- K
Jim Perrin wrote:
MySQL5 and associated packages are now available in the c4-testing repository for i386 and x86_64. It should be fully compatible with current centos4 packages requiring mysql, such as php-mysql etc. Feedback is appreciated.
Q: What is the main benefit of running these packages (incl. the old), over running the vendor RPM packages available from dev.mysql.com ? Is it a MySQL "Community Edition" versus "Red Hat Edition" thing ?
(Assuming that a similar "mysqlclient14" package is added, that is)
On a side note, I have made a similar "pq3" package for upgrading from PostgreSQL 7.x to PostgreSQL 8.x - how would I go about to submit this RPM as an enhancement package to the CentOS project ?
(it provides the old /usr/lib/libpq.so.3, for package compatibility)
--anders
Anders F Björklund wrote:
Jim Perrin wrote:
MySQL5 and associated packages are now available in the c4-testing repository for i386 and x86_64. It should be fully compatible with current centos4 packages requiring mysql, such as php-mysql etc. Feedback is appreciated.
Q: What is the main benefit of running these packages (incl. the old), over running the vendor RPM packages available from dev.mysql.com ? Is it a MySQL "Community Edition" versus "Red Hat Edition" thing ?
the main benefit would be to have this s/w in a yum repository - and to have it updated for bug fix's and security updates ( perhaps not as much or as fast as the core pkgs would be - but you will not be left dangling with these pkgs either )
On a side note, I have made a similar "pq3" package for upgrading from PostgreSQL 7.x to PostgreSQL 8.x - how would I go about to submit this RPM as an enhancement package to the CentOS project ?
(it provides the old /usr/lib/libpq.so.3, for package compatibility)
Excellent!
Upload the .src.rpm's somewhere on the net and drop an email here to the list. What we might also need, along with this package, is the entire pgsql rpm set - so that people can just enable the repl, and yum update to pgsql 8.
- K
Karanbir Singh wrote:
On a side note, I have made a similar "pq3" package for upgrading from PostgreSQL 7.x to PostgreSQL 8.x - how would I go about to submit this RPM as an enhancement package to the CentOS project ? (it provides the old /usr/lib/libpq.so.3, for package compatibility)
Excellent!
Upload the .src.rpm's somewhere on the net and drop an email here to the list. What we might also need, along with this package, is the entire pgsql rpm set - so that people can just enable the repl, and yum update to pgsql 8.
It's based on the original postgresql package, so for that I used: http://mirror.centos.org/centos-4/4.2/os/SRPMS/postgresql-7.4.8 -1.RHEL4.1.src.rpm
The new spec file for the compat lib can be found at this location: http://www.algonet.se/~afb/rpm/pq3.spec
Also needs a similar package for CentOS 3, using the 7.3.10 RPM (still TODO) http://mirror.centos.org/centos-3/3.6/os/SRPMS/rh-postgresql-7.3.10 -2.src.rpm
And for the updated PostgreSQL 8.x RPMS, I used the vendor's packages: http://www.postgresql.org/ftp/binary/ (there are SRPMS in there too, despite the "binary" directory name...)
BTW; I'm pretty sure you need to do a full database dump before doing such a major upgrade, but it's been a while since I tried.
But the PostgreSQL documentation should say all about that issue. http://www.postgresql.org/docs/faqs.FAQ.html#item3.6
--anders