The ghostscript-esp ebuild is broken because it attempts to use a non-existent patch file called ghostscript-7.05.6.man.patch, but the patch file is named ghostscript-esp-7.05.6.man.patch. This can prevent many things from building due to their dependence on ghostscript (such as samba and then consequentially many packages if 'samba' is USE'd). This is broken in the "stable" ghostscript-esp-7.07.1-r8 ebuild. I rsync'd on 2006-Jan-04.
I'm seeing this as well. Instead of ghostscript-7.05.6.man.patch, there's now a ghostscript-esp-7.05.6.man.patch in the files directory. Should this patch file be used instead? I synced about 2 hours ago.
(In reply to comment #1) > I'm seeing this as well. Instead of ghostscript-7.05.6.man.patch, there's now a > ghostscript-esp-7.05.6.man.patch in the files directory. > > Should this patch file be used instead? > > I synced about 2 hours ago. > Yes, I forgot to mention that I symlinked the patch file, did a digest, and was able to merge ghostscript-esp.
Created attachment 76215 [details, diff] Patch against 7.07.1-r10 ebuild, making it use esp files This patch makes the ebuild use patches named "esp", to reflect the renaming of the actual patchfiles in the "files" directory.
I renamed the patches in CVS, thanks. It will be available through rsync in an hour
*** Bug 117901 has been marked as a duplicate of this bug. ***
*** Bug 117934 has been marked as a duplicate of this bug. ***