I can't seem to find how to install the 4.0.5.1 version of mono for ubuntu 16.04.
i've tried changing it in sources.list.d but when I do mono --version, it's still the 4.2.1 version.
Keep in mind this is my first time using linux. I'm just trying to setup an AFK script for minecraft alts on my vps.
Related
I am very new to Cytoscape, which I need for my thesis and I need to use this specific version.
I installed it on my Laptop and on the installation instructions said to install the Java 2 Runtime Environment, version 1.4.2 or higher.
I could not install this version or SE 5/6 so eventually I installed the version 17.0.1. I launched cytoscape 2.8.2 using the following commands on cmd on Ubuntu
chmod a+x cytoscape.sh
./cytoscape.sh
I get these errors:
cmd errors, cytoscape error console
Ubuntu details:
Description: Ubuntu 20.04.2 LTS,
Release: 20.04,
Running on VMware® Workstation 16 Player, v16.1.0 build-17198959
Wow. That's a really old version of Cytoscape! That version was released 10 years ago. There is no way it will run with Java 17 (the newest LTS version). In fact, the current release of Cytoscape won't run on Java 17. We are working on that support for Cytoscape 3.10.
Your best bet is installing the oldest Java possible. It might simply not be possible without having a 10 year old machine that hasn't been updated and still runs.
I am trying to run my pharo2.0 application on CentoOS which was previously been installed in a mac. The original version is pharo2.0 so I need to run the same image CentoOS too, but I get an error which says this below :
/lib/libc.so.6: version `GLIBC_2.15' not found (required by xxxxx)
Should I be trying to upgrade the CentoOS and see if pharo2.0 works or port my whole application to a later version of pharo?
There is now a VM build especially for systems with an older libc version. In fact there is a build for Centos specifically (which has a slight variation in linkages from Debian), the latest version of which is permalinked here. See http://pharo.org/download#custom for more info.
I attempted to update my version of SVN from 1.7 to 1.8 as per this guide:
http://snippets.khromov.se/subversion-1-8-centos-6/
All seemed to install fine, however now I have an issue when I try to restart Apache:
/usr/sbin/httpd: symbol lookup error: /usr/sbin/httpd: undefined symbol: apr_crypto_init
Does anyone know how to solve this?
Which packages need to be updated?
I had same issue after installing some perl modules.
I did the following to resolve it:
yum remove vulture-common-3.2-185.1.x86_64
cd /usr/lib
ln -sf libaprutil-1.so.0.2.9 libaprutil-1.so.0
ln -sf libapr-1.so.0.2.9 libapr-1.so.0
apr_crypto_init is new with APR-Util 1.4.x. CentOS 6 should already have APR-Util 1.4.x. So either you're not using CentOS 6 which those instructions are made for or you're not using the apr-util/httpd version that comes with CentOS 6.
If you're not using CentOS 6 then I suggest you go get a version built for your distribution from WANdisco's download site (the script that the site you linked to actually is from WANdisco).
If you're using your own httpd version you'll either have to switch or you'll have to build your own copy of Subversion.
I have had similar experiences with other applications using this library and Centos 6.x. I have tracked most of the problems down to using the 'minimum install' version of the OS. From what I have been able to determine, the minimum or light install versions of Centos have a tendency to have older versions of the binaries. For example, my version of APR-Utils are 1.3x even though I am using version 6.6.
This is supposedly done for better stability and backward compatibility from what I can find but it causes some headaches if you aren't aware. You may need to use a more 'complete' version of the OS in order for this library to be the latest version, provided you are starting from scratch.
I've been trying to set Vagrant up for local development on my machine. I see from Apache's official website that 2.4.7 is the current stable version. And I had no issues installing it on my VPS. But with Vagrant it's a different story. I'm trying with both Base64 and Base32 boxes. This is the command i'm running:
sudo apt-get install -y apache2
It should install apache 2.4.x. But it doesn't. Sometimes it installs version 2.2, sometimes 2.4. This is driving me nuts, since the whole idea of using Vagrant is to have the same Virtual machine replicated everywhere. Any ideas?
Because the Debian based distro (possibly Ubuntu) you're using is still using 2.2.x. Switching to 2.4.x from 2.2.x means all the 3rd party modules they ship have to be upgraded (or at least rebuilt) so they probably haven't made the switch yet.
I had an ubuntu server with mono 2.10.8 apache and mod_mono
I wanted to update mono at ver 3.2.3 so I downloaded the source from github and compile it.
Everithing seems ok in fact from the terminal if I type mono --version I get 3.2.3
but if I try to access a website on the server (when I get an error page) it says 2.10.8.
What's wrong?
Note that I have restarted apache after the update.