Re: Build Failure

2018-03-19 Thread James Peach
> On Mar 19, 2018, at 4:38 PM, Shiv Deepak wrote: > > Thanks. I installed unzip. That worked. FWIW the test suite was fixed for 1.6 in 0da7b6cc37786df94465ae98948fd7be669a843e. > > On Mon, Mar 19, 2018 at 3:48 PM, Tomek Janiszewski wrote: > Do you

Re: Build Failure

2018-03-19 Thread Andrew Schwartzmeyer
It's sad that we fail at runtime like this when certain utilities aren't installed. We're currently working to replace the extraction logic with libarchive instead, so we'll no longer implicitly require unzip/gunzip/tar/7z etc. I think it will probably make it into 1.6.0. On 03/19/2018 4:38 pm,

Re: Build Failure

2018-03-19 Thread Shiv Deepak
Thanks. I installed unzip. That worked. On Mon, Mar 19, 2018 at 3:48 PM, Tomek Janiszewski wrote: > Do you have unzip installed? Can you try unzipping file like it's done in > the test? > > > pon., 19.03.2018, 22:53 użytkownik Shiv Deepak > napisał: > >>

Re: Welcome Chun-Hung Hsiao as Mesos Committer and PMC Member

2018-03-19 Thread Judith Malnick
Congrats Chun!  On Mon, Mar 12, 2018 at 2:50 PM, Benjamin Mahler wrote: > Welcome Chun! It's been great discussing things with you so far and thanks > for the all the hard work! > > On Sat, Mar 10, 2018 at 9:14 PM, Jie Yu wrote: > > > Hi, > > > > I am

Re: Build Failure

2018-03-19 Thread Tomek Janiszewski
Do you have unzip installed? Can you try unzipping file like it's done in the test? pon., 19.03.2018, 22:53 użytkownik Shiv Deepak napisał: > Hello, > > I am trying to build Mesos 1.5.0 from source on Ubuntu 16.04. > > I tried on Docker, VM, and EC2. Three test cases are

Fwd: Build Failure

2018-03-19 Thread Shiv Deepak
Hello, I am trying to build Mesos 1.5.0 from source on Ubuntu 16.04. I tried on Docker, VM, and EC2. Three test cases are failing no matter what. Here is the list. *[ PASSED ] 1904 tests.* *[ FAILED ] 3 tests, listed below:* *[ FAILED ] FetcherTest.Unzip_ExtractFile* *[ FAILED ]

Re: Release checksum file distribution change

2018-03-19 Thread Benjamin Bannier
Hi Harold, and thanks for chiming in. > Would it be prudent to provide both for a while before completely removing it? That would definitely be a possibility, but I am not aware of reasons it would be required, yet. Like I wrote, this only affects future releases and we will continue to serve