Error: old string incorrect `:�' when linking

[asmeurer]

Linking packages ...
Error: old string incorrect `:�'                                                                                                                        |   0%
Error: post-link failed for: conda-forge::openssl-1.0.2h-0

This was when running conda skeleton. I can't reproduce it outside of that.

[jakirkham]

No clue. I don't think we even have post-link scripts for openssl or its dependencies. conda info?

[asmeurer]

So I recently moved conda-forge above defaults. I think maybe what happened is it thought it was using the conda-forge openssl, but it was really using the one from defaults in my cache. The one in defaults does use a post-link script, to support older versions of conda that don't support binary prefix relocation.

I don't understand why this would result in this crash, though.

[jakirkham]

We ran into this earlier today when doing a Heroku deployment. Not really sure why this is happening as there are no post-link steps in our openssl package or in the feedstock FWICT.

cc @pelson

[asmeurer]

But the defaults openssl does have one. So somehow it is getting called instead.

[jakirkham]

Asking @msarahan about it to see if he has any ideas.

[asmeurer]

Based on strings ~/anaconda/pkgs/openssl-1.0.2h-1/bin/.openssl-libcrypto-fix, the error is indeed coming from the defaults post-link (and that exact error string isn't in conda).

[jakirkham]

Ran into a case of this in a CI build. Hopefully this helps narrow it down more.

[msarahan]

Sorry, I've got nothing on this. Like @asmeurer suggested, I suspect caching misbehavior, particularly if the build strings are identical. It may be beneficial to start adding "cf" to all of our build strings to prevent this from happening. I'm not sure if @mcg1969 might have better ideas.

CC'ing @kalefranz as Conda lead - this is more his area.

[jakirkham]

It may be beneficial to start adding "cf" to all of our build strings to prevent this from happening. I'm not sure if @mcg1969 might have better ideas.

Probably would work, but it is going to be pretty kludgy adding that everywhere. I hope we can do much better than that.

[jakirkham]

Created a simple reproducer. Building this Dockerfile will generate the error everytime. An example build showing this failure can be seen on Quay.

[jakirkham]

Raising as issue ( conda/conda#3319 ).

[kalefranz]

Yeah I think this is probably a pretty ugly conda bug.

On Aug 18, 2016, at 2:56 PM, jakirkham [email protected] wrote:

Raising as issue ( conda/conda#3319 ).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[frol]

Upgrading Conda from 4.2.9 to 4.2.11 solved the issue for me.

[jakirkham]

This was an issue with defaults (i.e. not a conda-forge issue), which I believe has been resolved. Going to close this out.