Skip to content

Conversation

@p-vdp
Copy link
Contributor

@p-vdp p-vdp commented Nov 4, 2025

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@conda-forge/core Unfortunately I'd like to request removal of the ouroboros (not ouroboros-gis) packages from conda-forge. I was in the process of acquiring ouroboros on PyPI but I was preempted by another project (pypi/support#7781). In the interest of keeping parity between conda-forge and PyPI, what is the best course of action here?

@conda-forge-admin
Copy link
Contributor

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/meta.yaml) and found it was in an excellent condition.

@p-vdp
Copy link
Contributor Author

p-vdp commented Nov 4, 2025

@conda-forge-admin, please rerender

@h-vetinari
Copy link
Member

Removing an output is not a problem per se. Given the complicated history of the ouroboros name, I think it would be good though if you'd be willing to relinquish the name more generally, i.e. we mark the sole release of ouroboros as broken, and your users move to ouroboros-gis.

Your timing is good, because we're just discussing how to formalise policies around package renames (and similar situations) in conda-forge/cfep#64

@p-vdp
Copy link
Contributor Author

p-vdp commented Nov 4, 2025

@h-vetinari Thanks for the quick response. I'm glad this misadventure could be a useful case study for the CFEP!

At this point I'm happy to rebrand the project and relinquish ouroboros for @Glenn032787 (the new owner of ouroboros on PyPI) to use on conda-forge.

Once I come up with a new package name I'll deprecate everything with ouroboros-gis and eventually pull that down as well. ouroboros-gis doesn't have much of an install base yet so it's a good time to take care of all of this.

Should I go ahead and merge this PR?

@h-vetinari
Copy link
Member

Sure, go ahead. If you could also raise a PR to https://github.com/conda-forge/admin-requeststo mark the existing ouroboros builds as broken, that would be splendid!

@p-vdp p-vdp merged commit 82382d6 into conda-forge:main Nov 5, 2025
4 checks passed
p-vdp added a commit to p-vdp/admin-requests that referenced this pull request Nov 5, 2025
Trying to avoid namespace conflicts, see conda-forge/ouroboros-gis-feedstock#10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants