You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Kevin Klues (JIRA)" <ji...@apache.org> on 2015/12/14 23:42:46 UTC

[jira] [Issue Comment Deleted] (MESOS-3842) getting started documentation following Mesos 0.25 build fails for CentOS7 (http://mesos.apache.org/gettingstarted/)

     [ https://issues.apache.org/jira/browse/MESOS-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Klues updated MESOS-3842:
-------------------------------
    Comment: was deleted

(was: [vagrant@mesos-centos-7 ~]$ sudo yum install subversion
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: linux.mirrors.es.net
 * extras: mirror.san.fastserv.com
 * updates: mirror.lax.hugeserver.com
Resolving Dependencies
--> Running transaction check
---> Package subversion.x86_64 0:1.9.2-1 will be installed
--> Processing Dependency: apr-util >= 1.2.7 for package: subversion-1.9.2-1.x86_64
--> Processing Dependency: apr >= 1.2.7 for package: subversion-1.9.2-1.x86_64
--> Processing Dependency: libapr-1.so.0()(64bit) for package: subversion-1.9.2-1.x86_64
--> Processing Dependency: libaprutil-1.so.0()(64bit) for package: subversion-1.9.2-1.x86_64
--> Processing Dependency: libserf-1.so.0()(64bit) for package: subversion-1.9.2-1.x86_64
--> Running transaction check
---> Package apr.x86_64 0:1.4.8-3.el7 will be installed
---> Package apr-util.x86_64 0:1.5.2-6.el7 will be installed
---> Package subversion.x86_64 0:1.9.2-1 will be installed
--> Processing Dependency: libserf-1.so.0()(64bit) for package: subversion-1.9.2-1.x86_64
--> Finished Dependency Resolution
Error: Package: subversion-1.9.2-1.x86_64 (WANdiscoSVN)
           Requires: libserf-1.so.0()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest)

> getting started documentation following Mesos 0.25 build fails for CentOS7 (http://mesos.apache.org/gettingstarted/)
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-3842
>                 URL: https://issues.apache.org/jira/browse/MESOS-3842
>             Project: Mesos
>          Issue Type: Documentation
>          Components: documentation, project website
>    Affects Versions: 0.25.0
>         Environment: CentOS 7 AWS Linux image: AWS EC2 MarketPlace CentOS 7 (x86_64) with Updates HVM (a t2.medium instance)
>            Reporter: Manne Laukkanen
>            Assignee: Kevin Klues
>              Labels: build, documentation, mesosphere
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> WANdisco SVN repo file usage leads to failure of build process with error, so usage of it should be 1) discouraged 2) replaced with a working solution
> Proceeding according to documentation at http://mesos.apache.org/gettingstarted/:
> # 'Mesos > 0.21.0' requires 'subversion > 1.8' devel package, which is
> # not available in the default repositories.
> # Add the WANdisco SVN repo file: '/etc/yum.repos.d/wandisco-svn.repo' with content:
>   [WANdiscoSVN]
>   name=WANdisco SVN Repo 1.9
>   enabled=1
>   baseurl=http://opensource.wandisco.com/centos/7/svn-1.9/RPMS/$basearch/
>   gpgcheck=1
>   gpgkey=http://opensource.wandisco.com/RPM-GPG-KEY-WANdisco
> ...we do as is described, then proceed to next step, which is 
> "# Install essential development tools."
> sudo yum groupinstall -y "Development Tools"
> ...the added WANDISCO -repo causes failed building process with error:
> Error: Package: subversion-1.9.2-1.x86_64 (WANdiscoSVN)
>            Requires: libserf-1.so.0()(64bit)
>  - we end up with e.g. no build tools to proceed with, so process fails, Mesos can not be built according to instructions (e.g. no C-compiler in path...)
> Interestingly, building with aforementioned instructions (with some modifications mentioned in ticket MESOS-3844) was successful without errors justa a few days ago on 30 Oct 2015. WANDISCO repo breakage? 
> No changes to building machine image (the CentOS7 image) nor machine itself (t2.medium EC2 instance) were made in between attempts.



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