public inbox for rhdb@sourceware.org
 help / color / mirror / Atom feed
From: Permaine Cheung <pcheung@redhat.com>
To: Lachlan Evans <lachlane@iinet.net.au>
Cc: rhdb@sources.redhat.com
Subject: Re: RHDB 2.1 and RHL 8.0
Date: Sun, 29 Dec 2002 17:49:00 -0000	[thread overview]
Message-ID: <3E0FA680.1000004@redhat.com> (raw)
In-Reply-To: <1040891071.1196.6.camel@chopper>

Lachlan Evans wrote:

>Hi,
>
>I'm having an awful lot of trouble getting RHDB 2.1 to install on a
>clean RHL 8.0 install.  I really can't work out what's going wrong,
>because the error messages aren't exactly all the helpful.
>
>I get the same message I do in text mode, that I do in graphical, I just
>used the text mode installation method so I'm able to show exactly what
>it is I'm doing via e-mail.
>
>Here goes:
>
>[root@chopper cdrom]# ./Install -text
>Red Hat Linux 8.0 detected; running installer...
>Tclish-text Installer, (c) 2001, 2002 Red Hat Inc.
>Portions Copyright (c) 1998, 1999, 2000 by The Tcl/Tk Consortium
>
>This installer comes with ABSOLUTELY NO WARRANTY; for details
>see the file LICENSE.TXT. This is free software, and you are
>welcome to redistribute it under the terms of the included
>license.
>
>Loading installer: Red Hat Database
>Copyright (C) 2001, 2002 Red Hat Inc.
>
>Error in package 'rh-postgresql': This package includes the client
>programs
>that you will need to access a PostgreSQL server. These client programs
>can be
>located on the same machine as the PostgreSQL server or on a remote
>machine
>that accesses the PostgreSQL server over a network connection. This
>package
>also contains the PostgreSQL Global Development Group's complete
>documentation
>in HTML format as well as command-line utilities for managing databases
>on
>PostgreSQL servers. If you want to manipulate a PostgreSQL database on a
>remote PostgreSQL server, you need this package.warning:
>packages/rh-postgresql-7.2.3-1_rhl80.i386.rpm: V3 DSA signature: NOKEY,
>key ID
>db42a60e
>
>[ Press ENTER to continue ]
>
>[root@chopper cdrom]#
>
>It really does not mean a lot to mean, I'm hoping someone might be able
>to clue me up, maybe I'm just being stupid, I have however tried this on
>several machines, with exactly the same result every time.
>
>Any help is muchly appreciated.
>
>Thanks.
>
>Lachlan Evans
>
>  
>
Hi Lachlan,

I wasn't able to reproduce your problem, however, I suspect
you need to install the appropriate key to verify the signature,
please try to import the PGP key in the iso, and then install
again. Hopefully, that will solve  the problem.

Cheers,
Permaine


  parent reply	other threads:[~2002-12-30  1:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-26  0:25 Lachlan Evans
2002-12-27  4:54 ` Rommel the iCeMAn
2002-12-29 17:53   ` Permaine Cheung
2002-12-29 17:49 ` Permaine Cheung [this message]
2003-01-02 15:30   ` Permaine Cheung
2003-02-04 17:04     ` Fernando Nasser
2003-02-04 17:23       ` Rommel the iCeMAn
2003-02-05 19:38       ` VB & RHDB Rommel the iCeMAn
2003-02-05 19:53         ` Fernando Nasser
2003-02-05 20:08           ` Rommel the iCeMAn
2002-12-30  4:57 ` Archives Rommel the iCeMAn
2002-12-30 17:21   ` Archives Patrick Macdonald
2002-12-31  4:42     ` Archives Rommel the iCeMAn
2003-02-04 18:13 RHDB 2.1 and RHL 8.0 Rommel the iCeMAn
2003-02-25 11:42 avezzaro
2003-02-25 15:22 ` Permaine Cheung

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E0FA680.1000004@redhat.com \
    --to=pcheung@redhat.com \
    --cc=lachlane@iinet.net.au \
    --cc=rhdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).