On Friday 14 June 2002 05:43 am, pgsql-bugs(at)postgresql(dot)org wrote:
> Short Description
> corrupt rpms
> Long Description
> Your redhat-6.2 rpms for postgresql latest trashed my rpm database and
> corrupted it which was unfixable and now have no ability to utilize the use
> of rpm, which had been operating for 4+years on this box, i can't believe
> this, that a well utilized site as this does this poor job maintaining
> their files, thanks for the devastation. Even tryed going back to my
> version and was unfixable.
What version of RPM are you using? Did you get and install the Red
Hat-recommended update to RPM 4? As you are the only one who has reported
this, and a number of people have downloaded and are using those RPM's
without any problem, I suspect a problem with your box.
Although Red Hat 6.2 hasn't been out for 4 years.
You didn't try to install the sparc RPM's, did you?
What program did you use to download the RPMset?
Your error report indicated PostgreSQL 7.0.3. This is not the latest version;
the latest is 7.2.1, which for Red Hat 6.2 is only available as the source
RPM or as SPARC32 RPM's. I don't have a Red Hat 6.2 Intel machine; but the
source RPM build works on Red Hat 6.2 for SPARC (and I have reports that it
rebuilds just fine on Red Hat 6.2/Intel from more than one source).
Besides all that, a corrupt RPM won't trash the RPM database. There is
something else going on there. A corrupt RPM will fail the installation. It
sounds to me like your RPM installation got hosed either due to a hardware
fault or running out of disk space on the /var partition. I certainly
reserve the right to be wrong; but to test this theory run 'rpm --rebuilddb'
and see what happens.
WGCR Internet Radio
1 Peter 4:11
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2002-06-14 22:42:39|
|Subject: Re: pg_dump fails for views with UNION and SELECT DISTINCT |
|Previous:||From: pgsql-bugs||Date: 2002-06-14 09:43:17|
|Subject: Bug #692: corrupt rpms|