On Tue, 2005-03-15 at 13:48 -0600, Paul Almquist wrote: > On Tuesday 15 March 2005 13:22, Gustavo Seabra wrote: > > On Tue, 15 Mar 2005 12:58:15 -0600, Paul Almquist <paul@xxxxxxxxxxxxx> > wrote: > > > On Tuesday 15 March 2005 11:46, Gustavo Seabra wrote: > > > > I wonder... I have Adobe Acrobat Reader installed, although I don't > > > > remember from which repo I got it. Using the link cited, will it > > > > overwrite the current version here, or will I end up with two > > > > acroreads installed? > > > > > > > > >rpm -q acroread > > > > > > > > acroread-5.0.10-1.1.fc3.rf > > > > > > > > >where acroread > > > > > > > > /usr/bin/acroread > > > > > > I installed v7 last night. Here is what I got: > > > # ll /usr/bin/acroread > > > lrwxrwxrwx 1 root root 40 Mar 15 01:11 /usr/bin/acroread > > > -> /usr/local/Adobe/Acrobat7.0/bin/acroread > > > > > > If you want to keep the old version you could rename /usr/bin/acroread > > > before installing v7. > > > > > > -- > > > Paul Almquist > > > paul@xxxxxxxxxxxxx > > > Eau Claire, WI USA > > > > This is what happens whn I try to install it: > > # rpm -ivh AdobeReader_enu-7.0.0-1.i386.rpm > > Preparing... ########################################### > > [100%] file /usr/bin/acroread from install of AdobeReader_enu-7.0.0-1 > > conflicts with file from package acroread-5.0.10-1.1.fc3.rf > > > > and it stops there. Am I doing something wrong here? > > > Oops, I forgot. rpm checks the rpm database for conflicts, not the file > system. there is an option to override such checks, --force if I remember > correctly--I'll check the man page. --force should work or use > --replacefiles which is one of 3 things that --force includes. > > See the man page for all the gory details. Lots of options. > Try again using: > rpm -ivh --force AdobeReader_enu-7.0.0-1.i386.rpm > > or you could remove your old version first. This is the thing to do. You are replacing the package "acroread" with an entirely different package called "AdobeReader_enu". The latter does not have an "Obsoletes: acroread" tag in its spec file and therefore does not cause the original acroread package to be upgraded. So you need to get rid of acroread yourself first. Never, ever use --force unless you know *exactly* what you are doing. It would be the wrong thing to do in this case as it would leave a partially-overwritten package on your system. Paul. -- Paul Howarth <paul@xxxxxxxxxxxx>
