-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install of git package fails on Raspberry Pi (succeeds elsewhere) with PackageInfoError #2898
Comments
I came across something like this yesterday using pip to install |
@ChasNelson1990 can you try with the latest pre-release please? Additionally, it will also be helpful if you can provide the stack trace by running the poetry command with
@BeebBenjamin I am unclear on what you mean by this. Do you want poetry to publish there? Or use this as a index when installing packages? If the latter, you can already do this. |
That's exactly what I mean. I probably won't be using |
Hi there, thanks for responding. Your response was nicely timed as I'm back on this project this week. I think, based on the above and my own issues I have two issues here (possibly both related to ARM but I think separate issues):
In response to my issue 1: @abn said:
Following the Poetry documentation and this idea I did: In response to my issue 2:
I did post the trace for the original call in the linked to Gist (https://gist.github.com/ChasNelson1990/6964153b4d5277518334716ac79f3a81) if that's what you were looking for? I have done |
P.S. I also note that if I install using |
The command you are using is for adding repositories for publishing. What you need is [[tool.poetry.source]]
name = "piwheels"
url = "https://www.piwheels.org/simple/" Adding this,
Apologies I missed this earlier. So the issue here is that we are unable to determine the package metadata for
A fix might be to add a [build-system]
requires = ["setuptools", "wheel", "numpy"]
build-backend = "setuptools.build_meta:__legacy__" |
poetry now insists on pep517 builds, which almost surely either fixes this or makes all of the particulars from the old failures irrelevant. suggest closing this, and invite a new issue for new problems |
I am on the latest Poetry version.
poetry self update --preview
I have searched the issues of this repo and believe that this is not a duplicate.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option).OS version and name: Linux raspberrypi 5.4.51-v7+ Running poetry install should not install the current project into site-packages #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux
Poetry version: Poetry version 1.1.0b2
Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/ChasNelson1990/6964153b4d5277518334716ac79f3a81
Issue
Hi there,
So I'm using a colleague's public bitbucket repository (
j_py_sad_correlation
) as a dependency for some of my own work. I'm able to use poetry to install this as a dependency on my Arch Linux laptop; and they're also able to use poetry to install this as a dependency on their OsX system. However, when I try to use poetry to install my dependencies on a Raspberry Pi v4 with the latest Raspberry Pi OS and preview Poetry I get a PackageInfoError and, to be honest, I'm just not expert enough on packages to understand what's going on here.I initially thought it might relate to an architecture problem in setup.py that we used to have (ARM processors required an additional flag at some point in the past) but I created a branch to test this (not shown) and got the same error. So it's not that.
Based on where in poetry this error is calling, it seems that poetry has recognised this is an old module and not pep517 compliant, has fallen back to using setup.py but, when calling setup.py to get egg_info, it fails. So that must work on both Arch Linux and OsX but not on Raspberry Pi OS? I have this vague recollection that pypi use to have some RPi issues due to eggs vs wheels but, again, not a package expert.
I'm expecting this is probably a problem in my colleague's setup.py, etc. that is not RPi compatible (although I can install this by cloning the repo and running
python setup.py build; python setup.py install
inside a clean poetry env). But the error isn't informative enough for me to understand whether this is true or not. One thing that could be useful is for the actual EnvCommandError to be passed back to the user on line 476 ofinspection/info.py
(although, tbh, I don't know what this error means either).Any suggestions? Happy to provide more info if needed.
Thanks!
Chas
P.S. If this is a RPi-specific issue with install, could that also explain why on my laptop Pillow seems to be installed from pip in a matter of seconds but on the RPi it seems to be building from source and takes so long I gave up?
The text was updated successfully, but these errors were encountered: