While you may have them disabled _now_ at some point they were enabled and so a
conflicting package was installed and is now causing the issue.
- On 26 Sep, 2017, at 05:23, Gary Stainburn g...@ringways.co.uk wrote:
| On Tuesday 26 September 2017 11:56:06 Joseph L. Casale wrote:
|> The error
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 rep
> Am 26.09.2017 um 15:38 schrieb Gary Stainburn :
>
> 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
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 n
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 opti
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 o
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 St
On Tuesday 26 September 2017 11:56:06 Joseph L. Casale wrote:
> The error is actually pretty straight forward. You are using a repo
> (atrpms) that has not been updated in years, it's not surprise that it
> finally has lost compatibility with the platform.
>
> Find a modern and up to date replaceme
-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Gary Stainburn
Sent: Tuesday, September 26, 2017 3:32 AM
To: centos@centos.org
Subject: [CentOS] yum update problem - dependancy problem
> For a while I've been updating using the command
>
>
I'm sure this is a FAQ, and a simple answer is available, but I've not managed
it yet. I've tried all of the RPM database tidy routines. I've tried
uninstalling the libblueray1 library but the ever growning dependency tree
was too big.
For a while I've been updating using the command
yum -y
10 matches
Mail list logo