Re: Updating the BDI2.04

[John Sheahan <jrsheahan-at-optushome.com.au>]

Jack
a linux rpm-based system maintain a database (in /var/lib/rpm)
of the files installed, the package they came from, and 
various dependencies.

If you  ONLY install files from rpm packages, 
and all the rpm packages are well built, and the distributon 
starts in a consistant and complete state, rpm files work well.


It seems the old bdi-204 missed this last step. 

Unfortunately there are so many different combinations of 
hardware and software versions out there its messy.

for a clean, minimal error message upgrade
rpm -Uvh <package>
  for the list of packages in the correct order

on a bdi install that had a clean rpm database should work 
with no errors.   Starting from a base with  a holey database will 
often look noisy and yucky.





On Thu, Jan 10, 2002 at 08:42:33PM -0500, Jack Ensor wrote:
> 
> I have run through various agonies in trying to get updated.  As
> usual if something is amiss when you are doing something new it leads
> to confusion.
> 
> I down loaded rcslib-rtl3_0-2_10_i586.rpm and
> emc-rtl3_0-2_10_i586.rpm.
> 
> To install these rpms I issued the command:
> 
> rpm -ivh rcslib-rtl3_0-2_10_i586.rpm
> 
> and get a message saying failed dependency rtlinux-3.0 is needed
> 
> I then do :
> 
> rpm -ivh --nodeps rcslib-rtl3_0-2_10_i586.rpm
> 
> and get message:
> 
> rcslib-rtl3.0-2.10 is already installed
> 

add --force to *really* install it

> Now is this a normal response?  The indications seem to imply there
> is a big problem here.  I ignore it and go on with:
> 

depends on whether the file was installed or not.


> rpm -ivh emc-rtl3_0-2_10_i586.rpm
> 
> and get message
> 
> failed dependencies
> 
> Then I do:
> 
> rpm -ivh --nodeps emc-rtl3_0-2_10_i586.rpm
> 
> and get about 45 messages typically reading:
> 
> emc/generic.ini from emc-rtl3.0-2.10 conflicts with file 
>        from package  emc-rtl3.0-2
> 
> and on and on files that are in /emc and emc/plat families.
> 
> Is this a normal response?  These error messages are very
> intimidating to a newbie.
> 
> Going on I look in the emc directory at some of the files there and
> apparently the old files are still there with a .bak appended to
> them.  And the new files are in there with today's date on them
> taking the place of the old files.  Now should I, in the interest of
> keeping a clean and uncluttered house remove the .bak files?
> 
> I tried running ./emc.run and it seems that it works okay although
> using home didn't seem to work as before - it seemed to drift around
> - I attribute this to  something not right in the ini file - I
> haven't studied that yet.
> 
> Now in the interest of keeping an accurate log for documentation
> purposes,  I would appreciate any comments on these problems.  Is
> this normal behavior for Linux?  Does one have to learn when and/or
> which error messages may be ignored?
> 
> Jack Ensor
> 
> Jack Ensor
>