Conda installs 0.6.3 instead of 0.7.x #24
Comments
|
Tagging off the comment thread conda/conda#9607 , @msarahan suggests that it's a problem with our package: conda/conda#9607 (comment) (tldr, unable to create an environment where the package can be installed). This seems very unlikely to me, since it works on every other platform and our package is noarch. Instead, I think it's more likely that there's an inconsistency in the dependency chain on windows platforms, possibly only on py3.7. (FWIW, we have test CI on appveyor using python 3.6 on conda and it works fine.) @Keanri828 can you try removing the visual studio package ( |
|
It seems like this would literally wipe out my environment: What's the use of this package? Seems like it's essential for Anaconda/Python on Windows. |
|
Ah yikes! I guess it must be necessary for installing / compiling packages from source when there are C/C++ extensions involved (eg numpy or anything using cython). This is very much outside my expertise, and I don't see how/why it should come up specifically for librosa. Our dependency stack has a few constraints, but it's nothing totally wild as far as I know. At this point, some assistance from the conda-forge community would be very much appreciated! |
|
@bmcfee what version of conda is your CI running? The fact that you can't create an environment at all with only librosa specified indicates that librosa has a conflict among its indirect or direct dependencies. I'm very confused as to why this works on your CI but not in general. Can you link me to an appveyor log that succeeded? |
To be clear, I was able to successfully create an environment with just librosa on my dev machine (ubuntu, latest conda) following your example: So I'm pretty confident that the problem is confined to the dependency chain on windows, and not the package itself (which is noarch anyway). On our CI, we conda-install most of the dependencies, but obviously not the packaged librosa. Some of the dependencies are installed by pip on our appveyor instance, but here's a recent build log: https://ci.appveyor.com/project/bmcfee/librosa/builds/30077025 |
|
Sorry I wasn't clear. Yes, the problem is confined to windows. The problem is in the pysoundfile package. It depends on libsndfile, but that package does not exist. All we have on windows is a different beast, m2w64-libsndfile. This is a different name because it is from a completely different compiler stack (mingw as opposed to visual studio). This kind of messes up the ability to make pysoundfile noarch, because selectors are not allowed (they take effect at build time, not run time). There could be a scheme to unify these using metapackages, though. |
|
Aha, that makes total sense -- thanks for the sleuthing! 🕵️♂️ It does sound like a metapackage for pysoundfile is the way to go. I gather that's a long-term solution though, any suggestions for how to work around this for the time being? |
|
Simplest is to just remove noarch from pysoundfile, add the selectors, bump the build number. I would then add an issue on the pysoundfile repo and also put a comment in the recipe as to why the selector is needed, and note the possibility of a metapackage to get noarch back. There might also be something we can do to help the bot understand that the recipe can't be noarch, but the selectors should be enough. |
|
Sounds like a plan. I'm not sure how to go about that (read: don't quite have the bandwidth to do it), but I can raise the issue over in the pysoundfile feedstock. |
|
Hi, I had the same issue on W10 : conda doesn't install the last version of librosa. I solved my problem simply by using pypi to install librosa 0.7.2 inside my conda env, and everything seems to work well. |
Hello there. :-)
Issue:
This issue "moved" from librosa (librosa/librosa#1060) to conda (conda/conda#9607) and now it's here. By using the command
conda install -c conda-forge librosaon Windows conda installs version 0.6.3. This happened on two different Windows-computers so far. The installation process on Mac worked correctly. To reproduce my thesis' environment I installed pandas first and then librosa.In another environment I tried to install librosa 0.7.2 via
conda install -c conda-forge librosa, but the installation process failed with the following output:Environment (
conda list):This is my environment with "successful" librosa installation (but with wrong version).
Details about
condaand system (conda info):The text was updated successfully, but these errors were encountered: