Incompatible packages on Windows about magic-wormhole-feedstock HOT 18 OPEN

I'll give it a try

from magic-wormhole-feedstock.

I think the issue here is to get libsodium working on windows properly.

from magic-wormhole-feedstock.

@CJ-Wright can you tell that from the error message and list of conflicts?

from magic-wormhole-feedstock.

No, but I remember windows being an issue

from magic-wormhole-feedstock.

Or maybe it was one of the other deps. I remember that getting the deps on windows was a pain.

from magic-wormhole-feedstock.

I have no idea what is going on with spake here https://github.com/conda-forge/spake2-feedstock

from magic-wormhole-feedstock.

There are files available for spake2 on anaconda.org though:
https://anaconda.org/conda-forge/spake2/files

from magic-wormhole-feedstock.

I think it is coming from python-spake2

from magic-wormhole-feedstock.

Yeah, that seems correct. Is there a problem with python not being a run requirement there?

https://github.com/conda-forge/python-spake2-feedstock/blob/master/recipe/meta.yaml

from magic-wormhole-feedstock.

that could do it

from magic-wormhole-feedstock.

Would you be interested in putting in a PR fixing it?

from magic-wormhole-feedstock.

you might consider giving test downstreams a try

from magic-wormhole-feedstock.

Unfortunately the change to spake8 didn't do anything. I get the same errors even with the new binary posted.

from magic-wormhole-feedstock.

Shoot. One thing to try is to put up a PR that removes the noarch and then use the CI to play around with things.

from magic-wormhole-feedstock.

After looking at the successful build on Windows for py3.6, I realized that the build system was pulling vc and vs2015_runtime from the defaults channel. If I instead run the following on my local machine, I can get it to work:

$ conda create -n wormhole magic-wormhole --override-channels -c conda-forge -c defaults

Should the defaults channel be necessary or does that indicate that something is missing on the conda-forge side that should be there?

from magic-wormhole-feedstock.

hmm, not certain, usually we put conda-forge before defaults with strict, is your conda setup like that?

from magic-wormhole-feedstock.

(also you should consider adding yourself as maintainer to these packages)

from magic-wormhole-feedstock.

I tend to have defaults and then conda-forge, but only use conda-forge to pick up things that are pure-python, unless I'm doing something specific with an isolated environment. Often times then I'll use --override-channels and just pick the specific channel I want.

That said, I see vc on anaconda.org under conda-forge, although the latest build is labeled broken. That's also the case for vs2015_runtime. There are non-broken files, but they only have cf201901 labels and not main. This might be the problem of why it has to go to defaults but I'm not sure.

from magic-wormhole-feedstock.