You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Greg Mann (JIRA)" <ji...@apache.org> on 2015/10/16 20:55:05 UTC

[jira] [Commented] (MESOS-3752) CentOS 6 dependency install fails at Maven

    [ https://issues.apache.org/jira/browse/MESOS-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961201#comment-14961201 ] 

Greg Mann commented on MESOS-3752:
----------------------------------

I think this may be a bug in the current el6 Maven package. See this thread: https://bugzilla.redhat.com/show_bug.cgi?id=847837 . It seems that the {{java-devel}} capability is not being used for versions 1.7.0+, and indeed if I list the capabilities for the 1.7.0 jdk package I see:

{code}
[vagrant@centos66_vagrant ~]$ repoquery --provides java-1.7.0-openjdk-devel
java-1.7.0-openjdk-devel = 1:1.7.0.85-2.6.1.3.el6_7
java-1.7.0-openjdk-devel(x86-64) = 1:1.7.0.85-2.6.1.3.el6_7
java7-1.7.0-devel = 1:1.7.0.85
java7-devel = 1:1.7.0
java7-devel-openjdk = 1:1.7.0.85
java7-sdk = 1:1.7.0
java7-sdk-1.7.0 = 1:1.7.0.85
java7-sdk-1.7.0-openjdk = 1:1.7.0.85
java7-sdk-openjdk = 1:1.7.0.85
lib.so()(64bit)
lib.so(SUNWprivate_1.1)(64bit)
libjli.so()(64bit)
libjli.so(SUNWprivate_1.1)(64bit)
libunpack.so()(64bit)
{code}

So it looks like the {{java7-devel}} capability is being used instead. I don't think {{yum}} should be looking for {{java-devel >= 1:1.7.0}}.

> CentOS 6 dependency install fails at Maven
> ------------------------------------------
>
>                 Key: MESOS-3752
>                 URL: https://issues.apache.org/jira/browse/MESOS-3752
>             Project: Mesos
>          Issue Type: Documentation
>            Reporter: Greg Mann
>            Assignee: Greg Mann
>              Labels: documentation, installation, mesosphere
>
> It seems the Apache Maven dependencies have changed such that following the Getting Started docs for CentOS 6.6 will fail at Maven installation:
> {code}
> ---> Package apache-maven.noarch 0:3.3.3-2.el6 will be installed
> --> Processing Dependency: java-devel >= 1:1.7.0 for package: apache-maven-3.3.3-2.el6.noarch
> --> Finished Dependency Resolution
> Error: Package: apache-maven-3.3.3-2.el6.noarch (epel-apache-maven)
>            Requires: java-devel >= 1:1.7.0
>            Available: java-1.5.0-gcj-devel-1.5.0.0-29.1.el6.x86_64 (base)
>                java-devel = 1.5.0
>            Available: 1:java-1.6.0-openjdk-devel-1.6.0.35-1.13.7.1.el6_6.x86_64 (base)
>                java-devel = 1:1.6.0
>            Available: 1:java-1.6.0-openjdk-devel-1.6.0.36-1.13.8.1.el6_7.x86_64 (updates)
>                java-devel = 1:1.6.0
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)