You have a conflicting package installed from repository @atrpms. You need to remove that package and/or disable that repository to get past the dependency issue. 'Skip broken' is not going to handle this situation nor will any other set of yum options.
On Tue, September 26, 2017 05:32, Gary Stainburn wrote:
--> Processing Dependency: /usr/sbin/ldconfig for package: libbluray1-0.4.0-6.el7.x86_64 --> Finished Dependency Resolution Error: Package: libbluray1-0.4.0-6.el7.x86_64 (@atrpms) Requires: /usr/sbin/ldconfig Removing: glibc-2.17-157.el7_3.1.i686 (@updates) Not found Updated By: glibc-2.17-196.el7.i686 (base) Not found You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@lcomp5 ~]#
On Tuesday 26 September 2017 14:23:46 James B. Byrne wrote:
You have a conflicting package installed from repository @atrpms. You need to remove that package and/or disable that repository to get past the dependency issue. 'Skip broken' is not going to handle this situation nor will any other set of yum options.
Hi James,
Thanks for this. The actual problem was that the repo had been disabled. I have made a note to not use atrpms in future.
Gary
On 09/26/2017 09:23 AM, James B. Byrne wrote:
You have a conflicting package installed from repository @atrpms. You need to remove that package and/or disable that repository to get past the dependency issue. 'Skip broken' is not going to handle this situation nor will any other set of yum options.
Christ, how long as ATRPMs been dead? I think I stopped using it in 2008/9.
On Tuesday 26 September 2017 14:27:43 Mark Haney wrote:
On 09/26/2017 09:23 AM, James B. Byrne wrote:
You have a conflicting package installed from repository @atrpms. You need to remove that package and/or disable that repository to get past the dependency issue. 'Skip broken' is not going to handle this situation nor will any other set of yum options.
Christ, how long as ATRPMs been dead? I think I stopped using it in 2008/9.
I don't know. I will have installed then when following instrunctions found online. I generally check the dates on any web page I use, maybe I missed one.
Anyway, enabling it again for this box fixed the problem.
Am 26.09.2017 um 15:38 schrieb Gary Stainburn gary@ringways.co.uk:
On Tuesday 26 September 2017 14:27:43 Mark Haney wrote:
On 09/26/2017 09:23 AM, James B. Byrne wrote:
You have a conflicting package installed from repository @atrpms. You need to remove that package and/or disable that repository to get past the dependency issue. 'Skip broken' is not going to handle this situation nor will any other set of yum options.
Christ, how long as ATRPMs been dead? I think I stopped using it in 2008/9.
I don't know. I will have installed then when following instrunctions found online. I generally check the dates on any web page I use, maybe I missed one.
Anyway, enabling it again for this box fixed the problem.
Sorry to be pedantic, the symptom is fixed not the problem.
To check which packages are from atrpms try this one:
# rpm -qa --qf '%{NAME}-%{VENDOR}\n' | grep -v CentOS
It will list package name along with the corresponding repo tag.
That list can then be used to plan a package migration.
-- LF
On Tuesday 26 September 2017 15:32:50 Leon Fauster wrote:
Sorry to be pedantic, the symptom is fixed not the problem.
To check which packages are from atrpms try this one:
# rpm -qa --qf '%{NAME}-%{VENDOR}\n' | grep -v CentOS
It will list package name along with the corresponding repo tag.
That list can then be used to plan a package migration.
Leon,
There's nothing wrong with being pedantic, and thanks for the command. It was very useful. However, for the box that has the problem, it's not worth the time and effort involved in doing the correct fix.
Gary
-
Gary Stainburn -
James B. Byrne -
Leon Fauster -
Mark Haney