On Wed, 2005-02-23 at 00:59 +0100, Rene Bon Ciric (Renich) wrote: This is because the latest version of sqlite in the repositories you have configured (the FC3 default repositories) is version 2.8. Yes, that's right. And if sqlite3 requires a later version of something, you may need to build that too... sqlite3-3.0.8-3.src.rpm is in the development repo alongside the other SRPMS you downloaded. You're getting the hang of this now, aren't you ;-) Paul. -- Paul Howarth <paul(a)city-fan.org&gt;

Graham Cossey wrote: Maybe you can; but if you use the ones from the development repo, you'll get them packaged "the fedora way", and a sunsequent upgrade to FC4 will present fewer surprises. Paul.

Ok guys, here is the status First of all, thank you all for your help, I've managed to get this far just beacause of your help! I promise i'm gonna make a great howto when we're done! I've managed to build these RPM's with rpmbuild --rebuild package Mysql - mysql-4.1.9-1.i386.rpm - mysql-bench-4.1.9-1.i386.rpm - mysql-debuginfo-4.1.9-1.i386.rpm - mysql-devel-4.1.9-1.i386.rpm - mysql-server-4.1.9-1.i386.rpm PHP - php-5.0.3-2.i386.rpm - php-debuginfo-5.0.3-2.i386.rpm - php-devel-5.0.3-2.i386.rpm - php-gd-5.0.3-2.i386.rpm - php-imap-5.0.3-2.i386.rpm - php-ldap-5.0.3-2.i386.rpm - php-mbstring-5.0.3-2.i386.rpm - php-mysql-5.0.3-2.i386.rpm - php-ncurses-5.0.3-2.i386.rpm - php-odbc-5.0.3-2.i386.rpm - php-pear-5.0.3-2.i386.rpm - php-pgsql-5.0.3-2.i386.rpm - php-snmp-5.0.3-2.i386.rpm - php-soap-5.0.3-2.i386.rpm - php-xml-5.0.3-2.i386.rpm - php-xmlrpc-5.0.3-2.i386.rpm SQLite - sqlite3-3.0.8-3.i386.rpm - sqlite3-debuginfo-3.0.8-3.i386.rpm - sqlite3-devel-3.0.8-3.i386.rpm I tried installing MySQl first and recieved this message: #>rpm -hUv mysql-4.1.9-1.i386.rpm error: Failed dependencies: libmysqlclient.so.10 is needed by (installed) perl-DBD-MySQL-2.9003-5.i386 libmysqlclient.so.10 is needed by (installed) mod_auth_mysql-20030510-5.i386 libmysqlclient.so.10 is needed by (installed) cyrus-sasl-sql-2.1.19-3.i386 libmysqlclient.so.10 is needed by (installed) libdbi-dbd-mysql-0.6.5-9.i386 libmysqlclient.so.10 is needed by (installed) qt-MySQL-3.3.3-8.i386 libmysqlclient.so.10 is needed by (installed) gda-mysql-1.0.4-3.i386 libmysqlclient.so.10 is needed by (installed) freeradius-mysql-1.0.1-1.i386 libmysqlclient.so.10 is needed by (installed) php-mysql-4.3.10-3.2.i386 libmysqlclient.so.10 is needed by (installed) dovecot-0.99.13-3.FC3.i386 libmysqlclient.so.10 is needed by (installed) mysql-server-3.23.58-14.i386 libmysqlclient.so.10 is needed by (installed) MyODBC-2.50.39-19.1.i386 libmysqlclient_r.so.10 is needed by (installed) MySQL-python-0.9.2-4.i386 mysql = 3.23.58 is needed by (installed) mysql-server-3.23.58-14.i386 mysql = 3.23.58 is needed by (installed) mysql-devel-3.23.58-14.i386 mysql = 3.23.58 is needed by (installed) mysql-bench-3.23.58-14.i386 Well... i've done a rpm -q on all the packages listed to see if i have them and i do... then i took a second look and deducted that i need libmysqlclient.so.10 ... is that available in the same dev dir? maybe... i'll go see.. Thats all for the update. Phase 1 .- Building the RPM's DONE! :-D Phase 2 .- Solving dependencies... IN PROGRESS Phase 3 .- Installation PENDING Phase 4 .- Testing PENDING Comments, suggestions... ? -- This is an email sent via the webforum on http://fcp.homelinux.org

