Skip to content

Conversion fails due to incompatible package install? #8628

Open
@jakirkham

Description

@jakirkham

Appears that conversion fails due to attempting to install incompatible packages. It seemed to be related to the openssl version installed, but fixing the openssl version didn't seem to work. Not sure what else might be causing it.

cc @conda-forge/core

Activity

jakirkham

jakirkham commented on Jun 24, 2019

@jakirkham
MemberAuthor

It's worth noting that conversion worked previously with Conda 4.7.4. So that doesn't seem like the issue.

jjhelmus

jjhelmus commented on Jun 24, 2019

@jjhelmus
Contributor

The python 3.7.3 package that is found requires openssl >=1.1.1b but the specification given on the install command explicitly require openssl 1.1.1a. Can that spec be dropped from the install line?

pkgs/main/linux-64::python==3.7.3=h0371630_0 -> openssl[version='>=1.1.1b,<1.1.2a']
jakirkham

jakirkham commented on Jun 24, 2019

@jakirkham
MemberAuthor

So that should have been solved with PR ( #8626 ) as seen here. Unfortunately it still runs into installation issues later. Though I may be missing something else.

jakirkham

jakirkham commented on Jun 24, 2019

@jakirkham
MemberAuthor

Strange. Seems this build didn't run into the same problem. Not sure what changed.

jakirkham

jakirkham commented on Jun 24, 2019

@jakirkham
MemberAuthor

Though this build is now back to the original problem. 😕

jakirkham

jakirkham commented on Jun 24, 2019

@jakirkham
MemberAuthor

Apparently just retrying made the build work. Something really strange is going on here.

jakirkham

jakirkham commented on Jun 25, 2019

@jakirkham
MemberAuthor
jakirkham

jakirkham commented on Jun 25, 2019

@jakirkham
MemberAuthor

Looks like all builds today failed until this one. Seems the failures are becoming more frequent.

jakirkham

jakirkham commented on Jun 26, 2019

@jakirkham
MemberAuthor

@jjhelmus, I'm not sure I follow your suggestion. openssl 1.1.1b is already included when this failure occurs. What am I missing?

jakirkham

jakirkham commented on Jun 26, 2019

@jakirkham
MemberAuthor

Is it possible that Conda does not think 1.1.1b is within >=1.1.1a,<1.1.2a?

scopatz

scopatz commented on Jun 26, 2019

@scopatz
Member

Thanks for looking into this @jakirkham

jjhelmus

jjhelmus commented on Jun 26, 2019

@jjhelmus
Contributor

I'm not sure I follow your suggestion. openssl 1.1.1b is already included when this failure occurs. What am I missing?

I was thinking of when openssl was pinned to 1.1.1a in #8626. This would prevent an update to 1.1.1b which is required for Python 3.7.3

jakirkham

jakirkham commented on Jun 26, 2019

@jakirkham
MemberAuthor

Yeah I tried that in response to update failing when we still had openssl 1.1.1b included thinking it might help. This still happens even when forcing openssl 1.1.1b.

Edit: I'll acknowledge I'm mostly guessing ATM.

jakirkham

jakirkham commented on Jun 26, 2019

@jakirkham
MemberAuthor

Alright I've tried to make things work with Conda 4.7, but it doesn't seem to be working. Am proposing we just pin to Conda 4.6. ( #8650 ) Please merge that PR if you agree.

jakirkham

jakirkham commented on Jun 26, 2019

@jakirkham
MemberAuthor

Have raised upstream issue ( conda/conda#8828 ).

Let's leave this issue open until we've seen conversion work reliably for a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

      Participants

      @scopatz@jjhelmus@jakirkham

      Issue actions

        Conversion fails due to incompatible package install? · Issue #8628 · conda-forge/staged-recipes