Rebuild for orc166 by regro-cf-autotick-bot · Pull Request #234 · conda-forge/arrow-cpp-feedstock

regro-cf-autotick-bot · 2020-12-21T21:50:26Z

This PR has been triggered in an effort to update orc166.

Notes and instructions for merging this PR:

Please merge the PR only after the tests have passed.
Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

This package has the following downstream children:

And potentially more.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot.

The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.

Finally, feel free to drop us a line if there are any issues!

This PR was generated by https://github.com/regro/autotick-bot/actions/runs/436652371, please use this URL for debugging}

…da-forge-pinning 2020.12.21.13.42.08

conda-forge-linter · 2020-12-21T21:50:33Z

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

xhochy · 2020-12-22T07:38:20Z

@conda-forge-admin please rerender

github-actions · 2020-12-22T07:40:28Z

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.

xhochy · 2020-12-22T07:42:53Z

@conda-forge-admin please rerender

…da-forge-pinning 2020.12.21.13.42.08

isuruf · 2020-12-22T07:53:13Z

recipe/meta.yaml

      ignore_run_exports:
        - cudatoolkit


Suggested change

ignore_run_exports:

- cudatoolkit

ignore_run_exports_from:

- {{ compiler('cuda') }}

- boost-cpp >=1.70

boost-cpp doesn't have a run_exports so this section should not be needed at all.

mbargull · 2020-12-22T07:56:57Z

I've removed automerge due to review.

mbargull · 2020-12-22T08:01:10Z

Question about arrow-cpp and its libarrow_python/libarrow_python_flight: What is their relationship to the actual python package? They don't appear to (dynamically) link to libpython and arrow-cpp itself does not include any Python package. Are they dependent on the Python version, i.e., do we need separate builds for each python?

xhochy · 2020-12-22T08:08:32Z

Question about arrow-cpp and its libarrow_python/libarrow_python_flight: What is their relationship to the actual python package? They don't appear to (dynamically) link to libpython and arrow-cpp itself does not include any Python package. Are they dependent on the Python version, i.e., do we need separate builds for each python?

Yes, they are dependent on the Python version and use symbols from Python. They don't link against libpython as they don't embed an interpreter and thus as-recommened should inherit the symbols from the Python executable that loads them.

xhochy · 2020-12-22T08:16:46Z

Question about arrow-cpp and its libarrow_python/libarrow_python_flight: What is their relationship to the actual python package? They don't appear to (dynamically) link to libpython and arrow-cpp itself does not include any Python package. Are they dependent on the Python version, i.e., do we need separate builds for each python?

Oh and the libarrow_python is the part that actually contains the complicated Python logic where the pyarrow package itself is mostly Cython-based glue code to it.

mbargull · 2020-12-22T08:18:19Z

Question about arrow-cpp and its libarrow_python/libarrow_python_flight: What is their relationship to the actual python package? They don't appear to (dynamically) link to libpython and arrow-cpp itself does not include any Python package. Are they dependent on the Python version, i.e., do we need separate builds for each python?

Yes, they are dependent on the Python version and use symbols from Python. They don't link against libpython as they don't embed an interpreter and thus as-recommened should inherit the symbols from the Python executable that loads them.

Thanks! Would it make sense to split them up into a subpackage to reduce redundancy (on CI and package repository) with the reset of the package?

mbargull · 2020-12-22T08:19:22Z

Oh and the libarrow_python is the part that actually contains the complicated Python logic where the pyarrow package itself is mostly Cython-based glue code to it.

Ah, makes sense. But they are expected to live in arrow-cpp or could(/should?) we move them to pyarrow?

xhochy · 2020-12-22T08:26:14Z

It's expected to be in arrow-cpp as it is currently, sadly that introduces a Python dependency on r-arrow.

I hope to have time somewhere in Spring 2020 to split this recipe into ~10 outputs (libarrow, libarrow_python, libarrow_flight, libgandiva, pyarrow, pyarrow.gandiva, ...) but that needs changes in upstream first. This will not reduce the build matrix though but at least keep it at the same size as currently.

xhochy · 2020-12-22T08:32:14Z

As arrow-cpp is the feedstock that is my main (initial) conda-forge motivation, I also blog about the progress since some weeks:

https://uwekorn.com/2020/09/08/trimming-down-pyarrow-conda-1-of-x.html (contains the unnecessary ignore_run_exports, I need to fix that)
https://uwekorn.com/2020/10/28/trimming-down-pyarrow-conda-2-of-x.html (scroll down to next steps for my todo list ;) )

mbargull · 2020-12-22T08:34:25Z

Perfect, thanks for all the explanations! :)

github-actions · 2020-12-22T08:45:23Z

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

linter: passed
drone: passed
azure: passed

Thus the PR was passing and merged! Have a great day!

regro-cf-autotick-bot added 2 commits December 21, 2020 21:47

Rebuild for orc166

9e3bc3f

MNT: Re-rendered with conda-build 3.20.5, conda-smithy 3.8.5, and con…

0a022cc

…da-forge-pinning 2020.12.21.13.42.08

regro-cf-autotick-bot requested review from cpcloud, jakirkham, jreback, kou, kszucs, leifwalsh, nealrichardson, pcmoritz, pearu, pitrou, robertnishihara, siddharthteotia, wesm and xhochy as code owners December 21, 2020 21:50

Update meta.yaml

893689f

Update meta.yaml

8664c5e

MNT: Re-rendered with conda-build 3.20.5, conda-smithy 3.8.5, and con…

a4a36ff

…da-forge-pinning 2020.12.21.13.42.08

xhochy added the automerge Merge the PR when CI passes label Dec 22, 2020

isuruf reviewed Dec 22, 2020

View reviewed changes

mbargull removed the automerge Merge the PR when CI passes label Dec 22, 2020

mbargull added the automerge Merge the PR when CI passes label Dec 22, 2020

github-actions bot merged commit 2011622 into conda-forge:master Dec 22, 2020

regro-cf-autotick-bot deleted the rebuild-orc166-0-1_h667a6b branch December 22, 2020 08:55

h-vetinari mentioned this pull request Sep 12, 2022

Unpin boost-cpp #850

Closed

-      ignore_run_exports:
-        - cudatoolkit
+      ignore_run_exports_from:
+        - {{ compiler('cuda') }}
+        - boost-cpp >=1.70

Uh oh!

Conversation

regro-cf-autotick-bot commented Dec 21, 2020

Uh oh!

conda-forge-linter commented Dec 21, 2020

Uh oh!

xhochy commented Dec 22, 2020

Uh oh!

github-actions bot commented Dec 22, 2020

Uh oh!

xhochy commented Dec 22, 2020

Uh oh!

isuruf Dec 22, 2020

Choose a reason for hiding this comment

Uh oh!

xhochy Dec 22, 2020

Choose a reason for hiding this comment

Uh oh!

mbargull commented Dec 22, 2020

Uh oh!

mbargull commented Dec 22, 2020

Uh oh!

xhochy commented Dec 22, 2020

Uh oh!

xhochy commented Dec 22, 2020

Uh oh!

mbargull commented Dec 22, 2020

Uh oh!

mbargull commented Dec 22, 2020

Uh oh!

xhochy commented Dec 22, 2020

Uh oh!

xhochy commented Dec 22, 2020

Uh oh!

mbargull commented Dec 22, 2020

Uh oh!

github-actions bot commented Dec 22, 2020

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants