On Thu, 23 Jul 2015 16:12:59 -0700 Travis Rhoden <trhoden@xxxxxxxxxx> wrote: > I’m working on ways to improve Ceph installation with ceph-deploy, and > a common hurdle we have hit involves dependency issues between ceph.com > hosted RPM repos, and packages within EPEL. For a while we were able to > managed this with the priorities plugin, but then EPEL shipped packages > that included changes that weren’t available on the ceph.com packages, > and the EPEL packages “obsoleted” the ceph.com ones. [...] This happens every time repos want to conflict with packages provided by the base distro or EPEL. I think the only sensible way to manage it is not to conflict and rely on the base packages. That means getting the right versions in. In old EPEL/CentOS/RHEL this may mean versioned names or other tricks, but the point is to get them in. You have access to experienced packagers such as Haikel G., who can help you. So, I'm just curious, what are the specific pain points that we're hitting, which prevent using EPEL packages? What are you duplicating and why? -- Pete -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
