Skip to content
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

Pixi package manager is unable to install rio-cogeo #47

Open
1 task done
tylere opened this issue Mar 6, 2024 · 2 comments
Open
1 task done

Pixi package manager is unable to install rio-cogeo #47

tylere opened this issue Mar 6, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@tylere
Copy link

tylere commented Mar 6, 2024

Solution to issue cannot be found in the documentation.

  • I checked the documentation.

Issue

The Pixi package manager is unable to install rio-cogeo:

pixi global install rio-cogeo
  × could not find an executable entrypoint in package rio-cogeo 5.2.0 pyhd8ed1ab_0 from conda-forge, are you sure
  │ it exists?

I suspect this occurs because the rio-cogeo feedstock meta.yaml does not include a build:entry_points: section, as described in the Conda-build Defining metadata

Something like the following (untested!!!) addition may resolve this, but I am unsure of the syntax since cogeo is a plugin for rio:

build:
  entry_points:
    - create = rio_cogeo.scripts:create
    - validate = rio_cogeo.scripts:validate

Installed packages

n/a (not running conda)

Environment info

n/a (not running conda)
@tylere tylere added the bug Something isn't working label Mar 6, 2024
@ocefpaf
Copy link
Member

ocefpaf commented Mar 7, 2024

I'm not sure if that is a bug in pixi or if we should be doing something different in conda-forge recipes for this kind of entrypoint. rio-cogeo doesn't have one per se but adds to rasterio:

[project.entry-points."rasterio.rio_plugins"]
cogeo = "rio_cogeo.scripts.cli:cogeo"

and we do test if in the recipe. @wolfv, sorry for the ping here but you probably can guide us to the right person in pixi that could help us out here.

@tdejager
Copy link

Hi 👋 I'm from the pixi team, I think @wolfv is the best person to react to this, but I suspect we need something like: prefix-dev/pixi#342 to support this properly. But I'm unsure :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants