Executable paths for shasum/openssl not protected against whitespace

in Makefile.am, we use @OPENSSL@ without properly quoting it. This is breaking the build on Windows for my build system

changed milestone to %Tor: 0.2.2.x-final

added component::core tor/tor milestone::Tor: 0.2.2.x-final priority::high resolution::fixed status::closed tor-client type::defect labels

branch bug5065 in my repository. Also contains a check-spaces cleanup patch.

Trac:
Status: new to needs_review

Looks good, but shouldn't this be on 0.2.2?

Trac:
Status: needs_review to needs_revision
Milestone: Tor: 0.2.3.x-final to Tor: 0.2.2.x-final

It is, afaict, not a problem when you build from a tarball; so I thought maybe we don't need it on 0.2.2. Also the forward merge does have conflicts. I prepared a branch bug5065_022, so you can decide which you'd rather use. If you go with bug5065_022, please cherry-pick the checkspaces thing from my bug5065 branch.

Looks good. I'll let Nick decide whether it should go into 0.2.2 or master. My tendency is to agree with him that it should go into 0.2.2 also.

Trac:
Status: needs_revision to needs_review

Merged into 0.2.2 and master. Cherry-picked the checkspaces thing. Thanks!

Trac:
Resolution: N/A to fixed
Status: needs_review to closed

Trac:
Keywords: N/A deleted, tor-client added

Trac:
Component: Tor Client to Tor

closed

moved to tpo/core/tor#5065 (closed)