-1, one blocker and a number of usability issues
I cannot build on Ubuntu Karmic (with all latest apt patches from
canonical applied), avro ruby requires echoe which requires a version of
gem (not echoe but gem, see below) not avail on Karmic. This seems like
it's going to cause problems for a large number of users?
ph...@valhalla:~/a/avro-src-1.3.0$ sudo gem install echoe
ERROR: Error installing echoe:
gemcutter requires RubyGems version >= 1.3.6
ph...@valhalla:~/a/avro-src-1.3.0$ sudo gem update --system
ERROR: While executing gem ... (RuntimeError)
gem update --system is disabled on Debian. RubyGems can be updated
using the official Debian repositories by aptitude or apt-get.
Also, the README states that the ruby build requires a gem that cannot
be found:
ph...@valhalla:~/a/avro-src-1.3.0$ sudo gem install jajl-ruby
ERROR: could not find gem jajl-ruby locally or in a repository
Additionally:
What are we voting on, the entire set of files or some subset of files
in this release candidate directory? I've always been told Apache
requires voting on a single archive containing all of the artifacts that
make up the "release". Is this no longer the case?
FYI test-tools in java fails if JAVA_HOME is not set (but fine for the
rest of the build up to that point? why's that? easy to fix?):
test-tools:
[exec] Error: JAVA_HOME is not set.
[exec] + set -o errexit
[exec] + '[' '' = '' ']'
[exec] + echo 'Error: JAVA_HOME is not set.'
[exec] + exit 1
When I access this release candidate link I see a list of archives,
jars, eggs, sha1, md5, pom, etc.... files. Consider adding a README that
gives me some insight into what I should download based on my intended
usage. I think that would help users significantly.
Patrick
Doug Cutting wrote:
I have created a second candidate build for Avro release 1.3.0.
Please download, test, and vote by 24 February.
http://people.apache.org/~cutting/avro-1.3.0-rc1/
Thanks,
Doug
