-
-
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
Added PySparse #6586
Added PySparse #6586
Conversation
Might wish we had it for linux
- adjust version string - switch from PyPI (doesn't build) to sourceforge - remove `nomkl` from Windows builds - fix dev_url
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/pysparse:
For recipes/pysparse:
|
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/pysparse:
|
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 ( |
Per [recommendations of looooo](conda-forge#6586 (review))
Something's trying to use vc9
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/pysparse:
|
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 ( |
Hopefully fortran is what's invoking vc9 and hopefully we don't need it
@conda-forge-coordinator, @conda-forge-manager: this recipe passed all checks seven days ago. Can it be merged? [FWIW, I'm trying to "ping @conda-forge/staged-recipes to request action", but GFM doesn't recognize that @mention] |
Hi, sorry for the delay , sometime it happens :/ I will review your PR right now |
Because [it's broken](https://sourceforge.net/p/pysparse/bugs/14/) we patch the [pip tarball](https://files.pythonhosted.org/packages/19/73/4429c57b285fa77ffabbfc078f35e2b7ef18eb317e8c82e2c8ff6992d5ae/pysparse-1.3-dev.tar.gz) to make it consistent with [git@512f26fa](https://sourceforge.net/p/pysparse/git/ci/512f26fa339d68583926155bb72cda08318d33ff/tree/)
If you read the log of the CI, you will see that your project is not being packaged. I need to investigate that |
@ocefpaf , could you please take a look on that? The package is not being created.
|
ping @conda-forge/staged-recipes |
recipes/pysparse/meta.yaml
Outdated
|
||
build: | ||
number: 0 | ||
skip: True # [not py27] |
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.
@guyer and @marcelotrevisani let's see if this fixes it.
It does not like the directory :-/ |
@guyer and @marcelotrevisani now we got a real failure to deal with 😄
|
@ocefpaf I regenerated the patch, but it's identical. What changed in the process? The patch was happily being applied since it was added two days ago. |
My impression is that the package was not getting built, so the patch was never applied, but I may be getting lost in the CI logs. Either way the patch looks oddly to big and it does not seem to be created with |
@ocefpaf I've rerun the diff with I don't know what to do about the "oddly to big" part. The available tarball is a disaster. Piles of code is missing completely. I already truncated the diff substantially by omitting the missing documentation and examples. |
I meant |
GitHub will let you "View" the overly big diff. Adding Thanks for pointing out that it wasn't even building before the changes you and @marcelotrevisani made to my meta.yaml. |
@conda-forge/staged-recipes: @ocefpaf merged this to master three days ago (thank you!), but then it's been sitting in |
See #6659 for more info on the issue. |
No description provided.