RE: [cobalt-users] [RAQ3] .pkg install failure - where are the error logs?

["Andy Brown" <andy.brown@xxxxxxxxxxxxx>]

<snip>
> [root@ns mysql]# ls -ltr
> total 26569
> -rw-rw-r--   1 root     admin     2124034 Apr 13  2001 
> MySQL-client-3.22.32-1.i386.rpm
> -rw-rw-r--   1 root     admin     4915122 Apr 13  2001 
> MySQL-3.22.32-1.i386.rpm
> -rw-rw-r--   1 root     admin      631939 Apr 13  2001 
> MySQL-devel-3.22.32-1.i386.rpm
> -rw-rw-r--   1 root     admin      186217 Apr 13  2001 
> MySQL-shared-3.22.32-1.i386.rpm
> -rw-rw-r--   1 root     admin      721863 Apr 13  2001 
> php-manual-3.0.16-2C2.i386.rpm
> -rw-rw-r--   1 root     admin       38580 Apr 13  2001 
> php-mysql-3.0.16-2C2.i386.rpm
> -rw-rw-r--   1 root     admin      295676 Apr 13  2001 
> php-3.0.16-2C2.i386.rpm
> -rw-rw-r--   1 root     admin     9438535 Apr 13  2001 
> glibc-2.1.3-15C1.i386.rpm
> -rw-rw-r--   1 root     admin     8732989 May 11  2001 
> RaQ3-RaQ4-MySQL-3.23.37-1.pkg
> [root@ns mysql]# /usr/local/sbin/cobalt_upgrade 
> RaQ3-RaQ4-MySQL-3.23.37-1.pkg
> 4015 Problem installing package component: MySQL-3.23.37-1.i386.rpm
> 4015 Error in installation script upgrade_me
> [root@ns mysql]# rpm -q MySQL
> package MySQL is not installed
> 
> 
> >
> >So it will throw out the error (if any) to your shell 
> prompt. That might help get you moving along.
> >
> >It could be because of a previously failed RPM installation, so do:
> >rpm -q MySQL
> 
> 
> Yes, I found a previously botched MySQL install which I can't 
> ever remember attempting - it was a 3.22.32 install - so I 
> removed it using:
> 
> rpm -i MySQL-3.22.32
</snip>

Hi,
Couple of things straight away here. rpm -i does INSTALL not uninstall, to remove a package you should use this:
rpm -e MySQL-3.22.32

But since you've deleted the /home/mysql and other things it probably won't work so you might need to do:
rpm -e --nodeps --noscripts MySQL-3.22.32

The other thing I noticed is you've got a few mysql rpm's in there too. Make sure you don't have these installed, otherwise its going to get a lot of conflicts every time.

My suggestion is to query the rpm database several times, doing the correct erase command to remove the faulty rpm's, then try the .pkg again.

Regards,

Andy
andy@xxxxxxxxxx
http://www.raqpak.com  <-- Unofficial FAQs and PKGs