+1 (binding)
- Verified the binaries (though I had to restart several times because
artifactory dropped me off)
- Verified the source tarball (required to define DYLD_LIBRARY_PATH
instead of LD_LIBRARY_PATH)
- Verified the wheels (without problems)
on Intel macOS 12.
On Mon, Jan 31, 2022 at 9:58 PM David Li <lidav...@apache.org> wrote:
>
> +1
>
> Tested source (C++/Java with integration), binaries, and wheels on Ubuntu
> 18.04.
>
> I ran into the same error as Antoine with the wheels; adding `conda activate
> base` also fixed it for me. I had to disable Gandiva for source verification
> due to a linking error with LLVM (though my system repositories don't have an
> appropriate version of LLVM in the first place).
>
> -David
>
> On Mon, Jan 31, 2022, at 05:59, Antoine Pitrou wrote:
> > Le 30/01/2022 à 11:15, Krisztián Szűcs a écrit :
> >>>
> >>> (*) Here is the end of the logs:
> >>>
> >>> + pushd binaries
> >>> /tmp/arrow-7.0.0.C5b7S/binaries /tmp/arrow-7.0.0.C5b7S
> >>> ++ uname
> >>> + '[' Linux == Darwin ']'
> >>> + test_linux_wheels
> >>> ++ uname -m
> >>> + '[' x86_64 = aarch64 ']'
> >>> + local arch=x86_64
> >>> + local 'py_arches=3.7m 3.8 3.9 3.10'
> >>> + local 'platform_tags=manylinux_2_12_x86_64.manylinux2010_x86_64
> >>> manylinux_2_17_x86_64.manylinux2014_x86_64'
> >>> + for py_arch in ${py_arches}
> >>> + local env=_verify_wheel-3.7m
> >>> + '[' 3.7m = 3.10 ']'
> >>> + local 'channels=-c conda-forge'
> >>> + mamba create -yq -n _verify_wheel-3.7m -c conda-forge python=3.7
> >>> ./dev/release/verify-release-candidate.sh: line 646: mamba: command not
> >> Could you please try to `conda activate base` before the mamba command
> >> and if that doesn't work simply replace `mamba` with `conda` and test
> >> the wheels again?
> >
> > Adding `conda activate base` solved the issue indeed.
> >
> > Regards
> >
> > Antoine.
