staged-recipes
staged-recipes copied to clipboard
Add osdf-client
Checklist
- [x] Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
- [x] License file is packaged (see here for an example).
- [x] Source is from official source.
- [x] Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
- [x] If static libraries are linked in, the license of the static library is packaged.
- [x] Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
- [x] Build number is 0.
- [x] A tarball (
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details). - [x] GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
- [x] When in trouble, please check our knowledge base documentation before pinging a team.
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 (recipes/stashcp
) and found it was in an excellent condition.
@conda-forge/staged-recipes, this recipe is ready for review, thanks.
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 (recipes/osdf-client
) and found it was in an excellent condition.
@conda-forge/staged-recipes, this recipe is ready for review, thanks.
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 (recipes/osdf-client
) and found it was in an excellent condition.
Seems like you're trying to publish a fork of a package. We cannot publish the htcondor fork of stashcp under the stashcp name. That would probably be brand hijacking.
We can publish the upstream project, or the fork needs to be rebranded/renamed.
e.g. there are 3 coreutils packages: gnu-coreutils, uutils-coreutils, and m2-coreutils.
Thanks @carterbox. @djw8605 is the primary developer, and owner of both projects, so can hopefully explain that the fork relationship is a relic of the development history and will be sorted out behind-the-scenes.
In the mean time, the 'upstream' opensciencegrid/stashcp project has been archived to mark it as dead.
@conda-forge/staged-recipes, this is ready for another review, thanks.
Ping @conda-forge/staged-recipes, this is ready for review.
Ping @carterbox, are you able to re-review this recipe? Thanks.
I see that the README for the upstream project has been updated to indicate that it is archived. Please allow me to re-review this PR.