I have a docker image with texlive installed (via apt not tlmgr). I have a pgfplot in my project which needs a newer pgfplot version. I'm searching for ways to update my pgplots because I can't update it with tlmgr because of base install via apt.
Initial error message if I try to compile with texlive 2014:
! Package pgfkeys Error: Choice '1.16' unknown in choice key '/pgfplots/compat/
anchors'. I am going to ignore this key.
See the pgfkeys package documentation for explanation.
Type H <return> for immediate help.
...
l.7 \pgfplotsset{compat=1.16}
?
! Emergency stop.
...
l.7 \pgfplotsset{compat=1.16}
I downloaded the pgfplots.tds and did the following steps like the manual said:
docker cp pgfplots.tds docker_container_name:/root/texmf/pgfplots
export TEXINPUTS=/root/texmf/pgfplots/tex//:
export TEXDOCS=/root/texmf/pgfplots/doc//:
export LUAINPUTS=/root/texmf/pgfplots//:
texhash
Of course the export and texhash were done inside the container and not on the host system.
After this, the error message is gone, but I have a new issue:
package pgfplots notification 'compat/show suggested version=true': you might b
enefit from \pgfplotsset{compat=1.18} (current compat level: 1.16).
! Illegal parameter number in definition of \pgfmaththisrow#.
<to be read again>
I searched online and got the response that this is because of a broken pgfplots installation. In many articles the fix was just to install the texlive new. But I can't do that.
The issue should also not be in the tex code itself. If I install texlive on my host system, which is the most recent Ubuntu distro, the tex compiles just fine.
Can somebody help me in fixing this or lead me to a better way of upgrading pgfplots?
Resolution:
The pgfplots package 1.18.1 and also 1.16 were to recent. It had conflicts with the pgf package. I tried to go further back and landed on \pgfplotsset{1.14} and version 1.14 of pgfplots.tds.
This works fine now. I was probably pretty lucky that my plot looks and functions the same with this version as in 1.18.
This approach probably won't work for you if your more bound to version 1.18.
Related
I've always been able to compile sources from git repository https://github.com/GNOME/vala.git on my PC running "Linux Mint 18.3 Cinnamon 64-bit". I have the latest valac (0.42.4-0ubuntu1~16.04~valateam0) installed.
The last successful compile I did was from version 0.40.0.257-40b5-dirty. Today, I downloaded the latest vala.git, but when i run ./configure I get:
./configure: line 12579: syntax error near unexpected token `$flag,TEST_CFLAGS="$TEST_CFLAGS $flag"'
./configure: line 12579: ` AX_CHECK_COMPILE_FLAG($flag,TEST_CFLAGS="$TEST_CFLAGS $flag")'
Do I need to make additional environment changes? Not sure were to go from here.
Compiling Vala from source is a good start in contributing back to the Vala project. Vala currently uses autotools as its build system. For Ubuntu AX_CHECK_COMPILE_FLAG is provided by a separate package: autoconf-archive. See the autotools syntax error with ax_check_compile_flag answer on Stack Overflow for more details. So you should just need to install autoconf-archive.
By the way the main repository for Vala is in GNOME's GitLab instance: https://gitlab.gnome.org/GNOME/vala You may want to clone that one instead. The GitLab instance also allows issues to be raised and merge requests to be submitted.
I've Googled this a thousand times and I cannot, for the life of me, get VIM to work on my Minix 3. For the record, I am running on a Windows machine with Minix 3 working on Oracle's VM VirtualBox.
I've tried typing,
# pkgin up && pkgin in vim
but I get the error:
pkgin: Can't open database /usr/var/db/pkgin/pkgin.db: unable to open database file: No such file or directory
I then try to do pkgin search git to search for a package, but I get the same error. Could this be some kind of Internet connection issue? I'm incredibly confused.
If you haven't already, download the binary package from here:
ftp://ftp.minix3.org/pub/minix/packages/3.3.0/i386/editors/
Change "i386" to your correct architecture, if different.
As you're probably already familiar, this page tells you how to install binary packages for Minix:
http://wiki.minix3.org/en/UsersGuide/InstallingBinaryPackages
As far as your "pkgin" errors, here are two possible solutions:
http://osdir.com/ml/minix3/2011-03/msg00244.html
How to install vim into Minix3?
I asked on the Minix 3 Google Groups Forums and they solved my problem. If anyone else has trouble, I'm pasting a response by Lionel:
Switch to http downloads by editing "/usr/pkg/etc/pkgin/repositories.conf" and comment out the line:
ftp://ftp.minix3.org/pub/minix/packages/$osrelease/$arch/All
and add the following:
http://www.minix3.org/pkgsrc/packages/$osrelease/$arch/All
Then do shutdown, boot, pkgin update and then install your desired packages.
I am trying to install the latest PTAM (Parallel Tracking and Mapping) as described on the Installation page (http://wiki.ros.org/ethzasl_ptam#Installation). However, when running "rosdep install ptam" it yields the following error:
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
ptam: Cannot locate rosdep definition for [ptam_com]
I have followed the exact same procedure on a different system one month ago (before PTAM was changed to catkin) and it worked. The reason for changing the system is that the GUI of PTAM is said to be successfully loaded but it is actually not showing. So we changed to a new system with an nvidia graphics card.
I tried to retrieve the old version from Github on the new system but it yields the same error.
Many thanks.
ROS has its own very active answer forum. So questions like this should better be answered there. Besides,
Cannot locate rosdep definition for
This indicates that "ptam" is not yet registered as the rosdep key (I'm looking at Ubuntu).
The process for adding new keys may not be documented, but you could refer to thread like this and see if you can pick up.
In attempting to install the latest ImageMagick (and devel) RPM from http://www.imagemagick.org/download/linux/CentOS/x86_64/ I receive this message
ImageMagick-libs = 6.8.5-8 is needed by ImageMagick-devel-6.8.5-8.x86_64
Confusingly, there is no ImageMagick-libs RPM listed, and searching has yet to yield a solution. Is there a way around this existential dependency?
Neither I nor Google know where ImageMagick-libs lives nor what it contains, but for posterity this gets things up and running on CentOS 5.8 (the distribution listed on imagemagick.org):
>: rpm -Uvh --nodeps ImageMagick-6.8.5-8.x86_64.rpm ImageMagick-devel-6.8.5-8.x86_64.rpm
>: ln -s /usr/include/ImageMagick-6 /usr/include/ImageMagick
The symbolic link was necessary for software relying on ImageMagick header files.
If someone were to stumble upon this, the ImageMagick-libs RPM are now downloadable from the link in the question.
I ran into the same thing when building the RPMs myself.
line 66 of the SRPM's included ImageMagick spec file includes:
Requires: %{name}-libs = %{version}-%{release}
I just commented out that line and the build completes; the resultant RPM satisfies the requirement cleaner. In sum, I believe it a bug in the SPEC file bundled in the SRPM. It isn't necessary for functionality even when building against php magickwand and similar finicky tools that require headers from ImageMagick.
I'm having trouble running Agda on my windows 7 64-bit pc. I tried running the following commands:
cabal install agda
and
cabal install agda-executable
which both work, but I still can't seem to get it going with emacs, can someone help me? I've tried the one click installer from here but it doesn't seem to work, I run into this complaint:
C:\agda2\bin\agda2-install.cmd failed.
Code = 1
Incorrect Function
Setup was not completed.
Please correct the problem and run setup again
Install Agda (cabal install agda agda-executable), make sure agda-mode.exe is on search path. This required because installer will put something like (shell-command-to-string "agda-mode.exe locate") to .emacs file.
run "agda-mode setup".
My Emacs bin directory is also on the search path but I'm not sure if it required or not. Anyway, you will get error messages if you'll do something wrong.
You will also need Haskell mode (can be obtained from here https://github.com/haskell/haskell-mode) and you will have to add (load "c:\\haskell\\dev\\haskell-mode\\haskell-site-file.el") to your .emacs file. I load it prior to Agda stuff, I do not really know does load order matter or not.
I have GHC 7.0.4 (with Haskell Platform 2011.4.0.0) and I could install Agda 2.3.0 installer in Win7 64b without problems.
If you have GHC 7.4, you should try Agda 2.3.0.1