CentOS6 CR Repo – Depsolving Problem

Home » CentOS » CentOS6 CR Repo – Depsolving Problem
CentOS 2 Comments

All,

Has anyone else had a problem with the CR repo on a 6.4 or 6.5 system?

I have a test VM that has the CentOS6 CR repo enabled and it recently (well a week or so) started having dependency problems. It’s choking on dependencies for ca-cerfificates. Obviously there aren’t any CR packages yet for 6.5 so a zero package count and empty directory on the mirror [0]
are legitimate. But should the depsolving problems be the expected behavior?

[0] http://mirror.CentOS.org/CentOS/6.5/cr/x86_64/Packages/

Up until now, that machine has happily had the CR repo enabled. Thanks for any tips and assistance.

~]# yum deplist ca-certificates Loaded plugins: fastestmirror, security Loading mirror speeds from cached hostfile
<...snipped...>
Finding dependencies:
package: ca-certificates.noarch 2013.1.95-65.1.el6_5
dependency: /bin/bash
Unsatisfied dependency
dependency: p11-kit-trust >= 0.18.4-2
Unsatisfied dependency
dependency: /bin/sh
Unsatisfied dependency
dependency: p11-kit >= 0.18.4-2
Unsatisfied dependency

~]# yum repolist enabled Loaded plugins: fastestmirror, security Loading mirror speeds from cached hostfile
<...snipped...>
repo id repo name status base CentOS-6 – Base
0
cr CentOS-6 – CR
0
epel Extra Packages for Enterprise Linux 6 – x86_64
10,171
extras CentOS-6 – Extras
14
updates CentOS-6 – Updates
286
repolist: 10,472

~]# cat /etc/yum.repos.d/CentOS-CR.repo
# CentOS-CR.repo
#
# The continuous release ( CR ) repository contains rpms from the
# next point release of CentOS, which isnt itself released as yet.
#
# Look at http://wiki.CentOS.org/AdditionalResources/Repositories/CR
# for more details about how this repository works and what users
# should expect to see included / excluded

[cr]
name

2 thoughts on - CentOS6 CR Repo – Depsolving Problem

  • it’s your base repo that’s misconfigured. You have 0 packages whereas I
    have 6367 on a similar system. Perhaps hard-coded 6.4 in the base repo file?

    BTW you should seriously consider using yum priorities since you use third party repos (epel).

  • Holy smokes … I looked right by that.
    *facepalm*

    Not hardcoded to 6.4, but that doesn’t mean things elsewhere aren’t out of sync. I’ll have to double check my local mirror to see what is or if anything is up.

    My apologies to the list for the unnecessary noise. :-/

    That particular machine has only a few packages from EPEL (ex: mock) so I
    have the specific package names in an includepkgs= line in the epel repo file. I’ve used yum priorities elsewhere and should probably set this one up that way too.

    Thanks.

LEAVE A COMMENT