-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Fix __version__
contaminated by versioneer due to local patch
#100
base: main
Are you sure you want to change the base?
Fix __version__
contaminated by versioneer due to local patch
#100
Conversation
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 do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12309442179. Examine the logs at this URL for more detail. |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub Actions workflow below for more details. You can also ping The following suggestions might help debug any issues:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12308580391. Examine the logs at this URL for more detail. |
__version__
contaminated by versioneer due to local patch
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub Actions workflow below for more details. You can also ping The following suggestions might help debug any issues:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12308888227. Examine the logs at this URL for more detail. |
It seems every few weeks I need to catch up with the latest conda-forge development... I suspect this has to do with the global pinning updated to 12.6, but I can't tell what's the right solution. Time to ping @conda-forge/cuda 😄
|
@conda-forge-admin , please re-render |
…onda-forge-pinning 2024.12.13.03.36.57
@conda-forge-admin , please re-render |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12309444583. Examine the logs at this URL for more detail. |
596e7a2
to
d0788e8
Compare
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 ( |
From 240fbb78b2a7746a3ad026070cd5e5d6deaaa337 Mon Sep 17 00:00:00 2001 | ||
From: Vladislav Zhurba <[email protected]> | ||
Date: Fri, 8 Nov 2024 16:28:13 -0800 | ||
Subject: [PATCH] Fix discovery for trampoline files |
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.
Don't we need this patch to fix cimport
s or is there another fix for that?
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.
What happened was that when we figured out the patch, I applied it directly to here (Nov 10, 4:51pm ET) while upstream was still being updated (tagged at Nov 12, 7:14pm ET). So at the time of rebuilding in this feedstock, we were using the previous tag + local patch. Now we are switching to the latest, fixed tag. The validity of the package (cimport
is fixed) is ensured through the tests I added when rebuilding. Had I remembered the potential impact of versioneer I would have looked at __version__
and decided to not rush into rebuilding...
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.
patches: | ||
- 0001-include-pxd-pyx.patch | ||
# TODO: remove the hard-coded .post1 in the next release | ||
url: https://github.com/NVIDIA/cuda-python/archive/refs/tags/v{{ version }}.post1.tar.gz |
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.
Should we move the post1
into version
above?
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.
I was trying to not make it as part of the version string (as far as conda is concerned) and only use build number to indicate it's a rebuild (with potential fixes). Do you think it's affecting __version__
?
Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #99.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.
Fixes #99
xref: NVIDIA/cuda-python#308