CentOS yum — pre-existing rpmdb issues
up vote
3
down vote
favorite
I'm trying to install git on a developer box and I get the following:
You could try using --skip-broken to work around the problem
** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows:
kernel-2.6.32-431.17.1.el6.x86_64 has installed conflicts bfa-firmware < ('0', '3.2.21.1', '2'): bfa-firmware-3.0.3.1-1.el6.noarch
kernel-firmware-2.6.32-431.17.1.el6.noarch is a duplicate with kernel-firmware-2.6.32-358.23.2.el6.noarch
kernel-headers-2.6.32-431.17.1.el6.x86_64 is a duplicate with kernel-headers-2.6.32-358.23.2.el6.x86_64
How can I resolve this? I'm not too familiar with CentOS/RHEL
Thanks
linux git kernel yum dependencies
add a comment |
up vote
3
down vote
favorite
I'm trying to install git on a developer box and I get the following:
You could try using --skip-broken to work around the problem
** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows:
kernel-2.6.32-431.17.1.el6.x86_64 has installed conflicts bfa-firmware < ('0', '3.2.21.1', '2'): bfa-firmware-3.0.3.1-1.el6.noarch
kernel-firmware-2.6.32-431.17.1.el6.noarch is a duplicate with kernel-firmware-2.6.32-358.23.2.el6.noarch
kernel-headers-2.6.32-431.17.1.el6.x86_64 is a duplicate with kernel-headers-2.6.32-358.23.2.el6.x86_64
How can I resolve this? I'm not too familiar with CentOS/RHEL
Thanks
linux git kernel yum dependencies
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I'm trying to install git on a developer box and I get the following:
You could try using --skip-broken to work around the problem
** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows:
kernel-2.6.32-431.17.1.el6.x86_64 has installed conflicts bfa-firmware < ('0', '3.2.21.1', '2'): bfa-firmware-3.0.3.1-1.el6.noarch
kernel-firmware-2.6.32-431.17.1.el6.noarch is a duplicate with kernel-firmware-2.6.32-358.23.2.el6.noarch
kernel-headers-2.6.32-431.17.1.el6.x86_64 is a duplicate with kernel-headers-2.6.32-358.23.2.el6.x86_64
How can I resolve this? I'm not too familiar with CentOS/RHEL
Thanks
linux git kernel yum dependencies
I'm trying to install git on a developer box and I get the following:
You could try using --skip-broken to work around the problem
** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows:
kernel-2.6.32-431.17.1.el6.x86_64 has installed conflicts bfa-firmware < ('0', '3.2.21.1', '2'): bfa-firmware-3.0.3.1-1.el6.noarch
kernel-firmware-2.6.32-431.17.1.el6.noarch is a duplicate with kernel-firmware-2.6.32-358.23.2.el6.noarch
kernel-headers-2.6.32-431.17.1.el6.x86_64 is a duplicate with kernel-headers-2.6.32-358.23.2.el6.x86_64
How can I resolve this? I'm not too familiar with CentOS/RHEL
Thanks
linux git kernel yum dependencies
linux git kernel yum dependencies
asked Oct 10 '14 at 9:27
Dave Melia
51126
51126
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
up vote
3
down vote
In my case I found that something had gone wrong and many packages had been updated without the older versions being removed. Attempts to rebuild the RPM DB did not solve the problem.
One solution that is working is simply to remove the older version and reinstall the newer version.
Looking at the error output each line basically says Update Package is a duplicate with Previous Package, ie:
kernel-headers-2.6.32-431.17.1.el6.x86_64 is a duplicate with kernel-headers-2.6.32-358.23.2.el6.x86_64
The following seems to work for me:
rpm --erase --nodeps --noscript kernel-headers-2.6.32-358.23.2.el6.x86_64
The command tells RPM to remove the specific Previous Package without removing any dependencies or running any scripts associated with the task.
Next the package needs to be reinstalled:
yum reinstall kernel-headers
This time there's no need to specify the exact package version as yum will look for the most recent version and reinstall it.
Yum will output the result of its Yum Check operation during each run. Keep doing this until there are no more duplicate packages listed.
Note that you can query the RPM database directly. If you see lots of messages that include the string glibc, for example, you can get a simple list of packages which have that string in their names like this:
rpm -qa | grep glibc | sort
Which might produce something like:
glibc-2.17-157.el7_3.5.x86_64
glibc-common-2.17-157.el7_3.4.x86_64
glibc-common-2.17-157.el7_3.5.x86_64
glibc-devel-2.17-157.el7_3.5.x86_64
glibc-headers-2.17-157.el7_3.5.x86_64
Now it's more obvious that the previous version of glibc-common must be removed:
rpm --erase --nodeps --noscript glibc-common-2.17-157.el7_3.4.x86_64
yum reinstall glibc-common
add a comment |
up vote
0
down vote
Try executing following command
yum clean all
rpm --rebuilddb
yum update
yum clean all
yum reinstall glibc glibc-common libgcc
yum upgrade
yum install yum-utils
package-cleanup --problems
package-cleanup --dupes
1
Didn't work for me as written, but some useful info there. The last 2 steps output the broken-list. What finally resolved some of the problems, was to keep downgrading, then upgrading, everything broken with all extra repos disabled, and then rebuilding the db (your step #2) between each downgrade/upgrade step. Lots of trial and error involved.
– JosephK
Mar 13 '16 at 12:26
add a comment |
up vote
0
down vote
Root Cause
Interruption in the up2date or yum update process caused the installation of multiple versions of the same package.
Resolution
- If the system is Red Hat Enterprise Linux 5 or later, the package-cleanup command can be used:
$ package-cleanup --dupes
$ package-cleanup --cleandupes
The --dupes command will list the duplicate packages installed on the machine, while the --cleandupes switch will remove the older versions. package-cleanup command is provided by the yum-utils package.
- If package-cleanup does not help or the system is Red Hat Enterprise Linux 4, remove packages manually using rpm:
$ rpm -e --justdb <package-name>-<old-version>
The '--justdb' switch is used to ensure that the package removal does not remove its files from the file system, removing it only from the rpm database.
Some duplicates may not removed because they are required by installed packages.
You can try --cleandupes with --removenewestdupes, or review them with --dupes and remove manually.
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
In my case I found that something had gone wrong and many packages had been updated without the older versions being removed. Attempts to rebuild the RPM DB did not solve the problem.
One solution that is working is simply to remove the older version and reinstall the newer version.
Looking at the error output each line basically says Update Package is a duplicate with Previous Package, ie:
kernel-headers-2.6.32-431.17.1.el6.x86_64 is a duplicate with kernel-headers-2.6.32-358.23.2.el6.x86_64
The following seems to work for me:
rpm --erase --nodeps --noscript kernel-headers-2.6.32-358.23.2.el6.x86_64
The command tells RPM to remove the specific Previous Package without removing any dependencies or running any scripts associated with the task.
Next the package needs to be reinstalled:
yum reinstall kernel-headers
This time there's no need to specify the exact package version as yum will look for the most recent version and reinstall it.
Yum will output the result of its Yum Check operation during each run. Keep doing this until there are no more duplicate packages listed.
Note that you can query the RPM database directly. If you see lots of messages that include the string glibc, for example, you can get a simple list of packages which have that string in their names like this:
rpm -qa | grep glibc | sort
Which might produce something like:
glibc-2.17-157.el7_3.5.x86_64
glibc-common-2.17-157.el7_3.4.x86_64
glibc-common-2.17-157.el7_3.5.x86_64
glibc-devel-2.17-157.el7_3.5.x86_64
glibc-headers-2.17-157.el7_3.5.x86_64
Now it's more obvious that the previous version of glibc-common must be removed:
rpm --erase --nodeps --noscript glibc-common-2.17-157.el7_3.4.x86_64
yum reinstall glibc-common
add a comment |
up vote
3
down vote
In my case I found that something had gone wrong and many packages had been updated without the older versions being removed. Attempts to rebuild the RPM DB did not solve the problem.
One solution that is working is simply to remove the older version and reinstall the newer version.
Looking at the error output each line basically says Update Package is a duplicate with Previous Package, ie:
kernel-headers-2.6.32-431.17.1.el6.x86_64 is a duplicate with kernel-headers-2.6.32-358.23.2.el6.x86_64
The following seems to work for me:
rpm --erase --nodeps --noscript kernel-headers-2.6.32-358.23.2.el6.x86_64
The command tells RPM to remove the specific Previous Package without removing any dependencies or running any scripts associated with the task.
Next the package needs to be reinstalled:
yum reinstall kernel-headers
This time there's no need to specify the exact package version as yum will look for the most recent version and reinstall it.
Yum will output the result of its Yum Check operation during each run. Keep doing this until there are no more duplicate packages listed.
Note that you can query the RPM database directly. If you see lots of messages that include the string glibc, for example, you can get a simple list of packages which have that string in their names like this:
rpm -qa | grep glibc | sort
Which might produce something like:
glibc-2.17-157.el7_3.5.x86_64
glibc-common-2.17-157.el7_3.4.x86_64
glibc-common-2.17-157.el7_3.5.x86_64
glibc-devel-2.17-157.el7_3.5.x86_64
glibc-headers-2.17-157.el7_3.5.x86_64
Now it's more obvious that the previous version of glibc-common must be removed:
rpm --erase --nodeps --noscript glibc-common-2.17-157.el7_3.4.x86_64
yum reinstall glibc-common
add a comment |
up vote
3
down vote
up vote
3
down vote
In my case I found that something had gone wrong and many packages had been updated without the older versions being removed. Attempts to rebuild the RPM DB did not solve the problem.
One solution that is working is simply to remove the older version and reinstall the newer version.
Looking at the error output each line basically says Update Package is a duplicate with Previous Package, ie:
kernel-headers-2.6.32-431.17.1.el6.x86_64 is a duplicate with kernel-headers-2.6.32-358.23.2.el6.x86_64
The following seems to work for me:
rpm --erase --nodeps --noscript kernel-headers-2.6.32-358.23.2.el6.x86_64
The command tells RPM to remove the specific Previous Package without removing any dependencies or running any scripts associated with the task.
Next the package needs to be reinstalled:
yum reinstall kernel-headers
This time there's no need to specify the exact package version as yum will look for the most recent version and reinstall it.
Yum will output the result of its Yum Check operation during each run. Keep doing this until there are no more duplicate packages listed.
Note that you can query the RPM database directly. If you see lots of messages that include the string glibc, for example, you can get a simple list of packages which have that string in their names like this:
rpm -qa | grep glibc | sort
Which might produce something like:
glibc-2.17-157.el7_3.5.x86_64
glibc-common-2.17-157.el7_3.4.x86_64
glibc-common-2.17-157.el7_3.5.x86_64
glibc-devel-2.17-157.el7_3.5.x86_64
glibc-headers-2.17-157.el7_3.5.x86_64
Now it's more obvious that the previous version of glibc-common must be removed:
rpm --erase --nodeps --noscript glibc-common-2.17-157.el7_3.4.x86_64
yum reinstall glibc-common
In my case I found that something had gone wrong and many packages had been updated without the older versions being removed. Attempts to rebuild the RPM DB did not solve the problem.
One solution that is working is simply to remove the older version and reinstall the newer version.
Looking at the error output each line basically says Update Package is a duplicate with Previous Package, ie:
kernel-headers-2.6.32-431.17.1.el6.x86_64 is a duplicate with kernel-headers-2.6.32-358.23.2.el6.x86_64
The following seems to work for me:
rpm --erase --nodeps --noscript kernel-headers-2.6.32-358.23.2.el6.x86_64
The command tells RPM to remove the specific Previous Package without removing any dependencies or running any scripts associated with the task.
Next the package needs to be reinstalled:
yum reinstall kernel-headers
This time there's no need to specify the exact package version as yum will look for the most recent version and reinstall it.
Yum will output the result of its Yum Check operation during each run. Keep doing this until there are no more duplicate packages listed.
Note that you can query the RPM database directly. If you see lots of messages that include the string glibc, for example, you can get a simple list of packages which have that string in their names like this:
rpm -qa | grep glibc | sort
Which might produce something like:
glibc-2.17-157.el7_3.5.x86_64
glibc-common-2.17-157.el7_3.4.x86_64
glibc-common-2.17-157.el7_3.5.x86_64
glibc-devel-2.17-157.el7_3.5.x86_64
glibc-headers-2.17-157.el7_3.5.x86_64
Now it's more obvious that the previous version of glibc-common must be removed:
rpm --erase --nodeps --noscript glibc-common-2.17-157.el7_3.4.x86_64
yum reinstall glibc-common
edited Jul 29 '17 at 18:59
answered Jul 29 '17 at 2:02
Sam Azer
9113
9113
add a comment |
add a comment |
up vote
0
down vote
Try executing following command
yum clean all
rpm --rebuilddb
yum update
yum clean all
yum reinstall glibc glibc-common libgcc
yum upgrade
yum install yum-utils
package-cleanup --problems
package-cleanup --dupes
1
Didn't work for me as written, but some useful info there. The last 2 steps output the broken-list. What finally resolved some of the problems, was to keep downgrading, then upgrading, everything broken with all extra repos disabled, and then rebuilding the db (your step #2) between each downgrade/upgrade step. Lots of trial and error involved.
– JosephK
Mar 13 '16 at 12:26
add a comment |
up vote
0
down vote
Try executing following command
yum clean all
rpm --rebuilddb
yum update
yum clean all
yum reinstall glibc glibc-common libgcc
yum upgrade
yum install yum-utils
package-cleanup --problems
package-cleanup --dupes
1
Didn't work for me as written, but some useful info there. The last 2 steps output the broken-list. What finally resolved some of the problems, was to keep downgrading, then upgrading, everything broken with all extra repos disabled, and then rebuilding the db (your step #2) between each downgrade/upgrade step. Lots of trial and error involved.
– JosephK
Mar 13 '16 at 12:26
add a comment |
up vote
0
down vote
up vote
0
down vote
Try executing following command
yum clean all
rpm --rebuilddb
yum update
yum clean all
yum reinstall glibc glibc-common libgcc
yum upgrade
yum install yum-utils
package-cleanup --problems
package-cleanup --dupes
Try executing following command
yum clean all
rpm --rebuilddb
yum update
yum clean all
yum reinstall glibc glibc-common libgcc
yum upgrade
yum install yum-utils
package-cleanup --problems
package-cleanup --dupes
edited Oct 23 '14 at 13:41
answered Oct 23 '14 at 13:25
jatin7
92
92
1
Didn't work for me as written, but some useful info there. The last 2 steps output the broken-list. What finally resolved some of the problems, was to keep downgrading, then upgrading, everything broken with all extra repos disabled, and then rebuilding the db (your step #2) between each downgrade/upgrade step. Lots of trial and error involved.
– JosephK
Mar 13 '16 at 12:26
add a comment |
1
Didn't work for me as written, but some useful info there. The last 2 steps output the broken-list. What finally resolved some of the problems, was to keep downgrading, then upgrading, everything broken with all extra repos disabled, and then rebuilding the db (your step #2) between each downgrade/upgrade step. Lots of trial and error involved.
– JosephK
Mar 13 '16 at 12:26
1
1
Didn't work for me as written, but some useful info there. The last 2 steps output the broken-list. What finally resolved some of the problems, was to keep downgrading, then upgrading, everything broken with all extra repos disabled, and then rebuilding the db (your step #2) between each downgrade/upgrade step. Lots of trial and error involved.
– JosephK
Mar 13 '16 at 12:26
Didn't work for me as written, but some useful info there. The last 2 steps output the broken-list. What finally resolved some of the problems, was to keep downgrading, then upgrading, everything broken with all extra repos disabled, and then rebuilding the db (your step #2) between each downgrade/upgrade step. Lots of trial and error involved.
– JosephK
Mar 13 '16 at 12:26
add a comment |
up vote
0
down vote
Root Cause
Interruption in the up2date or yum update process caused the installation of multiple versions of the same package.
Resolution
- If the system is Red Hat Enterprise Linux 5 or later, the package-cleanup command can be used:
$ package-cleanup --dupes
$ package-cleanup --cleandupes
The --dupes command will list the duplicate packages installed on the machine, while the --cleandupes switch will remove the older versions. package-cleanup command is provided by the yum-utils package.
- If package-cleanup does not help or the system is Red Hat Enterprise Linux 4, remove packages manually using rpm:
$ rpm -e --justdb <package-name>-<old-version>
The '--justdb' switch is used to ensure that the package removal does not remove its files from the file system, removing it only from the rpm database.
Some duplicates may not removed because they are required by installed packages.
You can try --cleandupes with --removenewestdupes, or review them with --dupes and remove manually.
add a comment |
up vote
0
down vote
Root Cause
Interruption in the up2date or yum update process caused the installation of multiple versions of the same package.
Resolution
- If the system is Red Hat Enterprise Linux 5 or later, the package-cleanup command can be used:
$ package-cleanup --dupes
$ package-cleanup --cleandupes
The --dupes command will list the duplicate packages installed on the machine, while the --cleandupes switch will remove the older versions. package-cleanup command is provided by the yum-utils package.
- If package-cleanup does not help or the system is Red Hat Enterprise Linux 4, remove packages manually using rpm:
$ rpm -e --justdb <package-name>-<old-version>
The '--justdb' switch is used to ensure that the package removal does not remove its files from the file system, removing it only from the rpm database.
Some duplicates may not removed because they are required by installed packages.
You can try --cleandupes with --removenewestdupes, or review them with --dupes and remove manually.
add a comment |
up vote
0
down vote
up vote
0
down vote
Root Cause
Interruption in the up2date or yum update process caused the installation of multiple versions of the same package.
Resolution
- If the system is Red Hat Enterprise Linux 5 or later, the package-cleanup command can be used:
$ package-cleanup --dupes
$ package-cleanup --cleandupes
The --dupes command will list the duplicate packages installed on the machine, while the --cleandupes switch will remove the older versions. package-cleanup command is provided by the yum-utils package.
- If package-cleanup does not help or the system is Red Hat Enterprise Linux 4, remove packages manually using rpm:
$ rpm -e --justdb <package-name>-<old-version>
The '--justdb' switch is used to ensure that the package removal does not remove its files from the file system, removing it only from the rpm database.
Some duplicates may not removed because they are required by installed packages.
You can try --cleandupes with --removenewestdupes, or review them with --dupes and remove manually.
Root Cause
Interruption in the up2date or yum update process caused the installation of multiple versions of the same package.
Resolution
- If the system is Red Hat Enterprise Linux 5 or later, the package-cleanup command can be used:
$ package-cleanup --dupes
$ package-cleanup --cleandupes
The --dupes command will list the duplicate packages installed on the machine, while the --cleandupes switch will remove the older versions. package-cleanup command is provided by the yum-utils package.
- If package-cleanup does not help or the system is Red Hat Enterprise Linux 4, remove packages manually using rpm:
$ rpm -e --justdb <package-name>-<old-version>
The '--justdb' switch is used to ensure that the package removal does not remove its files from the file system, removing it only from the rpm database.
Some duplicates may not removed because they are required by installed packages.
You can try --cleandupes with --removenewestdupes, or review them with --dupes and remove manually.
answered Nov 16 at 13:33
Ramazan Polat
532717
532717
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f823401%2fcentos-yum-pre-existing-rpmdb-issues%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown