Skip to content

Install of git package fails on Raspberry Pi (succeeds elsewhere) with PackageInfoError #2898

@ChasNelson1990

Description

@ChasNelson1990

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 of inspection/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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugSomething isn't working as expectedstatus/triageThis issue needs to be triaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions