You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "dmfay (via GitHub)" <gi...@apache.org> on 2023/06/14 14:34:38 UTC
[GitHub] [arrow] dmfay opened a new issue, #36065: 12.0.1 has 12.0.0 metadata
dmfay opened a new issue, #36065:
URL: https://github.com/apache/arrow/issues/36065
### Describe the bug, including details regarding any error messages, version, and platform.
I'm trying to install pyarrow==12.0.1 from a requirements file and receive this:
```
WARNING: Requested pyarrow==12.0.1 from https://files.pythonhosted.org/packages/c5/68/d3410e975bebbf5be00c1238d0418345d8ec5d88b7a6c102211a1c967edd/pyarrow-12.0.1.tar.gz (from -r /tmp/requirements.txt (line 4)), but installing version 12.0.0
Discarding https://files.pythonhosted.org/packages/c5/68/d3410e975bebbf5be00c1238d0418345d8ec5d88b7a6c102211a1c967edd/pyarrow-12.0.1.tar.gz (from https://pypi.org/simple/pyarrow/) (requires-python:>=3.7): Requested pyarrow==12.0.1 from https://files.pythonhosted.org/packages/c5/68/d3410e975bebbf5be00c1238d0418345d8ec5d88b7a6c102211a1c967edd/pyarrow-12.0.1.tar.gz (from -r /tmp/requirements.txt (line 4)) has inconsistent version: expected '12.0.1', but metadata has '12.0.0'
ERROR: Could not find a version that satisfies the requirement pyarrow==12.0.1 (from versions: 0.9.0, 0.10.0, 0.11.0, 0.11.1, 0.12.0, 0.12.1, 0.13.0, 0.14.0, 0.15.1, 0.16.0, 0.17.0, 0.17.1, 1.0.0, 1.0.1, 2.0.0, 3.0.0, 4.0.0, 4.0.1, 5.0.0, 6.0.0, 6.0.1, 7.0.0, 8.0.0, 9.0.0, 10.0.0, 10.0.1, 11.0.0, 12.0.0, 12.0.1)
ERROR: No matching distribution found for pyarrow==12.0.1
```
Downloading the 12.0.1 tarball I see the string "12.0.0" as `default_version` in setup.py and also set in CMakeLists.txt.
### Component(s)
Packaging, Release
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] jorisvandenbossche commented on issue #36065: [Python][Release] 12.0.1 has 12.0.0 metadata
Posted by "jorisvandenbossche (via GitHub)" <gi...@apache.org>.
jorisvandenbossche commented on issue #36065:
URL: https://github.com/apache/arrow/issues/36065#issuecomment-1593309269
@dmfay what version of pip are you using?
I also can't reproduce this when forcing to use source dists (`pip install pyarrow==12.0.1 --no-binary :all:`, using pip 23.1.2)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] raulcd commented on issue #36065: [Python][Release] 12.0.1 has 12.0.0 metadata
Posted by "raulcd (via GitHub)" <gi...@apache.org>.
raulcd commented on issue #36065:
URL: https://github.com/apache/arrow/issues/36065#issuecomment-1593210740
As a note with the wheels is successful:
```
$ python3 -m venv raul-test
$ source raul-test/bin/activate
$ pip install pyarrow==12.0.1
Collecting pyarrow==12.0.1
Using cached pyarrow-12.0.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (38.9 MB)
Collecting numpy>=1.16.6
Using cached numpy-1.24.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (17.3 MB)
Installing collected packages: numpy, pyarrow
Successfully installed numpy-1.24.3 pyarrow-12.0.1
[notice] A new release of pip is available: 23.0.1 -> 23.1.2
[notice] To update, run: pip install --upgrade pip
$ python
Python 3.11.4 (main, Jun 6 2023, 22:16:46) [GCC 11.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyarrow as pa
>>> pa.__version__
'12.0.1'
```
cc @jorisvandenbossche
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] jorisvandenbossche commented on issue #36065: [Python][Release] 12.0.1 has 12.0.0 metadata
Posted by "jorisvandenbossche (via GitHub)" <gi...@apache.org>.
jorisvandenbossche commented on issue #36065:
URL: https://github.com/apache/arrow/issues/36065#issuecomment-1593388997
Hmm, maybe the `--no-binary` on a platform that supports wheels still behaves a bit different compared to a platform for which there are no wheels at all ..
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] kou commented on issue #36065: [Python][Release] 12.0.1 has 12.0.0 metadata
Posted by "kou (via GitHub)" <gi...@apache.org>.
kou commented on issue #36065:
URL: https://github.com/apache/arrow/issues/36065#issuecomment-1592521825
You used `dev/release/03-binary-submit.sh`, right?
It passes a branch name (`apache-arrow-12.0.1` in this case) to `archery crossbow submit` but each job does not use the branch name to checkout apache/arrow. See `dev/tasks/macros.jinja`. It uses `arrow.head` instead of `arrow.branch` (`apache-arrow-12.0.1` in this case).
`arrow.head` is the revision of HEAD in the local repository. So I think that you run `dev/release/03-binary-submit.sh` on https://github.com/apache/arrow/commit/6af660f48472b8b45a5e01b7136b9b040b185eb1 .
What should we do to prevent this in the future?
1. Verify package version in `dev/release/verify-release-candidate.sh` too
2. Use tag name to build binary artifacts
```diff
diff --git a/dev/release/03-binary-submit.sh b/dev/release/03-binary-submit.sh
index d65b4e97c..ca9da2052 100755
--- a/dev/release/03-binary-submit.sh
+++ b/dev/release/03-binary-submit.sh
@@ -43,6 +43,7 @@ archery crossbow submit \
--arrow-version ${version_with_rc} \
--arrow-remote "https://github.com/${ARROW_REPOSITORY}" \
--arrow-branch ${ARROW_BRANCH} \
+ --arrow-sha ${ARROW_BRANCH} \
--group packaging
# archery will add a comment to the automatically generated PR to track
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] raulcd commented on issue #36065: 12.0.1 has 12.0.0 metadata
Posted by "raulcd (via GitHub)" <gi...@apache.org>.
raulcd commented on issue #36065:
URL: https://github.com/apache/arrow/issues/36065#issuecomment-1591450665
This is weird indeed.
The release branch contained the update to the `CMakeLists.txt` and the `setup.py` as seen here: https://github.com/apache/arrow/commit/6af660f48472b8b45a5e01b7136b9b040b185eb1#diff-005a07ca82fb46b215f58a3a8f4d6d6cc6ca088ade44e8f15cc2e6a51d1da6f4
That commit (6af660f48472b8b45a5e01b7136b9b040b185eb1) is also on the tag: https://github.com/apache/arrow/releases/tag/apache-arrow-12.0.1
It does seem that the binaries submitted used the following commit though: eb89c633abccd463f8472eaed37aa12c5f210a27
That commit was the last one on the maintenance branch before merging the version updates.
I extracted that commit from the wheels job here: https://github.com/ursacomputing/crossbow/actions/runs/5201602383/workflow#L52
Which are the jobs on the PR for the binary submission: https://github.com/apache/arrow/pull/35967
The arrow branch used based on the script should be the tag based on:
```
release_tag="apache-arrow-${version}"
: ${ARROW_BRANCH:=$release_tag}
```
but it does seem it did not use that one based on the hash on the comment:
https://github.com/apache/arrow/pull/35967#issuecomment-1581005613
@kou any idea what might have happened?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] dmfay commented on issue #36065: [Python][Release] 12.0.1 has 12.0.0 metadata
Posted by "dmfay (via GitHub)" <gi...@apache.org>.
dmfay commented on issue #36065:
URL: https://github.com/apache/arrow/issues/36065#issuecomment-1593375010
> @dmfay what version of pip are you using? I also can't reproduce this when forcing to use source dists (`pip install pyarrow==12.0.1 --no-binary :all:`, using pip 23.1.2)
```
pip 23.1.2 from /usr/lib/python3.11/site-packages/pip (python 3.11)
```
from `apk add py3-pip` on Alpine 3.18 in Docker.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] colin-rogers-dbt commented on issue #36065: [Python][Release] 12.0.1 has 12.0.0 metadata
Posted by "colin-rogers-dbt (via GitHub)" <gi...@apache.org>.
colin-rogers-dbt commented on issue #36065:
URL: https://github.com/apache/arrow/issues/36065#issuecomment-1599468785
We're also seeing this issue when we install from a downloaded tar file.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] colin-rogers-dbt commented on issue #36065: [Python][Release] 12.0.1 has 12.0.0 metadata
Posted by "colin-rogers-dbt (via GitHub)" <gi...@apache.org>.
colin-rogers-dbt commented on issue #36065:
URL: https://github.com/apache/arrow/issues/36065#issuecomment-1599614401
My understanding is that the practice encouraged by pip is for the package maintainer to yank the release and put out a new one: https://github.com/pypa/pip/issues/9203
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org