Clearer error message if pyelftools is not installed

Clearer error message if pyelftools is not installed

R=ppi@google.com

[ppi, 2015-07-22 18:06:42]

ppi@chromium.org changed reviewers:
+ ppi@chromium.org

[ppi, 2015-07-22 18:06:42]

lgtm

[kulakowski, 2015-07-22 19:52:06]

On 2015/07/22 18:06:42, ppi wrote:
> lgtm

I don't seem to have push access to the mojo repo.

[ppi, 2015-07-22 22:09:18]

ppi@chromium.org changed reviewers:
+ jamesr@chromium.org
- ppi@google.com

[ppi, 2015-07-22 22:09:18]

+jamesr should be able to help with that

[jamesr, 2015-07-22 22:23:51]

On 2015/07/22 at 19:52:06, kulakowski wrote:
> On 2015/07/22 18:06:42, ppi wrote:
> > lgtm
> 
> I don't seem to have push access to the mojo repo.

Hi George!   I can help you out with that - what's your GitHub user name?

[kulakowski, 2015-07-22 22:27:39]

On 2015/07/22 22:23:51, jamesr wrote:
> On 2015/07/22 at 19:52:06, kulakowski wrote:
> > On 2015/07/22 18:06:42, ppi wrote:
> > > lgtm
> > 
> > I don't seem to have push access to the mojo repo.
> 
> Hi George!   I can help you out with that - what's your GitHub user name?

kulakowski

[jamesr, 2015-07-23 00:25:14]

You should be able to push now.

[kulakowski, 2015-07-23 00:43:01]

On 2015/07/23 00:25:14, jamesr wrote:
> You should be able to push now.

This landed but didn't close this, doing so manually.

[jamesr, 2015-07-23 00:44:53]

On 2015/07/23 at 00:43:01, kulakowski wrote:
> On 2015/07/23 00:25:14, jamesr wrote:
> > You should be able to push now.
> 
> This landed but didn't close this, doing so manually.

That's interesting - how did you land the patch?  What was the output from that
command?

[kulakowski, 2015-07-23 00:47:13]

On 2015/07/23 00:44:53, jamesr wrote:
> On 2015/07/23 at 00:43:01, kulakowski wrote:
> > On 2015/07/23 00:25:14, jamesr wrote:
> > > You should be able to push now.
> > 
> > This landed but didn't close this, doing so manually.
> 
> That's interesting - how did you land the patch?  What was the output from
that
> command?

I've unfortunately already lost the state of the terminal. I'm fairly sure |git
cl land| exited with 0: I would have noticed a red number in my shell otherwise.
Something seemed a bit weird about the output, but by the time I did my normal
|git checkout master; git pull; git branch -D $branch| dance (which worked; the
commit is there) I lost the output.

[jamesr, 2015-07-23 00:48:24]

Hmm, OK.  I wonder if the rietveld issue # was lost (it's normally stored as a
git branch property).  If you see it failing to comment+close when landing in
the future try to hang on to the output and branch data so we can debug.

[kulakowski, 2015-07-23 00:52:13]

On 2015/07/23 00:48:24, jamesr wrote:
> Hmm, OK.  I wonder if the rietveld issue # was lost (it's normally stored as a
> git branch property).  If you see it failing to comment+close when landing in
> the future try to hang on to the output and branch data so we can debug.

That seems likely. I hit ^C at some point when checking out the patch on a
different computer, on a bad network connection. Thanks.