I'm using http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin310 and http://mirror.centos.org/centos/7/extras/x86_64/Packages/centos-release-ansi... for ansible 2.6
Installation fails early because ansible 2.6 has a dependency on python-keyczar which is not provided by either of the two above repos.
If I use https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin310/ which does provide python-keyczar then installation fails because this origin310 repo provides python2-docker which is incompatible with atomic-1.22
If I use http://cbs.centos.org/repos/paas7-openshift-origin310-candidate/x86_64/os/Pa... this also provides python2-docker
Rich,
back in 3.10 cycle we had few issues around python-docker-py & python-docker rpms which was causing incompatibility with atomic-1.22 which in turn caused big problems with CI Origin pipeline.
As such Brian was able to fix up the [2] dependency and so we sorted it out atomic-1.22 however we have not rollback on -testing or -candidate as it too much effort to fix it hence the differences you saw.
Now w.r.t centos-release-ansible26-1-3.el7.centos.noarch.rpm http://mirror.centos.org/centos/7/extras/x86_64/Packages/centos-release-ansible26-1-3.el7.centos.noarch.rpm we worked on the assumption that it will be used as a baseline on v3.11 as mentioned in the email i sent out [3] We didn't tackle the v3.10 release since it was already out there in the field.
Saying that i don't have an alternative for you right now, will need to think a bit about it. The risk is that we might break again the CI Origin dependency chain and i'd like to avoid that
will need to think about it.
[1] https://github.com/openshift/origin/issues/20653#issuecomment-413322137 [2] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin310 [3] http://lists.openshift.redhat.com/openshift-archives/users/2018-November/msg...
https://lists.centos.org/pipermail/centos-devel/2018-November/017050.html
On Wed, Nov 14, 2018 at 5:31 PM Rich Megginson rmeggins@redhat.com wrote:
I'm using http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin310 and http://mirror.centos.org/centos/7/extras/x86_64/Packages/centos-release-ansi... for ansible 2.6
Installation fails early because ansible 2.6 has a dependency on python-keyczar which is not provided by either of the two above repos.
If I use https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin310/ which does provide python-keyczar then installation fails because this origin310 repo provides python2-docker which is incompatible with atomic-1.22
If I use http://cbs.centos.org/repos/paas7-openshift-origin310-candidate/x86_64/os/Pa... this also provides python2-docker
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Nov 14, 2018 at 12:31 PM Rich Megginson rmeggins@redhat.com wrote:
I'm using http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin310 and http://mirror.centos.org/centos/7/extras/x86_64/Packages/centos-release-ansi... for ansible 2.6
Installation fails early because ansible 2.6 has a dependency on python-keyczar which is not provided by either of the two above repos.
If I use https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin310/ which does provide python-keyczar then installation fails because this origin310 repo provides python2-docker which is incompatible with atomic-1.22
If I use http://cbs.centos.org/repos/paas7-openshift-origin310-candidate/x86_64/os/Pa... this also provides python2-docker
Dependency resolution with python modules cah get.... fun.
If it helps you, I've been publishing srpm building tools for the "py2pack", and submitted pull requests to get the latest compatible RHEL and Fedora fplit python handling into the fedora.spec. Much like "cpan2rpm" used to bundle up CPAN modules as rpms, py2pack is useful for quickly fetching and RPM bundling python modules. My tweaked tools are at https://github.com/nkadel/py2packrepo .
-
Daniel Comnea -
Nico Kadel-Garcia -
Rich Megginson