Broker yum update today feedback.
On 24 ก.ค. 2557, at 06:09, N. Harrison Ripps <hripps redhat com> wrote:
> Hey all--
> Thanks for your patience. We are still making our way through the dependencies list, but hope to have things squared away by tomorrow.
> The issue is this: Origin v4 uses RPMs from six different software collections. Rather than adding each collection to the puppet module as a separate repo to set up, we thought it would be a better experience for folks if we mirrored the necessary RPMs into our own dependencies repo. There are some other nice benefits:
> 1. We don't have to update the Puppet module every time a new software collection needs to be included in the dependencies.
> 2. At yum update time, polling one big repo is a lot faster than polling six small ones.
> When we built the v4 RPMs, I expected that any unsatisfied RPM dependencies would fail and we could work through them before we announced v4's release. However, as some of you have found, some of these issues do not manifest until a user is trying to create an app of a given type, notably Node.JS. So while the RPMs are correctly built, the dependency chains are still a work in progress.
> To my knowledge, this only affects the Node.JS cart right now, but please let me know if you encounter issues with any other cartridges.
> Thanks again for your patience; I'm psyched that so many folks are trying out Origin v4 and I look forward to closing out this issue as quickly as possible.
> dev mailing list
> dev lists openshift redhat com
dev mailing list
dev lists openshift redhat com