I try to install cygnus. I install yum install java-1.6.0-openjdk-devel and run , my problem is:
Then, the developed classes must be packaged in a Java jar file which must be added to the APACHE_FLUME_HOME/lib directory:
$ git clone https://github.com/telefonicaid/fiware-connectors.git
$ git checkout release/0.1
$ cd fiware-connectors/flume
$ APACHE_MAVEN_HOME/bin/mvn package
$ cp target/cosmos-injector-1.0-SNAPSHOT.jar APACHE_FLUME_HOME/lib
in this step, I create cygnus.jar not cosmos-injector-1.0-SNAPSHOT.jar , and # APACHE_FLUME_HOME/conf/cosmos-injector.conf not exist on my flume directory.
Alejandro, I recommend you to install last version of Cygnus (currenty, 0.7.1), which can be installed through RPM packages (recommended). Simply configure the FIWARE repo and install it using yum (CentOS):
$ sudo cat > /etc/yum.repos.d/fiware.repo <<EOL [Fiware]
name=FIWARE
repository baseurl=http://repositories.testbed.fi-ware.eu/repo/rpm/x86_64/
gpgcheck=0
enabled=1
EOL
$ yum install cygnus
You can find the Cygnus Quick Start Guide at this link.
The README will give you extended information about the tool.
Advanced topics can be found at the doc/ folder.
Related
System info
kernel:Linux ubuntu 5.4.0-121-generic #137~18.04.1-Ubuntu SMP Mon Jun 20 07:25:24 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 18.04.6 LTS
Release: 18.04
Codename: bionic
Default version of qemu installed by apt will cause system error when using gdb-multiarch to debug mips executable files. So i'm trying to compile the source codes.
I've installed re2c, ninja and some packages, which are the dependency of qemu.
wget https://github.com/skvadrik/re2c/releases/download/3.0/re2c-3.0.tar.xz
tar -xvzf re2c-1.0.1.tar.gz
cd re2c-1.0.1/
./configure
make -j4
sudo make install
cd ..
git clone https://github.com/ninja-build/ninja.git
cd ninja
./configure.py --bootstrap
sudo cp ninja /usr/bin/
ninja --version
cd ..
sudo apt install build-essential zlib1g-dev pkg-config
sudo apt install libglib2.0-dev binutils-dev libboost-all-dev libssl-dev
sudo apt install libpixman-1-dev libfdt-dev libsdl2-dev
Then i'd like to build qemu statically and get executable like qemu-mipsel(which are static linked so i rename the files with -static suffix). But when i was trying to run any mips executable file, i got error below.
$ ./qemu-mipsel-static (mips_file_name)
qemu-mipsel-static: Could not open '/lib/ld.so.1': No such file or directory
I'm sure that the arch and endian is right. And i copied related lib files in /usr/mipsel-linux-gnu/lib to current directory and using option -L to specify the lib file path. I got the same result.
And i tried the version installed by apt, It can run smoothly.
Commands for installing qemu via apt are as followed.
sudo apt-get install qemu
sudo apt-get install qemu-user-static
sudo apt-get install qemu-system
sudo apt-get install uml-utilities
sudo apt-get install bridge-utils
However, as for the higher version of qemu compiled by source code, when i was tring commands below, it can run smoothly.
chroot . ./qemu-mipsel-static (mips file)
I wonder the reason and how to correctly run the file using ./ and chroot two ways. Thanks for your help!
I have tried
sudo apt-get install ethereum
sudo apt-get install ethereum=VERSION
And
sudo apt-get upgrade ethereum
To install a specific version of Geth but I can't.
An older version of Geth can be installed using tar file, here I am using version 1.8.16. To download the required Geth file, we need to check the OS version using the following command.
> dpkg --print-architecture
amd64
Once you have your OS information, download (amd64 tar in our case) file from the Geth website.
Upload downloaded tar file on a server and extract using the following command:
sudo tar -xvf <filename>
In our case,
sudo tar -xvf geth-linux-amd64-1.8.16-477eb093.tar.gz
Step into extracted folder
cd geth-linux-amd64-1.8.16-477eb093
It should contain the geth file, make it executable with the below command.
sudo chmod +x geth
Copy file to the user bin.
sudo cp geth /usr/local/bin/
Check the Geth version with the following command
> geth version
Version: 1.8.16-stable
Geth is now installed successfully on the system
Ref: How To Install Geth On A Linux Machine
You can get the older versions from here:
https://github.com/ethereum/go-ethereum/releases
To install ethereum on Ubuntu type the following commands into your CLI:
sudo add-apt-repository ppa:ethereum/ethereum
sudo apt update
Once this is done type:
sudo apt install ethereum
So, I want to use Mariadb. There is this Connector-C for it.
https://downloads.mariadb.org/connector-c/
How do I install it? Quiet frankly, the documentation for it is horrible. Even the src file for 3.0.5 is linked to 3.0.4 page.
I did not find a way to install the binary, and the documentation for building from src is quiet vague. I would prefer to know how to install both ways (binary and build from source)
I'm using CentOS7 64bit.
The easiest way to install it would be to use the MariaDB package repository.
curl -sS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup | sudo bash
sudo yum -y install MariaDB-devel
As for building from source, these steps should work on CentOS 7.
sudo yum -y install git gcc openssl-devel make cmake
git clone https://github.com/MariaDB/mariadb-connector-c.git
mkdir build && cd build
cmake ../mariadb-connector-c/ -DCMAKE_INSTALL_PREFIX=/usr
make
sudo make install
And for Ubuntu 20.04...
sudo apt-get install libmariadb3 libmariadb-dev
Raspberry Pi OS
cd to preferred build location. Then install (thanks to #markusjm!):
sudo apt install git gcc make cmake libssl-dev
git clone https://github.com/MariaDB/mariadb-connector-c.git
mkdir build && cd build
cmake ../mariadb-connector-c/ -DCMAKE_INSTALL_PREFIX=/usr
make
sudo make install
Then add installation directory to LD_LIBRARY_PATH. Note: my installation directory is /usr/lib/mariadb. If you cannot find this after your installation, search for e.g. libmariadb.so, a file that should reside in your installation folder.
export LD_LIBRARY_PATH=/usr/lib/mariadb:$LD_LIBRARY_PATH
Afterwards you can finally pip3 install mariadb, if, like me, you tried to do that in the first place.
After you download MariaDB Connector/C, untar and cd. Then mv the executable first.
sudo mv -f bin/mariadb_config /usr/bin/
Now you can execute mariadb_config and will know where to put header and library files to build wheel for mariadb.
For example,
Ubuntu 18.04
sudo mv -f include/mariadb /usr/local/include/
sudo mv -f lib/mariadb /usr/local/lib/
CentOS 7 & Ubuntu 20.04
sudo mv -f include/mariadb /usr/include/
sudo mv -f lib/mariadb /usr/lib/
Finally, you could pip install mariadb. (Or, export CFLAGS=-std=c99 may help.)
After, in the case you cannot import mariadb,
export LD_LIBRARY_PATH=/PATH/TO/where/you/mv/lib/mariadb
I am trying to solve problem installing XMind 3.6.0 RPM on Fedora 23.
I have downloaded the .deb package from XMind webpage.
Than, I have converted it to RPM package with Alien, to be able to install it on Fedora with help of this manual.
sudo alien -r -c xmind-3.6.0-2.x86_64.deb
and than install the generated RPM package
sudo rpm -ivh xmind-3.6.0-2.x86_64.rpm
but I keep getting the error message:
Preparing... ################################# [100%]
file /usr/bin from install of xmind-3.6.0-2.x86_64 conflicts with file from package filesystem-3.2-35.fc23.x86_64
file /usr/lib from install of xmind-3.6.0-2.x86_64 conflicts with file from package filesystem-3.2-35.fc23.x86_64
Does anybody know, how to resolve this conflict?
Thanks,
shimon
I was unable to solve the error described in my post. However, I have found a way to install XMind 7 (3.6.0) on Fedora 23.
Following this page.
The problem is, the xmind binaries structure has changed since this article. So the commands needed are little bit different.
Download Xmind portable version from Xmind web page - http://www.xmind.net/xmind/downloads/xmind7-portable-3.6.0.R-201511090408.zip
Extract it to directory ~/xmind_portable, then cd ~/xmind_portable
Untar the data.tar.gz tar -xf data.tar.gz
Move desktop launcher sudo mv ./usr/share/applications/xmind.desktop /usr/share/applications
sudo mv ./usr/share/mime/packages/xmind.xml /usr/share/mime/packages/
Move application data sudo mv ./usr/lib/xmind/ /opt/
Update mime DB sudo update-mime-database /usr/share/mime/
Make a link to your bin
sudo ln -s /opt/xmind/XMind /usr/local/bin/xmind
Then use it!
xmind
I made the attempt at enabling EPEL on my Fedora 22 machine by running
wget http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm
Then
sudo rpm -ivh epel-release-7-5.noarch.rpm
And now when I run
dnf repolist
I get the following
[sinux1#horrible-host ~]$ sudo dnf repolist
Extra Packages for Enterprise Linux 7 - x86_64 1.8 MB/s | 9.0 MB 00:05
Failed to open: /var/cache/dnf/epel-2b6dfc5904c26562/repodata/49c4e3bd54f19136521be9b254830c954369cc22ce1b661db502ebef13b0004c-updateinfo.xml.bz2.
[sinux1#horrible-host ~]$
I'm stuck and not sure what my next step is. How can I reverse what I did, and what would have been the proper way of enabling EPEL?
Thanks for any input
This is what appears to have worked for me.
Remove the epel repo
rm -rf /etc/yum.repos.d/epel*
then try install epel via dnf
dnf clean all
dnf install epel-release
I did the same as Sinux Tine and ended up in some sort of deadlock.
First try to do like Rup says.
If everything fails, try the following as a last resort. It worked for me.
> su
> cd /var/cache/dnf/epel-2b6dfc5904c26562/repodata
> mkdir throwaway
> mv 49c4e3bd54f19136521be9b254830c954369cc22ce1b661db502ebef13b0004c-updateinfo.xml.bz2 throwaway
That effectively deletes the file which dnf says it cannot open.
When and if the problem is solved, you can delete the throwaway directory and its contents.
Current libsolv version does not have bz2 compression.
Solution: enable bunzip2 compression in libsolv, Basically 'yum update libsolv', then reinstall epel-release.
To complement the answer for Centos 7, I followed the next steps:
Download the libsolv-0.6.14-1.el7 wich was patched
Install it
sudo rpm -ivh libsolv-0.6.14-1.el7.centos.x86_64.rpm
If we get a conflict with the previous version
warning: libsolv-0.6.14-1.el7.centos.x86_64.rpm: Header V3 RSA/SHA1 Signature, key ID 1b6f9f55: NOKEY
Preparing... ################################# [100%]
file /usr/lib64/libsolv.so.0 from install of libsolv-0.6.14-1.el7.centos.x86_64 conflicts with file from package libsolv-0.6.11-1.el7.x86_64
file /usr/lib64/libsolvext.so.0 from install of libsolv-0.6.14-1.el7.centos.x86_64 conflicts with file from package libsolv-0.6.11-1.el7.x86_64
We proceed to remove the previous version
sudo yum erase libsolv-0.6.11-1.el7.x86_64
and install the patched libsolv package
sudo rpm -ivh libsolv-0.6.14-1.el7.centos.x86_64.rpm
We need to reinstall the dnf package manager, because it was removed after to remove the libsolv so we install with the following command.
sudo yum install dnf
We validate it using sudo dnf repolist now it, give us the right output.
Using metadata from Mon Jun 13 10:53:11 2016
repo id repo name status
base CentOS-7 - Base 9,007