-
Notifications
You must be signed in to change notification settings - Fork 19
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
Install trouble - nextflow incompatible packages #31
Comments
oh man sorry for the delay. Window/WSL, honestly I personally have not done too much testing on it. Perhaps it woudl be better to totally create a fully separate conda environment that is clean to install rather than building upon an existing base. |
Whether I attempt to run timsconvert via the Anaconda prompt or directly via Python on the ordinary command line on my Windows 11 workstation, I get errors that there is "no module named 'timsconvert'." The complexity of installation required for sophisticated Python tools is often error-prone enough for me to decide not to use them. |
Hi @tjlundgren, apologies for the delayed response but did you have any luck with the conda environment setup? Since you are just running this on Windows, nextflow should not be necessary, and you can invoke TIMSCONVERT from the command line without it (see this section in the README). |
@dtabb73 apologies for the delayed response as well, and I'm sorry about the installation difficulty. That error generally occurs if the use of symbolic links are not enabled while cloning the repo using Git (see see Step 6 here in the README. I'm not sure if this has changed in newer versions of Git, but previously when installing Git on Windows, you would need to check the box labeled "Enable symbolic links" as seen in the image below. Unfortunately, if that was not enabled, a reinstall of Git may be the easiest option to enable it, followed by cloning the TIMSCONVERT repo again. |
i reinstalled git with symbolic link enable checked but still i am facing probably a similar issue running Docker image created in windows via cmd.exe
|
just an update, it seems to have worked via WSL 👍🏽 so i have loaded up the created docker image to hub https://hub.docker.com/r/animesh1977/timsconvert which can be pulled via windows cmd.exe
and it seems to be running just fine 🤞
|
Thanks for the update. The Docker container was written with Linux/Ubuntu in mind, so it makes sense that it only works in WSL. |
Hello,
I was hoping to try your software locally, but ran into some issues getting started. I was following the instructions for an anaconda installation in the readme file, but ran into this problem when installing nextflow. I've copied my terminal text below. I also tried using the package directly through command line but ran into a couple errors I think were due to bad install. Sorry if this isn't very helpful, I'm not much of a programmer....
(timsconcert) PS C:\Users\Lab Admin> conda install -c bioconda nextflow
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: /
Found conflicts! Looking for incompatible packages.
This can take several minutes. Press CTRL-C to abort.
failed
UnsatisfiableError: The following specifications were found to be incompatible with each other:
Output in format: Requested package -> Available versions
Package zlib conflicts for:
nextflow -> curl[version='>=7.76.1,<8.0a0'] -> zlib[version='>=1.2.11,<1.3.0a0']
python=3.7 -> sqlite[version='>=3.33.0,<4.0a0'] -> zlib[version='>=1.2.11,<1.3.0a0']
Package vs2015_runtime conflicts for:
python=3.7 -> vs2015_runtime[version='>=14.16.27012,<15.0a0']
python=3.7 -> vc[version='>=14.1,<15.0a0'] -> vs2015_runtime[version='>=14.0.25123,<15.0a0|>=14.0.25420|>=14.15.26706|>=14.27.29016|>=14.16.27012']
Package vc conflicts for:
python=3.7 -> openssl[version='>=1.1.1e,<1.1.2a'] -> vc=9
python=3.7 -> vc[version='14.*|>=14.1,<15.0a0']
The text was updated successfully, but these errors were encountered: