Hi there,
While running a yum update the hdd did get an error and the system was remounted in read only mode.
The error seems gone, but the rpmdb is not fine anymore, i did do rpm --rebuilddb But now i get weird errors with installing packages, like dupes or already installed (but it is not).
How do i create a new rpmdb with current installed packages?
Or am i doomed? :)
Danny
Danny Terweij - Net Tuning | Net writes:
Hi there,
While running a yum update the hdd did get an error and the system was remounted in read only mode.
The error seems gone, but the rpmdb is not fine anymore, i did do rpm --rebuilddb But now i get weird errors with installing packages, like dupes or already installed (but it is not).
How do i create a new rpmdb with current installed packages?
Or am i doomed? :)
An hdd error means - kiss your data good bye.
Salvage whatever data files you need, take the hard drive and throw it in the trash.
From: "Sam Varshavchik" mrsam@courier-mta.com
How do i create a new rpmdb with current installed packages? Or am i doomed? :)
An hdd error means - kiss your data good bye.
Salvage whatever data files you need, take the hard drive and throw it in the trash.
Thats not the answer on my question :) i have many boxes with....
The following warning/error was logged by the smartd daemon:
Device: /dev/hda, 3 Currently unreadable (pending) sectors
.....such messages and they still running fine after 2+ years (and have a lot data reads/writes)
So now the right answer please :)
Danny.
Danny Terweij - Net Tuning | Net writes:
From: "Sam Varshavchik" mrsam@courier-mta.com
How do i create a new rpmdb with current installed packages? Or am i doomed? :)
An hdd error means - kiss your data good bye.
Salvage whatever data files you need, take the hard drive and throw it in the trash.
Thats not the answer on my question :) i have many boxes with....
The following warning/error was logged by the smartd daemon:
Device: /dev/hda, 3 Currently unreadable (pending) sectors
.....such messages and they still running fine after 2+ years (and have a lot data reads/writes)
Just because you succesfully hoofed it across the six lanes of the interstate highway, a couple of times, doesn't mean you'll always succeed in dodging the 18-wheelers.
So now the right answer please :)
The right answer is that hard disks are cheap. It's just not worth it, waiting until the spindle finally grinds its way into the platter. You'll then have all your data gone, and be scrambling to get a new drive, swap in, and recover from backups.
Seems to me it's much easier to just go out and pick up a new drive, at your leisure, then schedule a weekend afternoon, in advance, to attach the new drive, and do an orderly migration.
On Saturday 04 February 2006 21:10, Sam Varshavchik wrote:
Danny Terweij - Net Tuning | Net writes:
From: "Sam Varshavchik" mrsam@courier-mta.com
new drive, and do an orderly migration.
It occurs that I have seen this before. Indeed many times before!
Many cdroms (especially older ones) can wreak havoc on IDE/ATA channels. They tend to be slower than hard drives and every so often can spit out spurious junk. I suspect that you have the cdrom on the same cable as the hard drive in question.
If this is so then you will have sporadic errors with a perfectly good hard drive.
If the hard drive is on the same cable/channel move it to the secondary IDE.
Danny Terweij - Net Tuning | Net wrote:
From: "Sam Varshavchik" mrsam@courier-mta.com
How do i create a new rpmdb with current installed packages? Or am i doomed? :)
An hdd error means - kiss your data good bye.
Salvage whatever data files you need, take the hard drive and throw it in the trash.
Thats not the answer on my question :) i have many boxes with....
The following warning/error was logged by the smartd daemon:
Device: /dev/hda, 3 Currently unreadable (pending) sectors
.....such messages and they still running fine after 2+ years (and have a lot data reads/writes)
So now the right answer please :)
Danny.
Even though the initial reply was a little harsh, a valid point is raised.
SMART was designed to help you BEFORE a crash. Well, as much as possible anyway.
This isn't just a warning "feature" - SMART was specifically designed to let you save data before impending doom.
Danny, if this box is not important to you, by all means, ignore the message.
If this box DOES mean something to you - then you really should heed the advice above. However, before you trash it, I would grab the manufacturer diagnostic utility (usually a boot floppy). Run the full barrage of tests.
If it fails in ANY way, then, I'm sorry to say - if the data is important, you're kidding yourself if you keep using the drive.
Regards, Ed.
On Saturday 04 February 2006 20:29, Sam Varshavchik wrote:
Danny Terweij - Net Tuning | Net writes:
Hi there,
While running a yum update the hdd did get an error and the system was remounted in read only mode.
The error seems gone, but the rpmdb is not fine anymore, i did do rpm --rebuilddb But now i get weird errors with installing packages, like dupes or already installed (but it is not).
How do i create a new rpmdb with current installed packages?
Or am i doomed? :)
An hdd error means - kiss your data good bye.
Salvage whatever data files you need, take the hard drive and throw it in the trash.
--->First read the man and info pages for these commands so you <--- --->understand what is being done (if you already don't ).<----
--> If the drive is failing Yes dump it <--
But if not--- You can force updates and installs
->rpm -Uvh --force --nodeps filename.rpm
If that doesn't work move each into a clean directory (I.E. mkdir 1 etc.), then;
->rpm2cpio libbeecrypt6-4.1.2-9.1_10.rhfc4.at.i386.rpm | cpio -iv --make-directories . #note '.' for current dir.
->mv -f file /to/the/proper/dir # the rpm2cpio will make subdirectories in the 'clean' directories you made.
After all this fun then you need to go back and;
->rpm -Uvh --force --nodeps filename.rpm # to cause rpm to recognize that the package is installed.
->rpm --rebuilddb ( There are possibly simpler ways but this does work-- I have done this myself to fix rpm -the package manager, yum and apt-get from a broken version upgrade)
Anyone have a better way I would like to hear it also.
Danny Terweij - Net Tuning | Net wrote:
Hi there,
While running a yum update the hdd did get an error and the system was remounted in read only mode.
The error seems gone, but the rpmdb is not fine anymore, i did do rpm --rebuilddb But now i get weird errors with installing packages, like dupes or already installed (but it is not).
How do i create a new rpmdb with current installed packages?
Or am i doomed? :)
Danny
Basically, you have to find the multiple version installed rpms and use a option to rpm called --justdb. this option will remove only the database entry for the old nonexistent package entry and then you could use the -V or --verify option to rpm to ensure the later installed version is intact. No output should show on the verify.
Someone on the test list posted this one-line command to allow an output to the terminal which will detect multiple entries of packages. The kernel and the gpg-pubkey and any other package that allows for multiple versions to coexist. If you are running a 64-bit system, the command will not work well.
rpm -aq --queryformat "%{NAME}\n" | sort | uniq -c | grep -v -E " *1 "
For packages that are not actually installed but are in the rpm database, it might be a tougher issue to deal with. You would need to run something like 'rpm -qa |grep missing' as root to detect packages which have missing files. Then you can either download the rpms and use rpm -Uvh --replacefiles --replacepkgs <package.rpm> or remove the database entry for the messed up package and do a 'yum install <package>' on the shortchanged package. Yum should not know it is installed and install over whatever remained of the package.
This other suggestions or you're doomed as you stated above. :-)
Jim
On Saturday 04 February 2006 20:50, Jim Cornette wrote:
Danny Terweij - Net Tuning | Net wrote:
Hi there,
While running a yum update the hdd did get an error and the system was remounted in read only mode.
The error seems gone, but the rpmdb is not fine anymore, i did do rpm --rebuilddb But now i get weird errors with installing packages, like dupes or already installed (but it is not).
How do i create a new rpmdb with current installed packages?
Or am i doomed? :)
Danny
Basically, you have to find the multiple version installed rpms and use a option to rpm called --justdb. this option will remove only the database entry for the old nonexistent package entry and then you could use the -V or --verify option to rpm to ensure the later installed version is intact. No output should show on the verify.
Someone on the test list posted this one-line command to allow an output to the terminal which will detect multiple entries of packages. The kernel and the gpg-pubkey and any other package that allows for multiple versions to coexist. If you are running a 64-bit system, the command will not work well.
rpm -aq --queryformat "%{NAME}\n" | sort | uniq -c | grep -v -E " *1 "
For packages that are not actually installed but are in the rpm database, it might be a tougher issue to deal with. You would need to run something like 'rpm -qa |grep missing' as root to detect packages which have missing files. Then you can either download the rpms and use rpm -Uvh --replacefiles --replacepkgs <package.rpm> or remove the database entry for the messed up package and do a 'yum install <package>' on the shortchanged package. Yum should not know it is installed and install over whatever remained of the package.
This other suggestions or you're doomed as you stated above. :-)
Jim
Hmm, jumping in here, that command above returns this: [root@coyote example]# rpm -aq --queryformat "%{NAME}\n" | sort | uniq -c | grep -v -E " *1 " 2 gnome-mag 2 gnome-speech 28 gpg-pubkey 2 kernel 2 perl-Digest-HMAC 2 perl-Digest-SHA1 2 perl-Time-HiRes
Frankly, with as much stuff as I've built and installed from tarballs, using either the make install or the checkinstall option, I would have thought the output would have been much more verbose. I use kde, self installed, so those gnome entries could probably be removed. Is there a way to get the versions back from that command automaticly?
-- The person who can smile when something goes wrong has thought of someone to blame it on.
Gene Heskett wrote:
On Saturday 04 February 2006 20:50, Jim Cornette wrote:
Danny Terweij - Net Tuning | Net wrote:
Hi there,
While running a yum update the hdd did get an error and the system was remounted in read only mode.
The error seems gone, but the rpmdb is not fine anymore, i did do rpm --rebuilddb But now i get weird errors with installing packages, like dupes or already installed (but it is not).
How do i create a new rpmdb with current installed packages?
Or am i doomed? :)
Danny
Basically, you have to find the multiple version installed rpms and use a option to rpm called --justdb. this option will remove only the database entry for the old nonexistent package entry and then you could use the -V or --verify option to rpm to ensure the later installed version is intact. No output should show on the verify.
Someone on the test list posted this one-line command to allow an output to the terminal which will detect multiple entries of packages. The kernel and the gpg-pubkey and any other package that allows for multiple versions to coexist. If you are running a 64-bit system, the command will not work well.
rpm -aq --queryformat "%{NAME}\n" | sort | uniq -c | grep -v -E " *1 "
For packages that are not actually installed but are in the rpm database, it might be a tougher issue to deal with. You would need to run something like 'rpm -qa |grep missing' as root to detect packages which have missing files. Then you can either download the rpms and use rpm -Uvh --replacefiles --replacepkgs <package.rpm> or remove the database entry for the messed up package and do a 'yum install <package>' on the shortchanged package. Yum should not know it is installed and install over whatever remained of the package.
This other suggestions or you're doomed as you stated above. :-)
Jim
Hmm, jumping in here, that command above returns this: [root@coyote example]# rpm -aq --queryformat "%{NAME}\n" | sort | uniq -c | grep -v -E " *1 " 2 gnome-mag 2 gnome-speech 28 gpg-pubkey 2 kernel 2 perl-Digest-HMAC 2 perl-Digest-SHA1 2 perl-Time-HiRes
Frankly, with as much stuff as I've built and installed from tarballs, using either the make install or the checkinstall option, I would have thought the output would have been much more verbose. I use kde, self installed, so those gnome entries could probably be removed. Is there a way to get the versions back from that command automaticly?
There was a script out there that someone made that made a file in the /tmp directory, then compared the uniq version and outputted the version information for the multiple versions. I long lost the script but it is in the archives on the fedora-test-list. I guess you could add rpm -q on the short list with the packagename files. The exact versions should show using the rpm -q function.
I should learn scripting instead of using ready-made scripts. Some day maybe.
Jim
On Saturday 04 February 2006 23:04, Jim Cornette wrote:
Gene Heskett wrote:
On Saturday 04 February 2006 20:50, Jim Cornette wrote:
Danny Terweij - Net Tuning | Net wrote:
Hi there,
While running a yum update the hdd did get an error and the system was remounted in read only mode.
The error seems gone, but the rpmdb is not fine anymore, i did do rpm --rebuilddb But now i get weird errors with installing packages, like dupes or already installed (but it is not).
How do i create a new rpmdb with current installed packages?
Or am i doomed? :)
Danny
Basically, you have to find the multiple version installed rpms and use a option to rpm called --justdb. this option will remove only the database entry for the old nonexistent package entry and then you could use the -V or --verify option to rpm to ensure the later installed version is intact. No output should show on the verify.
Someone on the test list posted this one-line command to allow an output to the terminal which will detect multiple entries of packages. The kernel and the gpg-pubkey and any other package that allows for multiple versions to coexist. If you are running a 64-bit system, the command will not work well.
rpm -aq --queryformat "%{NAME}\n" | sort | uniq -c | grep -v -E " *1 "
For packages that are not actually installed but are in the rpm database, it might be a tougher issue to deal with. You would need to run something like 'rpm -qa |grep missing' as root to detect packages which have missing files. Then you can either download the rpms and use rpm -Uvh --replacefiles --replacepkgs <package.rpm> or remove the database entry for the messed up package and do a 'yum install <package>' on the shortchanged package. Yum should not know it is installed and install over whatever remained of the package.
This other suggestions or you're doomed as you stated above. :-)
Jim
Hmm, jumping in here, that command above returns this: [root@coyote example]# rpm -aq --queryformat "%{NAME}\n" | sort | uniq -c | grep -v -E " *1 " 2 gnome-mag 2 gnome-speech 28 gpg-pubkey 2 kernel 2 perl-Digest-HMAC 2 perl-Digest-SHA1 2 perl-Time-HiRes
Frankly, with as much stuff as I've built and installed from tarballs, using either the make install or the checkinstall option, I would have thought the output would have been much more verbose. I use kde, self installed, so those gnome entries could probably be removed. Is there a way to get the versions back from that command automaticly?
There was a script out there that someone made that made a file in the /tmp directory, then compared the uniq version and outputted the version information for the multiple versions. I long lost the script but it is in the archives on the fedora-test-list. I guess you could add rpm -q on the short list with the packagename files. The exact versions should show using the rpm -q function.
I should learn scripting instead of using ready-made scripts. Some day maybe.
Jim
;-) I hear that, Jim. Me, at 71 I tend to furget, so I write scripts that don't forget. Yup, been there, done that. Several times... And a month later I may have forgotten the scripts name, and where I stashed it. I've heard that called CRS.
Gene Heskett wrote:
I should learn scripting instead of using ready-made scripts. Some day maybe.
Jim
;-) I hear that, Jim. Me, at 71 I tend to furget, so I write scripts that don't forget. Yup, been there, done that. Several times... And a month later I may have forgotten the scripts name, and where I stashed it. I've heard that called CRS.
Gene, I was able to get a script that will show you the version information and also it has the ability to not show rpms which it is normally allowed to show more than one instance. Steve Grub and Villa Herva had the most to do with this script. I did a bit of removal for the mismatched portion and added user feedback echoed test to terminal. I attached this as a text file, but it is actually a script.
A problem with the script that Ville described was the possibility that fookernel and kernelfoo packages would also be excluded as being alright. I checked and this is true. Ville suggested something like egrep "^ +[0123456789]+ +($dups)$" be added to the script to prevent the possibility from happening.
Jim
You subject does not seem to have any relationship to what you say in your posting. But incase you do what to repair the rpm database you do it by: rm /var/lib/rpm/__db* rpm --rebuilddb
On Sun, Feb 05, 2006 at 05:19:14PM -0500, Jim Cornette wrote:
Gene Heskett wrote:
I should learn scripting instead of using ready-made scripts. Some day maybe.
Jim
;-) I hear that, Jim. Me, at 71 I tend to furget, so I write scripts that don't forget. Yup, been there, done that. Several times... And a month later I may have forgotten the scripts name, and where I stashed it. I've heard that called CRS.
Gene, I was able to get a script that will show you the version information and also it has the ability to not show rpms which it is normally allowed to show more than one instance. Steve Grub and Villa Herva had the most to do with this script. I did a bit of removal for the mismatched portion and added user feedback echoed test to terminal. I attached this as a text file, but it is actually a script.
A problem with the script that Ville described was the possibility that fookernel and kernelfoo packages would also be excluded as being alright. I checked and this is true. Ville suggested something like egrep "^ +[0123456789]+ +($dups)$" be added to the script to prevent the possibility from happening.
Jim
-- The person who can smile when something goes wrong has thought of someone to blame it on.
#!/bin/sh
# Add any package here that is OK to have duplicates dups="gpg-pubkey|kernel" echo "Starting search for multiple rpms versions." echo
# Test 1. Look for multiple versions of the same package # We use # as a separator so that we can remove it later. # is not in any # package name that I know of and that's the basis of using it. list=`rpm -qa --queryformat "%{NAME}#%{ARCH}\n" | sort | uniq -c | tr '#' ' ' \ | egrep -vw "$dups" | awk '$1 > 1 { print $2 } '`
if [ x"$list" != "x" ] ; then echo "Duplicates were found:" echo $list | xargs rpm -q exit 1 else echo "No Duplicates found" fi
echo echo "Ending Search for Multiple RPMS." exit 0 fi
exit 0
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
akonstam@trinity.edu wrote:
You subject does not seem to have any relationship to what you say in your posting. But incase you do what to repair the rpm database you do it by: rm /var/lib/rpm/__db* rpm --rebuilddb
The original poster referred to trying the above steps. I don't see any references regarding the 'rm /var/lib/rpm/__db*' before running a rebuild on the database. I don't recall removing the entries helping out much before. The continuation was mainly referring to detecting which rpms were not cleaned up after install and left entries in the database. Out of curiosity myself, I'll see what happens when the /var/lib/rpm/__db* files are removed and the rpmdb is rebuilt with 'rpm --rebuilddb'
https://www.redhat.com/archives/fedora-list/2006-February/msg00602.html
Hi there,
While running a yum update the hdd did get an error and the system was remounted in read only mode.
The error seems gone, but the rpmdb is not fine anymore, i did do rpm --rebuilddb But now i get weird errors with installing packages, like dupes or already installed (but it is not).
How do i create a new rpmdb with current installed packages?
Or am i doomed? :)
Danny
On Sun, Feb 05, 2006 at 05:19:14PM -0500, Jim Cornette wrote:
Gene Heskett wrote:
I should learn scripting instead of using ready-made scripts. Some day maybe.
Jim
;-) I hear that, Jim. Me, at 71 I tend to furget, so I write scripts that don't forget. Yup, been there, done that. Several times... And a month later I may have forgotten the scripts name, and where I stashed it. I've heard that called CRS.
Gene, I was able to get a script that will show you the version information and also it has the ability to not show rpms which it is normally allowed to show more than one instance. Steve Grub and Villa Herva had the most to do with this script. I did a bit of removal for the mismatched portion and added user feedback echoed test to terminal. I attached this as a text file, but it is actually a script.
A problem with the script that Ville described was the possibility that fookernel and kernelfoo packages would also be excluded as being alright. I checked and this is true. Ville suggested something like egrep "^ +[0123456789]+ +($dups)$" be added to the script to prevent the possibility from happening.
Jim
-- The person who can smile when something goes wrong has thought of someone to blame it on.
#!/bin/sh
# Add any package here that is OK to have duplicates dups="gpg-pubkey|kernel" echo "Starting search for multiple rpms versions." echo
# Test 1. Look for multiple versions of the same package # We use # as a separator so that we can remove it later. # is not in any # package name that I know of and that's the basis of using it. list=`rpm -qa --queryformat "%{NAME}#%{ARCH}\n" | sort | uniq -c | tr '#' ' ' \ | egrep -vw "$dups" | awk '$1 > 1 { print $2 } '`
if [ x"$list" != "x" ] ; then echo "Duplicates were found:" echo $list | xargs rpm -q exit 1 else echo "No Duplicates found" fi
echo echo "Ending Search for Multiple RPMS." exit 0 fi
exit 0
On Sun, Feb 05, 2006 at 06:50:30PM -0500, Jim Cornette wrote:
akonstam@trinity.edu wrote:
You subject does not seem to have any relationship to what you say in your posting. But incase you do what to repair the rpm database you do it by: rm /var/lib/rpm/__db* rpm --rebuilddb
The original poster referred to trying the above steps. I don't see any references regarding the 'rm /var/lib/rpm/__db*' before running a rebuild on the database. I don't recall removing the entries helping out much before. The continuation was mainly referring to detecting which rpms were not cleaned up after install and left entries in the database. Out of curiosity myself, I'll see what happens when the /var/lib/rpm/__db* files are removed and the rpmdb is rebuilt with 'rpm --rebuilddb'
Well the /var/lib/rpm/__db* files are the database you are rebuilding which we are assuming are screwed up. So it makes some sensae to remove the old database before you rebuild it. This has always worked for me when rpm -qa says an rpm is installed which rpm -e says is not. ------------------------------------------- Aaron Konstam Computer Science Trinity University telephone: (210)-999-7484
akonstam@trinity.edu wrote:
On Sun, Feb 05, 2006 at 06:50:30PM -0500, Jim Cornette wrote:
akonstam@trinity.edu wrote:
You subject does not seem to have any relationship to what you say in your posting. But incase you do what to repair the rpm database you do it by: rm /var/lib/rpm/__db* rpm --rebuilddb
The original poster referred to trying the above steps. I don't see any references regarding the 'rm /var/lib/rpm/__db*' before running a rebuild on the database. I don't recall removing the entries helping out much before. The continuation was mainly referring to detecting which rpms were not cleaned up after install and left entries in the database. Out of curiosity myself, I'll see what happens when the /var/lib/rpm/__db* files are removed and the rpmdb is rebuilt with 'rpm --rebuilddb'
Well the /var/lib/rpm/__db* files are the database you are rebuilding which we are assuming are screwed up. So it makes some sensae to remove the old database before you rebuild it. This has always worked for me when rpm -qa says an rpm is installed which rpm -e says is not.
Aaron Konstam Computer Science Trinity University telephone: (210)-999-7484
I have removed the /var/lib/rpm/__db* a lot of times when the test release Phoebe before the split to FC happened without any known problems. I also ran rpm --rebuilddb during this period.
The only problems I see with performing these steps is that the rpm db is messed up because of some problem. The best way to deal with the messed up entries is to investigate why the entries are not correct. I usually assume that older versions of rpm entries for a package are lingering entries where the actual files were replaced by the newer rpm and can be safely removed. I have not tried the method described in present days but a recent poster reported losing a great many database entries for packages that are actually installed.
I currently have a clean database with fairly true package installed information. I did remove only the db entry for one particular rpm that is installed so I could update normally. It was a package that is removed on Future versions of Fedora. The program is hotplug. I am curious as to whether it will reappear once the /var/log/db* files are removed and rpm --rebuilddb is run on my system. I don't know what will happen, but I will be needing to do a clean install anyway on the test 3 release date. If the rpm db is damaged at ths point, a reinstall was intended anyway and nothing is lost, since the system is destined to vaporization at this point anyway,
I find all viewpoints and methods of trial interesting and hope to learn a bit from the different options to deal with a problem. Hopefully, I'll pick the right option from the many. I'll roll the wheel shortly.
Jim
Jim Cornette wrote:
There was a script out there that someone made that made a file in the /tmp directory, then compared the uniq version and outputted the version
I was the someone. The script is available at
http://warmcat.com/listrpmdupes
(Use Rightclick | Save As... )
but note it will not work right on x86_64, since duplicated packages differing only by arch are normal there.
What it does is not only list duped packages but specifically lists the ones it thinks can be deleted. So if you have blah-1.00 and blah-1.01 installed, the script will only output blah-1.00, which can be fed directly to rpm -e. If only one version of blah is installed it outputs nothing about blah. On a happy machine it won't output anything at all.
I used it several times with success, but it does no harm to review its output and convince yourself it makes sense considering rpm -qa before feeding it to rpm -e :-)
-Andy
yum died on me once and left a bunch of dup packages on my system since the cleanup part never ran on these packages. I wrote a script to fix these:
#!/bin/bash
for package in $(rpm -qa --qf '%{name}.%{arch}\n' | sort | uniq -d) ; do remove=`rpm -q $package | grep -v $(repoquery --quiet -C --queryformat '%{version}-%{release}' $package)` echo "Removing $remove.i386 ..."; rpm -e --nodeps "$remove.i386"; echo "Removing $remove.x86_64 ..."; rpm -e --nodeps "$remove.x86_64"; done
This script only gets i386 and x86_64 packages, the noarch and i686 packages will have to be done by hand
On 2/5/06, Andy Green andy@warmcat.com wrote:
Jim Cornette wrote:
There was a script out there that someone made that made a file in the /tmp directory, then compared the uniq version and outputted the version
I was the someone. The script is available at
http://warmcat.com/listrpmdupes
(Use Rightclick | Save As... )
but note it will not work right on x86_64, since duplicated packages differing only by arch are normal there.
What it does is not only list duped packages but specifically lists the ones it thinks can be deleted. So if you have blah-1.00 and blah-1.01 installed, the script will only output blah-1.00, which can be fed directly to rpm -e. If only one version of blah is installed it outputs nothing about blah. On a happy machine it won't output anything at all.
I used it several times with success, but it does no harm to review its output and convince yourself it makes sense considering rpm -qa before feeding it to rpm -e :-)
-Andy
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list