md5deep binary is missing

Bug #1525217 reported by Andrey de Oliveira on 2015-12-11
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
md5deep (Ubuntu)
Undecided
Unassigned

Bug Description

md5deep binary is missing in lastest stable packages in stable release.

Downgrade to md5deep_4.2-1 works fine.

# lsb_release -rd
Description: Ubuntu 15.10
Release: 15.10

#dpkg -S md5deep
md5deep: /usr/share/doc/md5deep/copyright
md5deep: /usr/share/doc/md5deep/changelog.Debian.gz
md5deep: /usr/share/doc/md5deep

# dpkg -l md5deep hashdeep
(...)
ii hashdeep 4.4-2 amd64 recursively compute hashsums or piecewise hashings
ii md5deep 4.4-2 all transitional dummy package for hashdeep

affects: hashdeep (Ubuntu) → md5deep (Ubuntu)
Hans Joachim Desserud (hjd) wrote :

Thanks for reporting this issue.

As dpkg mentioned, md5deep is now a transitional dummy package for hashdeep.

From what I can see, it looks like md5deep has been renamed to (and replaced by) hashdeep. For this reason the package was removed from Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804855) and in turn, Ubuntu (https://launchpad.net/ubuntu/+source/md5deep/+publishinghistory).

So this looks like this is intential, and that hashdeep should be possible to use instead.

Changed in md5deep (Ubuntu):
status: New → Incomplete
Andrey de Oliveira (crazy2010) wrote :

Thanks for reading and responding. I believe the purpose of hashdeep and md5deep are different.

The md5deep intends to be a md5sum fork with more features:

"(...) Md5deep is similar to the md5sum program found in the GNU Coreutils package, but has the Following additional features:" - http://md5deep.sourceforge.net/

Anyway, reading your answer and searching a bit more, I found that the latest version of hashdeep has different behavior depending on how it is called:

"For historical Reasons, the program has different options and features When run with the names" hashdeep "and" md5deep "" -https:. //github.com/jessek/hashdeep#md5deep-vs-hashdeep

Simply create a symlink called md5deep pointing to hashdeep and they work differently solving the problem.

I think this is missing and should be done in the installation of hashdeep package.

I have fixed the missing md5deep and made my script run okay.
sudo ln -s /usr/bin/hashdeep /usr/local/bin/md5deep
That is all I did to get both hashdeep and md5deep functional. They use the same binary code and work differently (a wee bit anyway) depending on being called by md5deep or hashdeep.
I'm using Linux Mint 18.1 derived from Ubuntu 16.10.
What is still not working is "info md5deep" but it is okay for "info hashdeep".

It all needs to be looked at in Ubuntu.

In Debian 18.1 and Mint LMDE 2 Betsy they were both okay after installation. Regards Ian.

The attachment "It is only a simple link" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Andrey de Oliveira (crazy2010) wrote :

This bug was fixed in the package hashdeep - 4.4-4

---------------
hashdeep (4.4-4) unstable; urgency=medium

  * debian/watch:
      - Leaving only a repository to avoid conflicting on uscan system.

 -- Giovani Augusto Ferreira <email address hidden> Thu, 13 Oct 2016 23:59:14 -0300

From hashdeep bug #1577293
https://bugs.launchpad.net/ubuntu/+source/hashdeep/+bug/1577293

Rik Mills (rikmills) on 2017-04-03
Changed in md5deep (Ubuntu):
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.