I am trying to use md5deep on ubunutu. I have run the following commands:
sudo apt-get update
sudo apt-get install md5deep
This successfully installs. However, I then run:
md5deep
And get the error message:
md5deep:command not found
I have read the first 10-20 google pages on installing this and watched a number of youtube videos but unable to get part this first step.
Can anyone explain what I am doing wrong here? (not sure if this is a linux question rather than a md5deep question)
My output for:
dpkg -L md5deep
is:
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/md5deep
/usr/share/doc/md5deep/copyright
/usr/share/doc/md5deep/changelog.Debian.gz
My output for:
dpkg -L hashdeep
is:
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/hashdeep
/usr/share/doc/hashdeep/README.md.gz
/usr/share/doc/hashdeep/README.Debian
/usr/share/doc/hashdeep/FILEFORMAT
/usr/share/doc/hashdeep/TODO.gz
/usr/share/doc/hashdeep/copyright
/usr/share/doc/hashdeep/NEWS.gz
/usr/share/doc/hashdeep/changelog.Debian.gz
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/hashdeep.1.gz
/usr/bin
/usr/bin/hashdeep
Running off: Ubuntu 16.04.1 LTS
TLDR: This is bug of hashdeep package (since debian); Use hashdeep -c md5 in older ubuntu; fixed in 17.04 (upgrade your ubuntu or try to downgrade package or use backports; or try to recompile into deb newer package or do sudo ln -s /usr/bin/hashdeep /usr/bin/md5deep or sudo ln -s hashdeep /usr/bin/md5deep as hack).
In debian and Ubuntu (some version before 16.04 or in it, actually 15.10) md5deep package was replaced by hashdeep package. Now, in 17.04 "zesty" md5deep is not a real package but just a "link" (transitional dummy package) to hashdeep package:
http://packages.ubuntu.com/zesty/md5deep
transitional dummy package for hashdeep
Most recent version of hashdeep (from 17.04 "zesty") http://packages.ubuntu.com/zesty/hashdeep can be installed by sudo apt-get install hashdeep and has all needed commands:
http://packages.ubuntu.com/zesty/amd64/hashdeep/filelist (only /usr/bin part)
/usr/bin/hashdeep
/usr/bin/md5deep
/usr/bin/sha1deep
/usr/bin/sha256deep
/usr/bin/tigerdeep
/usr/bin/whirlpooldeep
But the problem (bug) is that 16.04 and 16.10 versions of hashdeep lacked 5 additional names in /usr/bin including md5deep:
http://packages.ubuntu.com/xenial/amd64/hashdeep/filelist
http://packages.ubuntu.com/yakkety/amd64/hashdeep/filelist
/usr/bin/hashdeep
This is marked in Changelog of the recent package: http://changelogs.ubuntu.com/changelogs/pool/universe/h/hashdeep/hashdeep_4.4-4/changelog
hashdeep (4.4-3) ... 22 Sep 2016
debian/hashdeep.links:
- Added to enable multi-call for md5deep and others.
(Closes: #795053, LP: #1525217, #1577293)
Bugs listed are:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795053 "hashdeep: Important functions disabled by symlink removal" - 10 Aug 2015 - Found in version hashdeep/4.4-1; Fixed in version hashdeep/4.4-3
https://bugs.launchpad.net/ubuntu/+source/md5deep/+bug/1525217 "md5deep binary is missing" - Ubuntu 15.10 - 2015-12-11 -- 2017-03-29
https://bugs.launchpad.net/ubuntu/+source/hashdeep/+bug/1577293 "binary not available in package" - 16.04 - 2016-05-02 -- 2016-11-03
The program has different options and features when run with the names "hashdeep" and "md5deep"
Related
I am not a linux user, so this might be a basic question.
I am trying to upgrade python version from 3.5 to 3.9 on a chromebook.
The chrome book runs linux penguin (i type uname -a to get the version).
Linux penguin 5.4.67-09356-gf3ed4c0c4a31 #1 SMP PREEMPT Sun Sep 27 20:30:52 PDT 2020 aarch64 GNU/Linux
I have tried the following online method (replacing 3.7 for 3.9) but it fails:
https://dev.to/serhatteker/how-to-upgrade-to-python-3-7-on-ubuntu-18-04-18-10-5hab
https://dev.to/serhatteker/how-to-upgrade-to-python-3-7-on-ubuntu-18-04-18-10-5hab
I have tried other online methods too, but they also fail so i now go back to the basics.
I have also tried this method for miniconda:
https://docs.conda.io/en/latest/miniconda.html
for both the 32 and 64 bit versions of python on linux but get the error message:
Miniconda3-latest-Linux-x86_64.sh: line 414: /opt/miniconda3/conda.exe: cannot execute binary file: Exec format error
In particular i note that the new python version is not in the /usr/bin folder, but the old version is.
I therefore do: sudo apt install python3.9 and see the following:
dlefcoe#penguin:~$ sudo apt install python3.9
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'postgresql-plpython3-9.6' for regex 'python3.9'
postgresql-plpython3-9.6 is already the newest version (9.6.20-0+deb9u1).
0 upgraded, 0 newly installed, 0 to remove and 32 not upgraded.
This looks positive, but when i do python it still goes to the old version.
When i type python3.9 the system returns:
-bash: python3.9: command not found
I presume that version 3.9 is installed somewhere (but where i don't know) or i have not installed it properly.
How can i get this working on the chromebook please ?
The following solution works:
Install dependencies
sudo apt update
sudo apt install build-essential zlib1g-dev libncurses5-dev libgdbm-dev libnss3-dev libssl-dev libreadline-dev libffi-dev libsqlite3-dev wget libbz2-dev
Download latest release
wget https://www.python.org/ftp/python/3.9.0/Python-3.9.0.tgz
extract file
tar -xf Python-3.9.0.tgz
configure script
cd Python-3.9.0
./configure --enable-optimizations
build process
make -j 12
install binaries
sudo make altinstall
And then test the version with python3.9 --version.
The full link is here:
https://linuxize.com/post/how-to-install-python-3-9-on-ubuntu-20-04/
Presumably this will work with later versions too. So 3.9.x.
This is in reference to running the WRF model in my system. I am trying to run the file plotgrids.ncl to ensure that the domain is in the right location before running geogrid.exe . Running the following command in my terminal(ubuntu)
ncl util/plotgrids.ncl
gives me the following error:
ncl: /lib/x86_64-linux-gnu/libssl.so.10: version 'libssl.so.10' not found (required by ncl)
ncl: /lib/x86_64-linux-gnu/libcrypto.so.10: version 'libcrypto.so.10' not found (required by ncl)
at one NCL 6.4.0 installation at Ubuntu 10.10 the solution was
searching a compat-openssl10 package, as
compat-openssl10-1.0.2j-9.fc26.x86_64.rpm
turn it into a .deb package by doing this steps:
apt-get install libdpkg-perl
alien compat-openssl10-1.0.2j-9.fc26.x86_64.rpm
dpkg -i compat-openssl10_1.0.2j-10_amd64.deb
find / -name libssl.so.*
will now show it at /usr/lib/ libssl.so.10
NCL will still complain about GLIBC version
at this case that was solved by editing
vi /etc/apt/sources.list
:%s/maverick/wily/g
apt-get update
apt-get install libc6
this still shows as 2.15 with
ldd --version
however now the test works with
ng4ex xy01n -clean
for Ubuntu 16 please check help given by NCL forum at
mailman.ucar.edu/pipermail/ncl-install/2017-November/thread.html
as resumed here:
http://conda.pydata.org/miniconda.html
used Python 3.6 Linux 64-bit (bash installer)
cd /home/user/Downloads/
chmod +x Miniconda2-latest-Linux-x86_64.sh
./Miniconda2-latest-Linux-x86_64.sh
conda -V
conda 4.3.30
http://ncl.ucar.edu/Download/conda.shtml
conda create -n ncl_stable -c conda-forge ncl=6.4.0 gsl
root#hostname:~# source activate ncl_stable
(ncl_stable) root#hostname:~# ncl -V
6.4.0
ng4ex xy05n -clean -W png
it works!
outside conda (ncl_stable)
ng4ex
The program 'ng4ex' is currently not installed. You can install it by:
sudo su
vi /etc/apt/sources.list
add at the end
deb http://http.us.debian.org/debian/ testing non-free contrib main
exit editor
apt-get update
apt install libncarg-bin
I am using CentOS 7.2.
I would like to install the latest version of rsync - rsync-3.1.2,
rsync-3.0.9 is on system, installed when installing mariadb with yum,
# rpm -qa |grep rsync
rsync-3.0.9-17.el7.x86_64
removing rsync-3.0.9 first,
# yum remove rsync
rsync and mariadb were removed together,
then,
installing rsync-3.1.2 from source code,
# wget https://download.samba.org/pub/rsync/src/rsync-3.1.2.tar.gz
# tar -zxvf rsync-3.1.2.tar.gz
# cd rsync-3.1.2
# ./configure
# make
# make install
then,
installing mariadb with yum again,
but rsync-3.0.9 will still be installed.
How can I solve the problem?
You can install rsync 3.1.2 from the Fedora 24 .rpm package:
wget http://dl.fedoraproject.org/pub/fedora/linux/releases/24/Everything/x86_64/os/Packages/r/rsync-3.1.2-2.fc24.x86_64.rpm
rpm -Uvh rsync-3.1.2-2.fc24.x86_64.rpm
(but that question doesn't really belong to stackoverflow)
You can install rsync 3.1.2 from the gf-plus repo. Just follow the steps below:
Install the gf-release package.
sudo rpm -Uvh http://mirror.ghettoforge.org/distributions/gf/el/7/gf/x86_64/gf-release-7-10.gf.el7.noarch.rpm
Upgrade rsync package from the gf-plus repo.
sudo yum install -y --enablerepo=gf-plus rsync
Check rsync version.
hash -r; rsync --version | awk 'NR==1 {print $3}'
If it prints 3.1.2, rsync is upgraded.
By default, only the gf repo is enabled, which claims that it "won't overwrite core distro packages". You can disable it:
sudo yum-config-manager --disable gf
(For command not found error, run sudo yum install -y yum-utils and try again.)
Or simply remove all the gf* repos by removing the gf-release package:
sudo yum remove -y gf-release
You either need to install all of your software using packages, or install all of your software from source. Trying to mix and match is going to lead to exactly the sort of problem you are experiencing here: the mariadb package has a dependency on rsync, but the package manager doesn't know anything about the files you have installed from source.
The correct way to solve this problem is to build your own rsync package that can then be installed with yum. You can start with the source package for your distribution and then modify it for 3.1.2. You may be able to utilize a more recent package (e.g., from Fedora) and rebuild it for your system.
You can find the source RPM for rsync-3.0.9 here, and there is some documentation that will hopefully help you get started here.
I tried using the following commands. However when I reach the last step to install pdftk the console is giving me the error below. I am using a hostgator VPS server. any possible suggestions would be great.
NB: I tried installing libgcj.so.7rh()(64bit) but it already exists. maybe I am doing something wrong.
**Error:** Package: pdftk-1.44-2.el5.rf.x86_64 (rpmforge)
Requires: libgcj.so.7rh()(64bit)
You could try using --skip-broken to work around the problem
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
sendmail-cf-8.14.4-8.el6.noarch has missing requires of sendmail = ('0', '8.14.4', '8.el6')
These are the steps that I followed.
# Log in as root
cd /usr/local/src
# Type
uname -i
#To see which package you need
#Pick one of the below vdepending on the output of uname -i
i386<br>
wegt packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.i386.rpm
x86_64 <br>
wget packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm
#Then type
rpm --import apt.sw.be/RPM-GPG-KEY.dag.txt
Verify the downloaded package
rpm -K rpmforge-release-0.5.2-2.el5.rf.*.rpm
#Install RPM
rpm -i rpmforge-release-0.5.2-2.el5.rf.*.rpm
#Then
yum install pdftk
Note: I had to remove the http:// from the links in the commands above before posting.
It seems like you might have a 32-bit OS installed? If you ran through each of those commands in order, you would be trying to use the 64-bit rpmforge repository, which is incorrect for a 32-bit OS.
If that is an accurate supposition, do this..
cd /etc/yum.repos.d/
ls -al
rm <each-rpmforge-file>
Then...
cd /usr/local/src
yum clean
wget packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.i386.rpm
rpm -i rpmforge-release-0.5.2-2.el5.rf.*.rpm
yum update
yum install pdftk
I'm running Debian 7.2 on Google Compute Engine (Though I suspect Centos, Red Hat, and Amazon Linux AMI all have the same problem). After downloading the 64-bit Linux version of the Dart SDK from this page, any dart command I run, for example, dart --version, will output the following error:
./editor/dart/dart-sdk/bin/dart: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by ./editor/dart/dart-sdk/bin/dart)
./editor/dart/dart-sdk/bin/dart: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./editor/dart/dart-sdk/bin/dart)
Update: October 2014: Dart can now be installed on Debian with apt-get:
Instructions summarized from the dart website:
# Enable HTTPS for apt.
sudo apt-get update
sudo apt-get install apt-transport-https
# Get the Google Linux package signing key.
sudo sh -c 'curl https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -'
# Set up the location of the stable repository.
sudo sh -c 'curl https://storage.googleapis.com/download.dartlang.org/linux/debian/dart_stable.list > /etc/apt/sources.list.d/dart_stable.list'
sudo apt-get update
# Finally, install the dart package!
sudo apt-get install dart
Instructions for building the binary yourself:
This problem appears to be caused by Google compiling against an edge version of GLIBC (>= 2.15) which is not generally supported on Linux outside of Ubuntu 12 (Precise Pangolin).
First of all, do not attempt to download an experimental version of GLIBC or EGLIBC. I was able to get dart to work using that method, but the rest of my machine fell apart. Updating GLIBC is a recipe for madness.
Instead, the best solution is building dart from source. Despite the GLIBC version requirements of the binary, the source itself has no such requirements. There are wiki pages for installing from source on debian, centos/fedora/red hat/amazon, ubuntu, and other linux versions.
Here is an overview of those steps, which I can confirm works on Debian 7.2. The centos/fedora/redhat steps appear to be the same except they use yum instead of apt-get.
Install subversion and the required build tools:
sudo apt-get -y update
sudo apt-get -y install subversion
sudo apt-get -y install make
sudo apt-get -y install g++
sudo apt-get -y install openjdk-6-jdk
Check out google's depot tools and add gclient to your path
svn co http://src.chromium.org/svn/trunk/tools/depot_tools
export PATH=$PATH:`pwd`/depot_tools
Download the dart source at the desired branch.
Replace 1.2 with whatever branch you wish to build. You can see a list of available versions here. In general, the latest numbered branch is best.
gclient config http://dart.googlecode.com/svn/branches/1.2/deps/all.deps
gclient sync
gclient runhooks
Move into the new dart directory
cd dart
Do only A or B below:
Note: For 32bit, use the --arch=ia32 flag instead.
A. Build the entire Dart SDK including pub, dart2js, dart, etc.:
tools/build.py --mode=release --arch=x64 create_sdk
B. Build just the dart executable:
tools/build.py --mode=release --arch=x64 runtime
The dart executable is now at either out/ReleaseX64/dart or out/ReleaseX64/dart-sdk/bin/dart you can do a smoke test by printing the version
dart/out/ReleaseX64/dart --version
The output should be something like Dart VM version: 1.2.0 (Mon Mar 3 03:06:20 2014) on "linux_x64".
How to help fix this issue
This was much more painful than it needed to be, since the binary clearly doesn't need to be built using GLIBC >= 2.15. If you wish to draw attention to this issue, please star this dart bug.