When I do an emerge -puv --deep world I get the following output: These are the packages that I would merge, in order: Calculating world dependencies -/usr/sbin/ebuild.sh: /usr/portage/media-libs/fontconfig/fontconfig-2.2.1.ebuild: line 108: unexpected EOF while looking for matching ``' /usr/sbin/ebuild.sh: /usr/portage/media-libs/fontconfig/fontconfig-2.2.1.ebuild: line 109: syntax error: unexpected end of file !!! ERROR: media-libs/fontconfig-2.2.1 failed. !!! Function , Line 1290, Exitcode 1 !!! error sourcing ebuild aux_get(): (0) Error in media-libs/fontconfig-2.2.1 ebuild. (1) Check for syntax error or corruption in the ebuild. (--debug) !!! all ebuilds that could satisfy ">=media-libs/fontconfig-2.1-r1" have been masked. !!! (dependency required by "x11-base/xfree-4.3.0-r3" [ebuild]) !!! Problem with ebuild media-sound/xmms-1.2.8-r3 !!! Possibly a DEPEND/*DEPEND problem. !!! Depgraph creation failed. Reproducible: Always Steps to Reproduce: 1. emerge -puv --deep world Actual Results: The error. Expected Results: Shown me what needs to be installed to update my system. It looks like their is a"^L`" at the end of the file that is causing the prolem. Here is line 108: ^L` I am going to submit the ebuild without that character at the end.
Created attachment 24254 [details] The correct ebuild This should fix the problem
This looks invalid to me. There is no ^L` in the ebuild in portage. Try resyncing and trying it again. Could be local file corruption on your end or a bad mirror.
yeah, there was a rsync freak out recently ... just delete the file and sync up again and you should be fine
*** Bug 40305 has been marked as a duplicate of this bug. ***
Created attachment 25420 [details] This is a working ebuild, the last one submited has a typo. The other uploaded ebuild file contains this line: # Remove the subpixel test from local.conf (#12757) epatch ${PPREFIX}-2.2-rove_subpixel_test.patch It should look like this: # Remove the subpixel test from local.conf (#12757) epatch ${PPREFIX}-2.2-remove_subpixel_test.patch And however, rsync.no.gento.org still has the old file, the one with bad ending. Just like bug #40305 says.
