On Fri, 17 Nov 2000, Robert D. Nelson wrote:
> Try uninstalling everything related to postgres that is now installed. Then
> remove /var/lib/pgsql and any data directories that may exist. Start from
> scratch. Oh, and as to order? I just installed them all together, like "rpm
> -ivh postgresql-7.
Rich Shepard wrote:
> Thanks, Lamar. I upgraded the server package, and that appeared to work
> just fine. Then I installed the others. Is 'initdb' the proper way to
> restart everything, and creat a new /var/lib/pgsql? It's been a while since
> I worked with postgres, but I need to really dig i
> I actually do understand the differences among -i (install) -U (upgrade)
>and -F (freshen). What I don't understand is why what _should_ work _isn't_
>working.
>
> For example, as Lamar and others suggested:
>
>[root@salmo rshepard]# rpm -qa | grep postgres
>postgresql-server-6.5.3-1
>postgres
On Fri, 17 Nov 2000, Lamar Owen wrote:
> Once you have verified with rpm -qa|grep postgres that there are no more
> postgresql RPM's on your system, then you will need to clean out the old
> 6.5.3 data directory (rm -rf /var/lib/pgsql).
>
> Now you should be able to install the new RPMset.
Tha
Rich Shepard wrote:
> On Thu, 16 Nov 2000, Lamar Owen wrote:
> > The result of 'rpm -qa|grep postgres' would be educational here.
> [root@salmo rshepard]# rpm -qa | grep postgres
> postgresql-server-6.5.3-1
> postgresql-test-6.5.3-1
> postgresql-7.0.3-2
> "Aha, I said. The rpm database thinks
On Thu, 16 Nov 2000, Lamar Owen wrote:
> The result of 'rpm -qa|grep postgres' would be educational here.
I actually do understand the differences among -i (install) -U (upgrade)
and -F (freshen). What I don't understand is why what _should_ work _isn't_
working.
For example, as Lamar and o
On Wed, 15 Nov 2000, Lamar Owen wrote:
> Use --nodeps to override dependencies. It is complaining because RPM
> apparently has no record of /lib/cpp -- rpm --rebuilddb may be needed.
> RPM's dependencies are not checked against the filesystem, but against
> the RPM database. You can verify this
Rich Shepard wrote:
> So, can someone please explain to me why the 7.0.3-1 package complains
> that /lib/cpp isn't there when it is? FWIW, I got the same error when I
> tried using the --force switch with rpm. Something's screwy here.
Use --nodeps to override dependencies. It is complaining be
Ever since I upgraded to 6.5.2 I've had problems upgrading to the 7.x
series. I'm running Red Hat 6.1 (2.2.17 kernel) on this box.
Now I'm trying to upgrade to 7.0.3 via the rpm. When I tried both the
freshen (-F) and upgrade (-U) switches, I found a failed dependency:
/lib/gcc! and a bunch o
