The ebuild moves all recipes to /usr/share/doc/magicrescue-1.1.10-r2/recipes /usr/share/doc/magicrescue-1.1.10-r2/recipes/avi.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/canon-cr2.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/elf.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/empathy.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/flac.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/flv.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/gimp-xcf.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/gpl.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/gzip.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/jpeg-exif.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/jpeg-jfif.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/mbox-mozilla-inbox.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/mbox-mozilla-sent.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/mbox.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/mp3-id3v1.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/mp3-id3v2.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/msoffice.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/nikon-raw.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/perl.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/png.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/ppm.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/rar.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/sqlite.bz2 /usr/share/doc/magicrescue-1.1.10-r2/recipes/zip.bz2 But the man page explains where they are expected: --8<------------------------------------------------------------- -r recipe Mandatory. Recipe name, file, or directory. Specify this as either a plain name (e.g. "jpeg-jfif") or a path (e.g. recipes/jpeg-jfif). If it doesn't find such a file in the current directory, it will look in ./recipes and PREFIX/share/magicrescue/recipes, where PREFIX is the path you installed to, e.g. /usr/local. If recipe is a directory, all files in that directory will be treated as recipes. Browse the PREFIX/share/magicrescue/recipes directory to see what recipes are available. A recipe is a text file, and you should read the comments inside it before using it. Either use the recipe as it is or copy it somewhere and modify it. For information on creating your own recipes, see the "RECIPES" section.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=000ecf84a67fc8a38b223e471246f8f341a0954f commit 000ecf84a67fc8a38b223e471246f8f341a0954f Author: Sam James <sam@gentoo.org> AuthorDate: 2022-10-05 15:48:35 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-10-05 15:48:35 +0000 app-forensics/magicrescue: fix recipes path Closes: https://bugs.gentoo.org/875383 Signed-off-by: Sam James <sam@gentoo.org> .../{magicrescue-1.1.10-r2.ebuild => magicrescue-1.1.10-r3.ebuild} | 1 - 1 file changed, 1 deletion(-)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2325b51c13b971cb6ac9de1702f8a1ece03ceb54 commit 2325b51c13b971cb6ac9de1702f8a1ece03ceb54 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-10-05 15:52:31 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-10-05 15:52:43 +0000 app-forensics/magicrescue: use upstream path fixes In 000ecf84a67fc8a38b223e471246f8f341a0954f, we drop the docdir sed for recipes to get a quick fix so things start working again, but let's import the upstream commit for using FHS paths in a new revision to ~arch (as opposed to the new revision straight-to-stable earlier to get things working ASAP) adn drop one of our own patches moving some internal tools into /usr/bin as well. Closes: https://bugs.gentoo.org/875383 Signed-off-by: Sam James <sam@gentoo.org> .../files/magicrescue-1.1.10-fhs-paths.patch | 67 ++++++++++++++++++++++ .../magicrescue/magicrescue-1.1.10-r4.ebuild | 33 +++++++++++ 2 files changed, 100 insertions(+)
