Thanks a lot, Krisztian.
The JS packages are still missing. I already have access to npm (thanks
Sutou). As part of the npm-release.sh in 4.0.1, we require all tests to
pass [1]. However, there are tests failing on my computer [2], which blocks
the release.
What is the procedure when this
FWIW, this CI C++ build script contains what I think is a comprehensive
list of cmake options supported in Arrow along with the common default
values:
https://github.com/apache/arrow/blob/master/ci/scripts/cpp_build.sh#L47-L132
Although I am not sure if this set of default values is used to build
Understood. Yes, if I compile it with devtoolset-3 it all works as
expected. We ran our testsuite on it (database + plugin + Arrow) and it
passed.
Which are the options set in cmake when the official package is built? We
built with all the options set as default and realized that Zlib
compression
Thank you -- I have created a PR to update the scripts [1] to include the
RC number in the subject line next time
[1] https://github.com/apache/arrow-rs/pull/450
Andrew
On Fri, Jun 11, 2021 at 12:27 PM Krisztián Szűcs
wrote:
> +1 (binding)
>
> Verified using the script on macOS Intel.
>
> I
+1
I ran the following command line on Debian GNU/Linux sid:
dev/release/verify-release-candidate.sh 4.3.0 1
Thanks,
--
kou
In
"[VOTE][RUST] Release Apache Arrow Rust 4.3.0" on Thu, 10 Jun 2021 18:04:56
-0400,
Andrew Lamb wrote:
> Hi,
>
> I would like to propose a release of
Hi,
I'm the original author of the Debian packages for Debian.
I'm positive that Apache Arrow package exists in the
official Debian repository.
> I do have a working package based on the JFrog packaging groundwork [0]
> but had to make various changes mostly to avoid downloading dependencies
>
Tying this together, it sounds like we have a few competing priorities
and it would be good to come up with more formal criteria about what
platforms + versions we support.
We have a list of operating systems (and versions) that we support
[1], and some of our client languages list versions that
Le 11/06/2021 à 20:10, Wes McKinney a écrit :
So this particular toolchain mix seems to be broken, does everything
work if you compile Arrow, the plugin, and the core database with
devtoolset-3? I think the weak link is Arrow C++ compiled with a
non-devtoolset compiler toolchain.
This
So this particular toolchain mix seems to be broken, does everything
work if you compile Arrow, the plugin, and the core database with
devtoolset-3? I think the weak link is Arrow C++ compiled with a
non-devtoolset compiler toolchain. If there were the package
maintainer bandwidth, having both
hi Andreas — do you want to go ahead and prepare PRs into the
maintenance branches? If the CI passes I don't see an issue with
merging them. I'm not sure we will make any more official patch
releases out of maint-4.0.x (and certainly not 3.0.x) but backporting
a patch like this sounds fine to me.
Hi Tahsin,
I've added you as a Contributor on JIRA and assigned you the ticket. From now
on you should be able to self-assign as well.
Best,
David
On 2021/06/11 16:18:45, Tahsin Hassan wrote:
> Hi all,
>
> I just submitted a Jira issue
> (https://issues.apache.org/jira/browse/ARROW-13056)
+1 (binding)
Verified using the script on macOS Intel.
I wasn't sure about the RC number, just inferred from the source tarball's link.
Could you please place the RC number in the subject line next time?
Thanks, Krisztian
On Fri, Jun 11, 2021 at 12:38 AM Wes McKinney wrote:
>
> +1 (binding)
>
Hi all,
I just submitted a Jira issue
(https://issues.apache.org/jira/browse/ARROW-13056) and I would like to request
a commiter to please assign the issue to me.
I am following the process described in
https://github.com/apache/arrow/blob/master/CONTRIBUTING.md for asking a
commuter to
Thanks Micah. Those criteria seem reasonable (and that discussion was
recent enough that my memory of it should have been sharper). I've created
https://issues.apache.org/jira/browse/ARROW-13055 so that we can document
this decision. IMO we don't need a vote on these criteria--seems like there
was
Dear arrow community,
Is there any chance for getting a (source-only) backport of
https://github.com/apache/arrow/pull/10429 to
https://github.com/apache/arrow/tree/maint-3.0.x and
https://github.com/apache/arrow/tree/maint-4.0.x ? If we could get that, we
could build pyarrow on our own, but
This is a great idea, thanks a lot!
Will you use PPA? Let me know to test these binaries
On Fri, Jun 11, 2021, 5:27 AM Sascha Steinbiss wrote:
> Hi Arrow community!
>
> I am a Debian Developer looking to package Arrow officially in Debian as
> a dependency for a specific tool I want to get into
Hi Arrow community!
I am a Debian Developer looking to package Arrow officially in Debian as
a dependency for a specific tool I want to get into Debian as well.
I do have a working package based on the JFrog packaging groundwork [0]
but had to make various changes mostly to avoid downloading
17 matches
Mail list logo
