Thanks that fixed my error the -U and also thanks for clearing up the rpm 
removal query..

At 01:18 PM 9/22/2000 -0500, you wrote:
>On Fri, Sep 22, 2000 at 02:07:19PM -0400, Eileen Orbell wrote:
> > What is the best way to unistall a RPM.  I tried rpm -e filename
> > but get a error message "cannot remove filename directory not empty.
> > Should I delete the contents of the directory first?
>
>After you get those errors, try "rpm -q [package-name]", you'll usually find
>that rpm removed most of the package as well as its entry in the rpm database.
>The files it leaves behind are usually files which aren't part of the original
>package, such as user-added data or files automatically generated during the
>life of the software.  If you're sure you don't need the contents of the
>non-empty directory, yeah, you can usually delete it by hand.  I usually wait
>until after the rpm -e process completes successfully though.
>
> > Also I have noticed when I try to upgrade a RPM I get conflict error
> > messages.  Example is upgrading Perl from 5.00503-10 to 5.00503-12 I get
> > this error
> > file /usr/man/man1/pod2man.html.1.gz conflict with early install from
> > perl-5.00503
>
>Hm.  What options do you give rpm?  -U?  Or something else?  This is exactly
>the sort of thing that rpm is supposed to take care of for you...
>
>-m
>--
>Michael Jinks, IB
>Systems Administrator, CCCP
>finger [EMAIL PROTECTED] for public key
>Vote Duke! http://www.entertaindom.com/pages/duke2000/home.jsp
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list


Eileen Orbell
Software & Internet Applications
Capitol College
mailto:[EMAIL PROTECTED]
Don't Fear the Penguin.





_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to