[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: JBoss RPMs (was Re: Status update on v4 repo)



Thanks Harrison.  I searched in that repo before posting and did not see the java-devel dependency.


On Thu, Jul 31, 2014 at 1:56 PM, N. Harrison Ripps <hripps redhat com> wrote:

> On Jul 31, 2014, at 13:52, Kevin Conaway <kevin conaway gmail com> wrote:
>
> I see, thanks.  Trying to install that RPM complains about missing java-devel (java-devel is needed by maven3-3.0.3-4.noarch).

Anything that maven3 requires is probably also available in the v3 dependencies repo; you can search it by loading the base deps URL in your browser:

https://mirror.openshift.com/pub/origin-server/release/3/rhel-6/dependencies/x86_64

I would strongly recommend against just adding this as another repo; safer to "cherry-pick" the RPMs that you need.

>
> I have the following already installed:
>
> java-1.7.0-openjdk-1.7.0.65-2.5.1.2.el6_5.x86_64
> java-1.7.0-openjdk-devel-1.7.0.65-2.5.1.2.el6_5.x86_64
>
> Is there another repo I should be looking in?
>
>
>
>
> On Thu, Jul 31, 2014 at 1:38 PM, N. Harrison Ripps <hripps redhat com> wrote:
> Hey Kevin--
>
> > On Jul 31, 2014, at 13:32, Kevin Conaway <kevin conaway gmail com> wrote:
> >
> > Hi Philibert,
> >
> > What do you mean?
>
> The Origin 3 deps repo is still available, and contains that RPM:
>
> https://mirror.openshift.com/pub/origin-server/release/3/rhel-6/dependencies/x86_64/maven3-3.0.3-4.noarch.rpm
>
> --Harrison
>
> >
> >
> > On Thu, Jul 31, 2014 at 11:46 AM, Philibert Romain <romain philibert worldline com> wrote:
> > You could take it the the openshift r3 dependency repo.
> >
> >
> >
> > De : dev-bounces lists openshift redhat com [mailto:dev-bounces lists openshift redhat com] De la part de Kevin Conaway
> > Envoyé : jeudi 31 juillet 2014 17:21
> > À : Diego Spinola Castro
> > Cc : dev lists openshift redhat com
> > Objet : Re: JBoss RPMs (was Re: Status update on v4 repo)
> >
> >
> >
> > Thanks Diego.
> >
> >
> >
> > I installed the tomcat7 RPM without a problem.  When I try to install the jbossews cartridge, it complains that maven3 is needed.  I don't see that in the yum repo, is there an RPM for that somewhere that I should install?
> >
> >
> >
> > On Thu, Jul 31, 2014 at 9:15 AM, Diego Spinola Castro <spinolacastro gmail com> wrote:
> >
> > Yes, you can use for v4 install.
> >
> >
> >
> > 2014-07-31 10:03 GMT-03:00 Kevin Conaway <kevin conaway gmail com>:
> >
> >
> >
> > Thanks guys. Are those RPMS valid for v4 as well?
> >
> >
> >
> > On Mon, Jul 28, 2014 at 9:24 AM, N. Harrison Ripps <hripps redhat com> wrote:
> >
> > Hey all--
> > I just realized that Diego's response to the discussion about JBoss RPMs only went to me. Replying to include the list:
> >
> > > On Jul 25, 2014, at 10:37, Diego Spinola Castro <spinolacastro gmail com> wrote:
> > >
> > > Hi guys, i've done some jboss packages to meet jbossews and also jbossas cartridges.
> > > You can check this out:
> > >
> > > https://s3-us-west-2.amazonaws.com/getup-mirror/getup-openshift-origin-release-3/noarch/jboss-as7-7.1.1.Final-1.noarch.rpm
> > > https://s3-us-west-2.amazonaws.com/getup-mirror/getup-openshift-origin-release-3/noarch/tomcat6-6.0.39-1.noarch.rpm
> > > https://s3-us-west-2.amazonaws.com/getup-mirror/getup-openshift-origin-release-3/noarch/tomcat7-7.0.50-1.noarch.rpm
> > >
> > > On my RHEL deployment i just need those three extra packages , the rest is already provided by RHEL repos.
> > >
> > > Let me know if it solved your issue.
> > >
> > >
> > > 2014-07-25 10:39 GMT-03:00 N. Harrison Ripps <hripps redhat com>:
> > >
> > > > On Jul 24, 2014, at 17:46, Kevin Conaway <kevin conaway gmail com> wrote:
> > > >
> > > > Isn't the redhat or fedora repo public?  The jbossews cartridge gets dependency errors as well:http://pastebin.com/p3B7kH4z
> > >
> > > -To my knowledge- there are no public repos. But if somebody can find one, I will happily add it as a default for the java repo in oo-install / install.openshift.com
> > >
> > > >
> > > >
> > > > On Thu, Jul 24, 2014 at 5:34 PM, N. Harrison Ripps <hripps redhat com> wrote:
> > > >
> > > > On Jul 24, 2014, at 17:28, Kevin Conaway <kevin conaway gmail com> wrote:
> > > >
> > > > > I'm setting up my node host and am getting a dep error when installing the jboss cartridge:
> > > >
> > > > JBoss is actually a different story than the other cartridges. In order to have your JBoss cart work, you need to provide a repo URL to oo-install or the puppet module; this is not provided by default. If there is a public repo that we can use reliably, please let me know and I will make it a default under oo-install.
> > > >
> > > > >
> > > > > yum install -y openshift-origin-cartridge-jbossas
> > > > > Loaded plugins: fastestmirror
> > > > > Loading mirror speeds from cached hostfile
> > > > >  * base: mirror.hmc.edu
> > > > >  * epel: dl.fedoraproject.org
> > > > >  * extras: mirrors.sonic.net
> > > > >  * updates: centos.mirror.freedomvoice.com
> > > > > Setting up Install Process
> > > > > Resolving Dependencies
> > > > > --> Running transaction check
> > > > > ---> Package openshift-origin-cartridge-jbossas.noarch 0:1.26.1.1-1.el6 will be installed
> > > > > --> Processing Dependency: jboss-as7-modules >= 7.1.1.Final for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Processing Dependency: jboss-as7 >= 7.1.1.Final for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Processing Dependency: maven3 for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Processing Dependency: jboss-openshift-metrics-module for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Processing Dependency: java-1.7.0-openjdk-devel for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Processing Dependency: java-1.7.0-openjdk for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Running transaction check
> > > > > ---> Package java-1.7.0-openjdk.x86_64 1:1.7.0.65-2.5.1.2.el6_5 will be installed
> > > > > --> Processing Dependency: xorg-x11-fonts-Type1 for package: 1:java-1.7.0-openjdk-1.7.0.65-2.5.1.2.el6_5.x86_64
> > > > > ---> Package java-1.7.0-openjdk-devel.x86_64 1:1.7.0.65-2.5.1.2.el6_5 will be installed
> > > > > ---> Package jboss-openshift-metrics-module.noarch 0:1.0.2.redhat_1-1.2.el6oso will be installed
> > > > > --> Processing Dependency: quartz for package: jboss-openshift-metrics-module-1.0.2.redhat_1-1.2.el6oso.noarch
> > > > > ---> Package openshift-origin-cartridge-jbossas.noarch 0:1.26.1.1-1.el6 will be installed
> > > > > --> Processing Dependency: jboss-as7-modules >= 7.1.1.Final for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Processing Dependency: jboss-as7 >= 7.1.1.Final for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Processing Dependency: maven3 for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Running transaction check
> > > > > ---> Package openshift-origin-cartridge-jbossas.noarch 0:1.26.1.1-1.el6 will be installed
> > > > > --> Processing Dependency: jboss-as7-modules >= 7.1.1.Final for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Processing Dependency: jboss-as7 >= 7.1.1.Final for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Processing Dependency: maven3 for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > ---> Package quartz.noarch 0:2.2.1.redhat_1-1.el6oso will be installed
> > > > > ---> Package xorg-x11-fonts-Type1.noarch 0:7.2-9.1.el6 will be installed
> > > > > --> Processing Dependency: ttmkfdir for package: xorg-x11-fonts-Type1-7.2-9.1.el6.noarch
> > > > > --> Processing Dependency: ttmkfdir for package: xorg-x11-fonts-Type1-7.2-9.1.el6.noarch
> > > > > --> Running transaction check
> > > > > ---> Package openshift-origin-cartridge-jbossas.noarch 0:1.26.1.1-1.el6 will be installed
> > > > > --> Processing Dependency: jboss-as7-modules >= 7.1.1.Final for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Processing Dependency: jboss-as7 >= 7.1.1.Final for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > --> Processing Dependency: maven3 for package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch
> > > > > ---> Package ttmkfdir.x86_64 0:3.0.9-32.1.el6 will be installed
> > > > > --> Finished Dependency Resolution
> > > > > Error: Package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch (openshift-origin)
> > > > >            Requires: jboss-as7 >= 7.1.1.Final
> > > > > Error: Package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch (openshift-origin)
> > > > >            Requires: maven3
> > > > > Error: Package: openshift-origin-cartridge-jbossas-1.26.1.1-1.el6.noarch (openshift-origin)
> > > > >            Requires: jboss-as7-modules >= 7.1.1.Final
> > > > >  You could try using --skip-broken to work around the problem
> > > > >  You could try running: rpm -Va --nofiles --nodigest
> > > > >
> > > > >
> > > > > On Thu, Jul 24, 2014 at 5:25 PM, N. Harrison Ripps <hripps redhat com> wrote:
> > > > >
> > > > >
> > > > > On Jul 24, 2014, at 17:10, Kevin Conaway <kevin conaway gmail com> wrote:
> > > > >
> > > > >> This appears to be fixed now.
> > > > >
> > > > > I am running a full test with an updated puppet module; if the deployment is successful then I will update oo-install. I think we're good for the v4 release repos now but I want to be super extra sure.
> > > > >
> > > > > Cheers,
> > > > > Harrison
> > > > >
> > > > >>
> > > > >>
> > > > >> On Thu, Jul 24, 2014 at 8:56 AM, Kevin Conaway <kevin conaway gmail com> wrote:
> > > > >> I'm getting the same error as MrChoke: http://pastebin.com/u8Z3mfVb
> > > > >>
> > > > >> This is when I try to run yum install -y openshift-origin-broker openshift-origin-broker-util per http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html#install-necessary-packages
> > > > >>
> > > > >>
> > > > >> On Wed, Jul 23, 2014 at 9:54 PM, supphachoke suntiwichaya <mrchoke gmail com> wrote:
> > > > >> Hi, Team
> > > > >>
> > > > >> Broker yum update today feedback.
> > > > >>
> > > > >> http://pastebin.com/CfHDBG4F
> > > > >>
> > > > >> reps error.
> > > > >>
> > > > >> Regard ,
> > > > >>
> > > > >> MrChoke
> > > > >>
> > > > >>
> > > > >> 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.
> > > > >> >
> > > > >> > Cheers,
> > > > >> > Harrison
> > > > >> >
> > > > >> > _______________________________________________
> > > > >> > dev mailing list
> > > > >> > dev lists openshift redhat com
> > > > >> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> > > > >>
> > > > >>
> > > > >> _______________________________________________
> > > > >> dev mailing list
> > > > >> dev lists openshift redhat com
> > > > >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> > > > >>
> > > > >>
> > > > >> _______________________________________________
> > > > >> dev mailing list
> > > > >> dev lists openshift redhat com
> > > > >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> > > > >
> > > >
> > > >
> > >
> > >
> > > _______________________________________________
> > > dev mailing list
> > > dev lists openshift redhat com
> > > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> > >
> >
> >
> > _______________________________________________
> > dev mailing list
> > dev lists openshift redhat com
> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
> >
> > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
> >
> > _______________________________________________
> > dev mailing list
> > dev lists openshift redhat com
> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]