-
Notifications
You must be signed in to change notification settings - Fork 421
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
Long build root error masked by long-prefix changes #1337
Comments
@msarahan - please close at will. |
You just wanted to claim 1337, didn't you? This is a good point - thank you for raising it, and giving people some information to find. |
I should've held out 20 minutes before submitting 1336. |
Wow - feeling a little behind the times... 😄 I haven't heard of 1337 as a thing b3f0r3... |
As a thing, it would probably be helpful if conda spat out a better message here. Ping @kalefranz to raise awareness. |
I also see the same error. This also fails on conda-build=1.21.3.
|
@licode this error is caused by conda-forge's packages being built with a prefix that is shorter than the prefix that you're trying to install into. Conda-build 2 will try to build packages with a longer prefix, but fall back to a shorter one if any package that it is installing is limited to a shorter prefix. The only way that you'll be successful is to have packages for all of your prerequisites that are built with conda-build 2. They need to be built in order - any dependency with a short prefix will mess up attempts to get a long prefix in something that uses it. Most of the packages in defaults have been rebuilt with the long prefix. Based on your log, it looks to me like you need sqlite and xz from defaults right now, until conda-forge starts using conda-build 2 and rebuilds their packages. |
thanks. I put default before conda-forge in .condarc to make sure we get packages (like sqlite and xz) first from default channel. So it looks working now. |
Hi there, thank you for your contribution! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment. Thanks! |
Just wanted to raise the fact that having a CONDA_BLD_PATH that is long can cause some grief with the new conda-build because of the automatic re-try behaviour implemented in
conda-build 2
.Essentially, conda-build initially tries to build a recipe against a long build prefix, and then when that fails, falls back to trying a shorter prefix. The problem is that the shorter prefix is still too long, and the error message is hard to decipher (it just exits without any information).
Example output:
conda-build doesn't need to do anything about this (as we will soon have packages that can support long prefixes), I just wanted to raise awareness. Ping @bjlittle & @lbdreyer
The text was updated successfully, but these errors were encountered: