Results 1 to 10 of 10
I've tried everything I can think of or find but I have 3 firefox entries in Yast Software Management database although I only have 1 I'm using (the others don't ...
- 03-02-2008 #1
Remove Software Entry from Yast
I've tried everything I can think of or find but I have 3 firefox entries in Yast Software Management database although I only have 1 I'm using (the others don't exist except in Yast).
Does anyone know how to remove these entries. Every time I try to uninstal and reinstal, I get an error message and an extra package entry. If i try again I'll just keep building up versions in Yast.
Firefox works fine and it's the right package version.Pete
- 03-02-2008 #2
Did you try
sudo rpm --rebuilddb
??
- 03-03-2008 #3
- 03-03-2008 #4
What happens when you run
One option would be to download the Firefox rpm from here, uninstall the old version and then use RPM to install the version you downloaded. Does that still create multiple entries in your menu?Code:#rpm -qa | grep -i firefox
- 03-03-2008 #5
Running your code gives me:
root pete > rpm -qa |grep -i firefox
firefox-2.9.93-11.1
MozillaFirefox-2.0.0.12-5.1
firefox-translations-2.9.93-11.1
MozillaFirefox-2.9.93-9.3
You can see the order but 2.0.0.12 only stuck when I downgraded to it. Now I can't remove 2.0.0.12 or 2.9.93-9.3. 2.9.93-11.1 works fine and shows as the version with firefox running. The other 2 I can't get rid of.Pete
- 03-03-2008 #6
Try doing
After that install the latest version using YAST or manually using rpm.Code:#rpm -e firefox-2.9.93-11.1 MozillaFirefox-2.0.0.12-5.1 firefox-translations-2.9.93-11.1 MozillaFirefox-2.9.93-9.3
- 03-03-2008 #7
I've tried that - it doesn't work either. It removes 2.9.93.11.1 but leaves the other 2 entries (no actual firefox). I get this error for each of the 2 remaining entries:
Code:Usage: usr/bin/update-mime-database [-hvV] MIME-DIR No directories in update-desktop-database search path could be processed and updated. error: %postun(MozillaFirefox-2.9.93-9.3.i586) scriptlet failed, exit status 1
Pete
- 03-03-2008 #8
Use the --noscripts option e.g.
Code:#rpm -e --noscripts somepackage
- 03-04-2008 #9
- 03-04-2008 #10
Glad you got things sorted. The RPM Guide is a very good resource for learning about RPM, so whenever you have time, its worth taking a look at it.


Reply With Quote
