-
Notifications
You must be signed in to change notification settings - Fork 431
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
PREFIX detection on Windows failing #3909
Comments
I've added a build test at conda-forge/gobject-introspection-feedstock#20 for the failure case that I'm tracking. In building that |
We do not replace build prefix on any os. |
Please don't refer to the host prefix as the build prefix. They are completely different. |
Looking at this now, sorry for the trouble. |
Sorry for my sloppy nomenclature, and thanks for taking a look! |
conda-forge/yaml-cpp-feedstock#6 (comment) looks to have some more details about how this plays out. I'm not sure if this would still be classed as a |
I think I might discover a regression of the prefix detection logic: Taking
And 6 month later, the maintainer added
And you can notice
@mingwandroid, do you just happen to have any idea where it might go wrong? Does |
@mingwandroid Friendly ping. |
When we make the 3. 19.4 release, hopefully soon, this should be fixed. |
What is the roadmap for 2.19.4? Is there something we can do to help? This is blocking a lot of conda-forge's updates. See conda-forge/qgis-feedstock#124 |
Hi there, thank you for your contribution! This issue has been automatically locked because it has not had recent activity after being closed. Please open a new issue if needed. Thanks! |
Actual Behavior
Text files with the host prefix are not detected and marked in
info/has_prefix
.Expected Behavior
Text files with the host prefix should be detected, marked in
info/has_prefix
, and the prefix should be replaced upon install.Steps to Reproduce
Build on Windows with
conda-build=3.19.1
, see e.g. conda-forge/gobject-introspection-feedstock#19.Output of conda info
Likely related to #3899. It would appear that the fix in #3903 was not sufficient.
(edited for clarity, "build prefix" -> "host prefix")
The text was updated successfully, but these errors were encountered: