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

• Type: Documentation
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.25.0
• Component/s: documentation, project website
• Labels: build documentation mesosphere

Environment

CentOS 7 AWS Linux image: AWS EC2 MarketPlace CentOS 7 (x86_64) with Updates HVM (a t2.medium instance)

• Target Version/s: 0.27.0
• Sprint: Mesosphere Sprint 24
• Assignee: Kevin Klues
• Reporter: Manne Laukkanen
• Shepherd: Till Toenshoff
• Created: 06/Nov/15 19:23
• Updated: 26/Nov/18 12:20
• Resolved: 26/Nov/18 12:20

Description

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/:

1. 'Mesos > 0.21.0' requires 'subversion > 1.8' devel package, which is
2. not available in the default repositories.
3. 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.