When emerging fortune-mod-1.0.9708-r1 I get errors about a failed patch. Reproducible: Always Steps to Reproduce: 1. emerge sync 2. emerge -uD fortune-mod 3. Actual Results: bash-2.05b# emerge -uD fortune-mod Calculating dependencies ...done! >>> emerge (1 of 1) games-misc/fortune-mod-1.0.9708-r1 to / >>> md5 src_uri ;-) fortune-mod-9708.tar.gz * By default the fortune ebuild does not include 'offensive' fortunes. * If you wish to enable this functionality, you must manually edit the * ebuild. The comments inside are self explainatory. >>> Unpacking source... >>> Unpacking fortune-mod-9708.tar.gz to /var/tmp/portage/fortune-mod-1.0.9708-r1/work /usr/sbin/ebuild.sh: line 29: cd: /var/tmp/portage/fortune-mod-1.0.9708-r1/work/fortune-mod-1.0.9708: No such file or directory * Applying 9708-Makefile.patch... * Failed Patch: 9708-Makefile.patch! * * Include in your bugreport the contents of: * * /var/tmp/portage/fortune-mod-1.0.9708-r1/temp/9708-Makefile.patch-8110.out !!! ERROR: games-misc/fortune-mod-1.0.9708-r1 failed. !!! Function epatch, Line 322, Exitcode 0 !!! Failed Patch: 9708-Makefile.patch! Expected Results: Sucessful emerge of fortune-mod Looks like it's a naming issue, since emerge -uDp world shows "[ebuild UD] games-misc/fortune-mod-1.0.9708-r1 [9708-r1]" /var/tmp/portage/fortune-mod-1.0.9708-r1/temp/9708-Makefile.patch-8274.out: ***** 9708-Makefile.patch ***** =============================== PATCH COMMAND: patch -p0 -g0 < /usr/portage/games-misc/fortune-mod/files/9708-Makefile.patch =============================== can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.orig 2003-06-28 01:37:38.000000000 -0400 |+++ Makefile 2003-06-28 01:39:44.000000000 -0400 -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored =============================== PATCH COMMAND: patch -p1 -g0 < /usr/portage/games-misc/fortune-mod/files/9708-Makefile.patch =============================== missing header for unified diff at line 3 of patch can't find file to patch at input line 3Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.orig 2003-06-28 01:37:38.000000000 -0400 |+++ Makefile 2003-06-28 01:39:44.000000000 -0400 -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored =============================== PATCH COMMAND: patch -p2 -g0 < /usr/portage/games-misc/fortune-mod/files/9708-Makefile.patch =============================== missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.orig 2003-06-28 01:37:38.000000000 -0400 |+++ Makefile 2003-06-28 01:39:44.000000000 -0400 -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored =============================== PATCH COMMAND: patch -p3 -g0 < /usr/portage/games-misc/fortune-mod/files/9708-Makefile.patch =============================== missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.orig 2003-06-28 01:37:38.000000000 -0400 |+++ Makefile 2003-06-28 01:39:44.000000000 -0400 -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored =============================== PATCH COMMAND: patch -p4 -g0 < /usr/portage/games-misc/fortune-mod/files/9708-Makefile.patch =============================== missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.orig 2003-06-28 01:37:38.000000000 -0400 |+++ Makefile 2003-06-28 01:39:44.000000000 -0400 -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored
This has been fixed in portage. Please resync and try it again.
