[
https://issues.apache.org/jira/browse/MESOS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206611#comment-13206611
]
[email protected] commented on MESOS-153:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3877/
-----------------------------------------------------------
(Updated 2012-02-13 01:25:12.166400)
Review request for mesos and Matei Zaharia.
Summary
-------
It turns out we had a rule in third_party/Makefile.am to extract the
boto-....tar.gz; we accidentally let this break (i.e. I was a bad code
reviewer) when we changed the .tar.gz to .zip. Since the EC2 scripts now use
boto directly from the .zip, we never need to extract boto.
This addresses bug MESOS-153.
https://issues.apache.org/jira/browse/MESOS-153
Diffs
-----
third_party/Makefile.am 344154b
Diff: https://reviews.apache.org/r/3877/diff
Testing
-------
Thanks,
Charles
> EC2 scripts no longer work because third_party/boto-2.02b was compressed
> ------------------------------------------------------------------------
>
> Key: MESOS-153
> URL: https://issues.apache.org/jira/browse/MESOS-153
> Project: Mesos
> Issue Type: Bug
> Components: build, ec2
> Reporter: Matei Zaharia
> Assignee: Matei Zaharia
> Priority: Blocker
> Attachments: MESOS-153.patch
>
>
> The EC2 scripts try to add Boto onto the Python path, but the recent change
> that compressed third_party prevents this. I can think of a few options to
> get around that:
> - Move Boto into a subdirectory of ec2 (maybe ec2/third_party)
> - Leave it uncompressed in the third_party directory
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