I have uploaded the rpmbuild output to my webpage, in case anyone wants to check it out http://www.woralelandia.com/build-output/ -- This is an email sent via the webforum on http://fcp.homelinux.org

On Wed, 2005-02-23 at 22:51 +0100, Rene Bon Ciric (Renich) wrote: You might want to try upgrading all the mysql packages at once.... Put all the rpm's that you built for mysql in one directory and then do a rpm -Uvh *.rpm from that directory and see if the newer version of mysql will help to resolve the "conflict" with the mysqlclient10 package.... HTH, --Rob

On Wed, 2005-02-23 at 21:06 -0600, Christofer C. Bell wrote: I was going to ask the same question but notice that the package names are actually different. It looks like the packaging of the rpm's may have changed between mysql v3 and v4 that he is heading towards. Notice that the "new" files are trying to be installed from a package named mysqlclient10 versus the old packaging that had them as part of mysql.... So while the base version of each is eerily identical 3.23.58, the extraversion on the mysqlclient10 is a smaller number (4) versus the older packaging that had the larger number (14). But the error is actually a complaint of a conflict between package names not versions. Of course, this apparent packaging change is why I suggested that he use rpm -Uvh earlier rather than the other suggestion of using rpm -Fvh. I am assuming that he may not have a package named mysqlclient10 currently installed and hence the F would not install it.... Of course, I don't use mysql so could be talking out my proverbial... oops, need to keep it G rated... :-) --Rob

Rene Bon Ciric (Renich) wrote: You can safely get rid of these directories. You will notice that this shows that your PHP is built against the Client API version 3.23.58 for mysql, which is probably not what you wanted. The reason for this is that you built your PHP packages before you installed your updated MySQL packages. You might not like hearing this, but I would rebuild your PHP package if I was you. Once built, you'll be able to install them using: # rpm -Uvh --replacefiles --replacepkgs php*.rpm If you want to build the mysqli extension too, then you'll need to modify the spec file for the PHP SRPM, which is beyond the scope of this email... Paul.

I don't get tired of thanking you all! Specially the ones that were here from the begining (you can check the thread to see who they are). Im totally grateful. Ok Paul, as always, your wise guideance is always welcome. One thought... Ok, I will rebuild the php5 SRPM... how would I manage to edit the spec file for it if everything is automatic with rpmbuild --rebuild? Ill try to do it, in the mean time, im looking for a way to compile the mysqli.so extension. By the way, for the ones that don't use MySQL... you should give it a try! :-D check out mysql.com... specifically http://www.mysql.com/it-resources/benchmarks/ http://dev.mysql.com/tech-resources/features.html and http://www.mysql.com/consulting/enhancements.html -- This is an email sent via the webforum on http://fcp.homelinux.org

They didn't include Postgresql in their benchmarks :( hicham. Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/

Check out the output files at http://www.woralelandia.com/stuff/ -- This is an email sent via the webforum on http://fcp.homelinux.org http://fcp.homelinux.org/modules/newbb/viewtopic.php?post_id=43801&am...

Rene Bon Ciric (Renich) wrote: Since you rebuilt all of the rpms from source already, I think that the suggestion that Robert made about putting all of the rpms in a single directory and running rpm -Fvh *.rpm if you want to upgrade only rpms that are installed on your system. The F flag does not install the program if it is not already installed on the system. The functionality of rpm should sort the install order and resolve the dependacies with the whole pool of rpms in one directory. If you want to install all of the rpms you built from source, run rpm -Uvh *.rpm from within the directory that contains all the rpms. This should allow rpm to resolve dependacies and package install order. Giving rpm the wildcard symbol ensures that rpm will see all of the pool and do its best to sort out everything. Giving rpm just a certain filename patern will only have rpm try to resolve from the filename patern that was given as the argument. (gn*.rpm will only choose/resolve from rpms with gn something in the names. *.rpm will use all packages available.) Jim

Rene Bon Ciric (Renich) said: [snip] [snip] Grabbing the mysqlclient10 SRPM (also in rawhide) and rebuilding it might get you these. -- William Hooper