-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Adds multiple PERL packages to support biber (stage 1 / subset 1) #29370
base: main
Are you sure you want to change the base?
Conversation
Hi! This is the staged-recipes linter and I found some lint. File-specific lints and/or hints:
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/perl-class-accessor/recipe.yaml:
For recipes/perl-class-accessor/recipe.yaml:
Documentation on acceptable licenses can be found here. For recipes/perl-data-dump/recipe.yaml:
For recipes/perl-data-dump/recipe.yaml:
Documentation on acceptable licenses can be found here. For recipes/perl-class-inspector/recipe.yaml:
For recipes/perl-class-inspector/recipe.yaml:
Documentation on acceptable licenses can be found here. For recipes/perl-data-uniqid/recipe.yaml:
For recipes/perl-class-singleton/recipe.yaml:
For recipes/perl-class-singleton/recipe.yaml:
Documentation on acceptable licenses can be found here. This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13724829481. Examine the logs at this URL for more detail. |
Hi Anjos, great work kicking off this PR—adding these Perl packages to get Biber running on conda-forge is a fantastic step! Linking it to plk/biber#485 really helps tie it together. The linter’s flagged a few things, so here’s a quick rundown to smooth it out. To get this rolling: License File: Could you add a license_file entry to each recipe.yaml? It’s usually LICENSE or COPYING from the package tarball—conda-forge needs that packaged. Once these are sorted, CI should light up green—super excited to see Biber land! Let me know if you’d like help tweaking the recipes. Happy to pitch in—great stuff so far! 😊 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for initiating this process. These recipes in my repo were kind of a mess so I've made suggestions to "standardize" them correctly. Let's see how things look after these changes have been made to these 5 recipes.
Hi Anjos, thanks for kicking this off and being open to sprucing up these recipes—starting messy and refining is totally the way to go! These Perl packages for Biber are a great addition, and I’m glad we’re getting them dialed in. Daniel, your suggestions are spot-on for standardizing—really appreciate the detailed cleanup! Anjos, here’s what I’d suggest folding in from Daniel’s notes to get this humming: Trim the Fat: Drop schema_version and the context stuff (name, sha256)—just hardcode name: perl-class-accessor and sha256: bf12a3e5... in the package and source sections. Keeps it lean since they’re only used once. |
Hi Daniel, thanks for the thorough reviews—your suggestions to standardize these Perl recipes are spot-on and will really help clean things up! I’ve looked into your changes, and they make a lot of sense. Dropping the perl=5.32 pinning to just perl for perl-class-inspector (and all recipes) is a smart move, especially with the goal of a noarch: perl down the line. The test block for perl-data-dump is a great simplification too—swapping run_test.pl for that test section should streamline things. I agree we need to update the Perl feedstock to cover all supported versions before this fully works—otherwise, we might hit build issues. I’d suggest applying these changes across all five recipes: Update host and run to perl (no version) with a comment like # Requires Perl feedstock update for all versions. yaml host:
yaml test:
|
To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks! |
@Varun786223 - you want to close this PR and open a new one with these package fixed? If so, please go ahead! Do not hesitate in picking up further packages from plk/biber#485 (comment). It is going to be a large set of PRs. |
I'm also happy to resubmit these as they were originally my recipes and I know all the quirks! |
No problem, @danielnachun - please go ahead! Let me know how to help. |
Meanwhile, I implemented all required changes (I think) on the latest push. |
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 ( |
Hi! This is the friendly automated conda-forge-linting service. I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13735535409. Examine the logs at this URL for more detail. |
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 ( |
I'll agree on behalf of @conda-forge/perl-packagers to be added as maintainers. Not sure if this will satisfy the linter or not. |
Thanks, guys, for getting these packages into conda-forge. Regarding the bioconda comment in linting, bioconda would like move all perl packages to conda-forge, so this should not be an issue. Once a PR is merged here and the feedstocks are created, a PR should be submitted to https://github.com/bioconda/bioconda-recipes to remove the recipe(s) there. |
@conda-forge/bioconda-recipes, could someone add a comment here to let the linter know these recipes are okay to be migrated from bioconda? |
Asked about this on conda-forge chat and was told it could be ignored. I believe the same is also true of the bioconda overlap messages. Since these are the only remaining errors, once you're happy with everything you can go ahead and request a review/merge of the PR. |
I think this PR is in order, if somebody with powers accept it, I can start the second wave. |
@conda-forge/staged-recipes, ready for review |
To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks! |
@conda-forge/help-perl, ready for review |
@anjos Once everything here is in order, would you mind making next batch 4 PRs of 5 recipes at once? This will enable much faster reviewing because someone can go through a large number of these in one sitting. We'll only have a such a large volume of these recipes in the first pass here - afterward we'll only be able to submit a few at a time as a we "walk" up the dependency tree to |
@danielnachun: I will do all the PRs for stage 1 at once as requested. It may take me sometime tho. Regarding the order of processing, is there any preference for the noarch updates listed in the bottom of plk/biber#485 (comment)? Should I go through the stage 1 updates before going through the new submissions for stage 2? |
I would go through all the stage 1 recipes before trying stage 2 - it's much simpler this way because it means (assuming I made no mistakes) that all the stage 2 recipes will work without needing to worry about missing dependencies. |
@conda-forge/staged-recipes @conda-forge/help-perl I think we are ready to merge here. |
To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks! |
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).Here is the first set of 5 packages no arch to build support for biber at conda-forge, as per discussion in
plk/biber#485 (comment)
ping @danielnachun