On Sun, May 27, 2018 at 5:02 PM, Alan Pevec <apevec at redhat.com> wrote: >>>> Error: Package: podman-0.5.3-7.gitc54b423.el7.x86_64 >>>> (virt7-container-common-candidate) >>>> Requires: conmon >= 2:1.10.0-3.gitb0f6d98 >>>> Installed: conmon-1.11.0-1.git55a3daa.el7.x86_64 >>>> (@virt7-container-common-candidate) >>>> conmon = 1.11.0-1.git55a3daa.el7 > >> Is it resolved now? I am trying to build minishift centos ISO and want >> to have podman but looks like due to this conflict I can't have it as >> of now. Finally, this is now resolved and now able to install podman without any conflict or error using 'virt7-container-common-candidate' repo. > > I was going to say that using builds from -candidate is not safe, but > in this case even builds in Virt SIG testing repo have the problem > with the Epoch. > AFAICT Virt SIG builds are rebuilt from Fedora spec where we have in cri-o.spec > %if 0%{?fedora} > Epoch: 2 > %endif > > but it's unconditional in Fedora podman.spec: > ... > Requires: conmon >= 2:1.10.0-3.gitb0f6d98 > > Cheers, > Alan > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > https://lists.centos.org/mailman/listinfo/centos-devel -- Praveen Kumar http://fedoraproject.org/wiki/User:Kumarpraveen http://fedoraproject.org/ http://kumar-pravin.blogspot.com