Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Paul Kasper <paul@patton.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: RedHat 7.1/mips update
Date: Wed, 31 Oct 2001 14:20:22 -0500	[thread overview]
Message-ID: <3BE04EF6.2B3766E4@patton.com> (raw)
In-Reply-To: 20011024121646.A6520@lucon.org

[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]

"H . J . Lu" wrote:
> 
> I updated my RedHat 7.1/mips port. There are quite a few changes. Check it
> out.
> 
> H.J.
> -----
> My mini-port of RedHat 7.1 is at
> 
> ftp://oss.sgi.com/pub/linux/mips/redhat/7.1/
> 
.....
>
> 
> H.J.

I am trying to install from a SuSE 7.2 workstation. In an effort to get
findrpm to work, I updated my RPMs with 2 of yours and 2 from RedHat:
------------------------------
scooby:/opt/rh71_oss/install # rpm -Uhv  
../RPMS/i386/rpm-python-4.0.2-8.6.i386.rpm
../RPMS/i386/rpm-4.0.2-8.6.i386.rpm
/opt/download/RPMS/db1-1.85-7.i386.rpm
/opt/download/RPMS/patch-2.5.4-9.i386.rpm 
Preparing...                ###########################################
[100%]
package rpm-python-4.0.2-8.6 is already installed
package rpm-4.0.2-8.6 is already installed
package db1-1.85-7 is already installed
package patch-2.5.4-9 is already installed
scooby:/opt/rh71_oss/install # rpm -qa |grep python
python-imaging-1.1-68
python-tk-2.0-90
python-2.0-90
python-doc-2.0-90
python-devel-2.0-90
python-nothreads-2.0-90
python-demo-2.0-90
rpm-python-4.0.2-8.6
scooby:/opt/rh71_oss/install # rpm -qa |grep rpm   
rpm2html-1.5-16
rpmfind-1.6-62
autorpm-1.9.9-14
xrpm-2.2-333
rpm-4.0.2-8.6
rpm-python-4.0.2-8.6
scooby:/opt/rh71_oss/install # ./findrpm gcc
Traceback (most recent call last):
  File "./findrpm", line 5, in ?
    import rpm
ImportError: No module named rpm        <----- ??? -----
scooby:/opt/rh71_oss/install # 

------------------------------

Not being much of a python person, does anybody have any suggestions? 
Should I upgrade more of the python packages even though there are no
complaints regarding depenencies?

Any suggestions welcomed.

--
Paul Kasper
-- 
 /"\ . . . . . . . . . . . . . . . /"\
 \ /   ASCII Ribbon Campaign       \ /     Paul R. Kasper
  X    - NO HTML/RTF in e-mail      X      Patton Electronics Co.
 / \   - NO MSWord docs in e-mail  / \     301-975-1000 x173

[-- Attachment #2: Card for Paul Kasper --]
[-- Type: text/x-vcard, Size: 311 bytes --]

begin:vcard 
n:Kasper;Paul
tel;fax:301-869-9293
tel;work:301-975-1000 x173
x-mozilla-html:FALSE
url:www.patton.com
org:Patton Electronics Co.;Central Office Products
adr:;;7622 Rickenbacker Drive;Gaithersburg;MD;20879;USA
version:2.1
email;internet:paul@patton.com
x-mozilla-cpt:;10912
fn:Paul Kasper
end:vcard

  parent reply	other threads:[~2001-10-31 19:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-24 19:16 RedHat 7.1/mips update H . J . Lu
2001-10-25  7:07 ` Gleb O. Raiko
2001-10-25  7:13   ` H . J . Lu
2001-10-25 22:15 ` Geoffrey Espin
2001-10-25 22:25   ` H . J . Lu
2001-10-31 19:20 ` Paul Kasper [this message]
2001-10-31 19:29   ` H . J . Lu

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=3BE04EF6.2B3766E4@patton.com \
    --to=paul@patton.com \
    --cc=hjl@lucon.org \
    --cc=linux-mips@oss.sgi.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