linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: root <hughc@babcockbrown.com>
To: Jeff Rugen <jrugen@primenet.com>
Cc: linuxppc-user@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: R5 Install (Mostly) Successful on PBG3
Date: Thu, 11 Feb 1999 15:07:54 -0800	[thread overview]
Message-ID: <36C362C9.6D64E0A6@babcockbrown.com> (raw)
In-Reply-To: Pine.BSI.3.96.990211154529.28495A-100000@usr09.primenet.com


This was a new install, no R4 stuff involved.

It turns out that running rpm --rebuilddb fixed it.  I haven't had any problems
installing the stuff I missed after that.

Do the LinuxPPC guys want to hear about problems with the install and
operation?

Hugh

Jeff Rugen wrote:

> On Thu, 11 Feb 1999, root wrote:
>
> > There were a few failures during intstall.  The main problem I have is
> > that RPM doesn't work; any attempt to use it returns an error
> > "//var/lib/rpm/nameindex.rpm: Invalid argument"
>
> The problem seems to be the R4 RPM database and the pre-R5 RPM database are
> incompatible with each other.  I manually removed all the /var/lib/rmp/*
> files (well, i copied them off) and reinstalled -- it created a new RPM
> database that works.  However, I was left with a ton of files from R4 rpms,
> that were no longer needed and I had to remove manually.
>
> I did write a script that would return 0 if the file passed in as a name was
> listed in the RPM database, and -1 otherwise, then used the script in a find
> command to list all the non-RPM files.  I ran it overnight -- ended up with
> thousands of files, and manually deleted large chunks of them.
>
> Be _very_ careful doing this.  Sometimes you'll get RPMs that don't indicate
> that a directory is part of the distribution, so you'll see directory names
> you think you can delete.  You don't want to do that. :-)
>
> ----------------------------------------------------------------------------
> Jeff Rugen                      jrugen@primenet.com
>
> ...Had this been an actual emergency, we would have fled in terror, and you
> would not have been informed.

--
Hugh Caley, System Administrator
Babcock & Brown, Inc., San Francisco
1+512+1515x694 | hughc@babcockbrown.com




[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

      reply	other threads:[~1999-02-11 23:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-11 20:39 R5 Install (Mostly) Successful on PBG3 root
1999-02-11 22:51 ` Jeff Rugen
1999-02-11 23:07   ` root [this message]

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=36C362C9.6D64E0A6@babcockbrown.com \
    --to=hughc@babcockbrown.com \
    --cc=jrugen@primenet.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-user@lists.linuxppc.org \
    /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 NNTP newsgroup(s).