Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
MIME-Version: 1.0
In-Reply-To: <8a186f4a-545f-1517-bce7-f0a587d2d5f1@weimo.de>
References: <CA+4sW8h-5oXmG4JSmeegLStWC3sDNEmtaSZ--b9V8ASRbgP95g@mail.gmail.com>
	<CA+4sW8h8z-_QnFcioJjw1gBZ6nkNkGSBhoKXu=ZtMvhFMxHNFg@mail.gmail.com>
	<8a186f4a-545f-1517-bce7-f0a587d2d5f1@weimo.de>
Date: Fri, 20 May 2016 20:37:47 -0700
Message-ID: <CA+4sW8j=d_bdNqwNm2f2C6F5nvKxOwU-h8bQJnaJHm_gjvNePg@mail.gmail.com>
Subject: Re: Error checking in artifacts for release
From: Boris Shulman <shulmanb@gmail.com>
To: dev@reef.apache.org
Content-Type: multipart/alternative; boundary=001a114fad805b110c053351ee85
archived-at: Sat, 21 May 2016 03:37:53 -0000

--001a114fad805b110c053351ee85
Content-Type: text/plain; charset=UTF-8

The issue was that I didn't clean up, and ended having binaries in the
tar.gz, so it was too big. I cloned the repo again to make sure I have a
clean branch.

On Fri, May 20, 2016 at 8:35 PM, Markus Weimer <markus@weimo.de> wrote:

> On 2016-05-20 14:46, Boris Shulman wrote:
>
>> I managed checking in the smaller files, but not the actual gz, so
>> probably
>> some kind of proxy/firewall issues. Will try in the evening from home.
>>
>
> Since we are having a vote in another thread, it seems like you were able
> to upload the release artifact after all. What was the issue?
>
> Markus
>

--001a114fad805b110c053351ee85--