Ran dev/release/verify-release-candidate.sh source 0.14.0 0 on macOS Mojave.
I got the following error, but it may be specific to my environment.

"""
[ERROR] Failed to execute goal 
pl.project13.maven:git-commit-id-plugin:2.2.2:revision (for-jars) on project 
arrow-java-root: Could not complete Mojo execution...: Error: Could not get 
HEAD Ref, are you sure you have set the dotGitDirectory property of this plugin 
to a valid path? -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
+ cleanup
+ '[' no = yes ']'
+ echo 'Failed to verify release candidate. See 
/var/folders/8t/lw8gghw13hscdt7rr9j8kqnm0000gn/T/arrow-0.14.0.XXXXX.1bxYZ8hL 
for details.'
Failed to verify release candidate. See 
/var/folders/8t/lw8gghw13hscdt7rr9j8kqnm0000gn/T/arrow-0.14.0.XXXXX.1bxYZ8hL 
for details.
“""

"""
$ java --version                                                                
                                                                                
                                    
openjdk 11.0.2 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)
“""

"""
$ mvn --version                                                                 
                                                                                
                                     
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 
2018-10-25T03:41:47+09:00)
Maven home: /usr/local/Cellar/maven/3.6.0/libexec
Java version: 11.0.2, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-11.0.2.jdk/Contents/Home
Default locale: en_JP, platform encoding: UTF-8
OS name: "mac os x", version: "10.14.4", arch: "x86_64", family: "mac"
“""

 C# verification ran fine to me.


> On Jul 2, 2019, at 18:57, Antoine Pitrou <anto...@python.org> wrote:
> 
> 
> +1 for this RC0 anyway (binding).
> 
> 
> Le 02/07/2019 à 11:36, Antoine Pitrou a écrit :
>> 
>> I tried again (Ubuntu 18.04):
>> 
>> * binaries verification succeeded
>> 
>> * source verification failed in gRPC configure step:
>> 
>> CMake Error at cmake/cares.cmake:38 (find_package):
>>  Could not find a package configuration file provided by "c-ares" with any
>>  of the following names:
>> 
>>    c-aresConfig.cmake
>>    c-ares-config.cmake
>> 
>>  Add the installation prefix of "c-ares" to CMAKE_PREFIX_PATH or set
>>  "c-ares_DIR" to a directory containing one of the above files.  If "c-ares"
>>  provides a separate development package or SDK, be sure it has been
>>  installed.
>> Call Stack (most recent call first):
>>  CMakeLists.txt:139 (include)
>> 
>> 
>> Problem is, Ubuntu's c-ares does not provide any CMake files:
>> 
>> $ dpkg -L libc-ares-dev
>> /.
>> /usr
>> /usr/include
>> /usr/include/ares.h
>> /usr/include/ares_build.h
>> /usr/include/ares_dns.h
>> /usr/include/ares_rules.h
>> /usr/include/ares_version.h
>> /usr/lib
>> /usr/lib/x86_64-linux-gnu
>> /usr/lib/x86_64-linux-gnu/libcares.a
>> /usr/lib/x86_64-linux-gnu/pkgconfig
>> /usr/lib/x86_64-linux-gnu/pkgconfig/libcares.pc
>> /usr/share
>> /usr/share/doc
>> /usr/share/doc/libc-ares-dev
>> /usr/share/doc/libc-ares-dev/NEWS.gz
>> /usr/share/doc/libc-ares-dev/README.cares
>> /usr/share/doc/libc-ares-dev/README.md
>> /usr/share/doc/libc-ares-dev/copyright
>> /usr/share/man
>> /usr/share/man/man3
>> [ snip man pages ]
>> /usr/lib/x86_64-linux-gnu/libcares.so
>> 
>> 
>> Regards
>> 
>> Antoine.
>> 

Reply via email to