Comment 2 for bug 1525217

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.