I reinstalled miktex multiple times now, but I still get the same error, when updating or installing new packages: The executed process did not succeed (fileName="[path to miktex 2.9 directory]\miktex\bin\x64\miktex-fc-cache.exe", exitCode="1").
I installed it only for my user and let it update packages on the fly.
I already checked, whether the path name contains any unusual symbols or spaces, but the only instance of a space is the very own directory "MiKTeX 2.9".
Unfortunately I don't know how to interpret the miktex report, so I can't find the error myself.
I also tried installing TeXLive but had the same problem, that it could not install any packages.
Related
I realize that a requirements.txt file can be used to pin the versions used in pip install. Sometimes I don't want to go through all that- and just simply want to protect my installation from downgrades. Is there any way to instruct pip install to do that?
An example: I just installed librosa and it downgraded numpy from 1.24.1 to 1.23.5 . I don't want that behavior to happen unless I explicitly request. On the other hand if there are missing dependencies then please let's grab them.
For this installation of python it is acceptable to take the risk of occasionally ending up with a mismatch due to installing newer versions [ but I don't want older ones].
When I use iPython to run some scripts, I've got the following warning message in iTerm:
/Users/###/anaconda3/lib/python3.6/site-packages/ipykernel/displayhook.py:12:
VisibleDeprecationWarning: zmq.eventloop.minitornado is deprecated in pyzmq 14.0 and will be removed.
Install tornado itself to use zmq with the tornado IOLoop.
When I try to run my code in Visual Studio Code, I've got the following error message:
Error message in VSCode
I have already tried to update Anaconda, I have already tried to install nomkl with conda as well, without any success.
iTerm and VisualStudio on Mac OS 10.14.6, Anaconda up to date (4.7.12)
Remedy Option A)
Use anaconda-tools to separate an environment, say aLastWorkingENV, where you make use of anaconda-tooling to roll-back all components to a last working state, which does not whine about future deprecations. In such aLastWorkingENV environment, all thus synchronised programs will work smooth (as they did before a first component update, that has moved the stick)
Remedy Option B)
Use anaconda-tools to update all current components and all their supporting modules and all packages versions [ python, ipython, pyzmq, jupyter, ..., ] to their most recent versions, where products QA coverage ought either confirm the PASS, or provide a remedy or workaround or the last-trouble-free version ( to eventually downgrade one such package, based on such exception, if present and relevant )
Either way, your code would stop throwing the soft-warnings and remain in such state, until any un-coordinated package update takes place.
How do you get LaTex output on Spyder? I saw some other post recommending installing the MikTex package but I don't know how to use it.
I installed the MikTex package on Anaconda Spyder, but now how do I use it? I have:
import sympy as sp
sp.init_printing()
x = sp.symbols('x')
integrate(x)
But nothing
I had troubles getting Latex output to work in Spyder too, and I was able to hunt the bug down. At least for me, the Miktex installation delivered by the conda miktex package got confused about being a shared or a single-user installation, and consequently failed to install the necessary packages on-the-fly.
Here's my strategy:
Verify if you have the same problem by looking at the Miktex log files (on Windows, in your user's AppData\Local\Miktex\2.9\miktex\log directory); watch out for lines like
installing package (...) triggered by (...), immediately followed by entries marked FATAL with the error message Administrative mode cannot be enabled (makes no sense) because this is not a shared MiKTeX setup.
If this is the same issue for you, start the Miktex console in the conda Miktex package; the location is (Anaconda dir)\Library\miktex\texmfs\install\miktex\bin\miktex-console.exe. (Trying to run the _admin version fails with a similar "Administrative mode" error message.)
In the console, go to "Packages", and manuall install the following packages: standalone, varwidth and zhmetrics
After these steps, Latex output worked for me. Note that these package installations are user-specific, so you'll have to repeat them for each user.
I want to install the package dataframe of Octave on one of my servers, which does not have internet access. I used my laptop to download dataframe-1.1.0.tar.gz. I wonder how I can install it on my server manually.
In the README.html of Octave 4.0.0 folder you can find the following passage:
Included Octave Forge Packages
A number of Octave-Forge packages have been included with Octave, however they must be installed in order to use them.
To install:
• Start Octave and then open the build_packages.m file found in the src folder where Octave was installed.
• Run the script build_packages.m to build and install the packages.
Installation is a one-time procedure. After installation packages must still be loaded in order to use them with the pkg load PACKAGENAME command.
Other packages are available from Octave-Forge.
What you need to do for other packages, which are not included with Octave, is: download the package from http://octave.sourceforge.net/packages.php. Then put the package in the src folder and modify build_packages.m respectively before executing it.
According to the Octave documentation:
37.1 Installing and Removing Packages
Assuming a package is available in the file image-1.0.0.tar.gz it can
be installed from the Octave prompt with the command
pkg install image-1.0.0.tar.gz
If the package is installed successfully nothing will be printed on
the prompt, but if an error occurred during installation it will be
reported. It is possible to install several packages at once by
writing several package files after the pkg install command. If a
different version of the package is already installed it will be
removed prior to installing the new package. This makes it easy to
upgrade and downgrade the version of a package, but makes it
impossible to have several versions of the same package installed at
once.
After making cabal install of the darcsden code I get this message:
cabal: The following packages are likely to be broken by the reinstalls:
bin-package-db-0.0.0.0
ghc-7.4.1
Use --force-reinstalls if you want to install anyway.
How do I get around this? What does it mean?
Why does it happen?
If you look at the full output of cabal install darcsden, you will find several lines that look like this:
binary-0.5.1.0 -bytestring-in-base (reinstall) changes: array-0.4.0.0 ->
0.3.0.3, containers-0.4.2.1 -> 0.4.1.0
This means that cabal has found an install plan that involves (destructively) reinstalling packages that you already have on your system.
Now, GHC packages are rather sensitive when it comes to their (reflexive) dependencies, and generally only work if exactly the right version of all dependencies is available, compiled against the right versions of their dependencies and so on. Therefore, replacing an already installed package with a new version of changed dependencies can cause some packages on your system to become unusable. Since version 0.14.0, cabal warns you about such a situation in advance to prevent you from accidentally breaking your system.
In your case, ghc and bin-package-db are among the potentially broken packages, because they depend on binary which gets reinstalled. So you should not try to use the --force-reinstalls flag, because it might really break your GHC.
What can you do?
If you scan what is going to be reinstalled, you see that quite a few dependencies are downgraded. This hints at the fact that the package you are trying to install might not be properly updated to GHC 7.4.1 yet.
You can in general try to call cabal install darcsden --avoid-reinstalls to explicitly try to find an install plan that has no reinstalls. Unfortunately, in this case, it fails (for me).
I've briefly looked at the darcsden package description, but it looks like quite a few dependencies of darcsden need to be updated. So the remaining options are: Convince the author(s) of darcsden to release an updated version, or install darcsden using an older version of GHC (such as 7.0.4), which should just work.