There is a typo in the latest ebuild of screen (3.9.13-r4), there is a '}' missing at the end of the file resulting in an error. Adding the character resolves the problem Reproducible: Always Steps to Reproduce: 1. emerge screen 2. 3. Actual Results: herman root # emerge screen Calculating dependencies ...done! >>> emerge (1 of 1) app-misc/screen-3.9.13-r4 to / /usr/sbin/ebuild.sh: /usr/portage/app-misc/screen/screen-3.9.13-r4.ebuild: line 104: syntax error: unexpected end of file !!! ERROR: app-misc/screen-3.9.13-r4 failed. !!! Function , Line 984, Exitcode 1 !!! error sourcing ebuild Expected Results: a normal emerge of screen.
what mirror are you rsycing with ? could you rsync again and see if the file is still bj0rked ? the ebuild is fine ... here is the cvs copy ... http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo-x86/app-misc/screen/screen-3.9.13-r4.ebuild?rev=1.2&content-type=text/vnd.viewcvs-markup
*** Bug 15506 has been marked as a duplicate of this bug. ***
I use rsync://ftp.snt.utwente.nl/gentoo-portage I did not think of searching for the error there :) Shall I warn the maintainer of that server or not?
yes, it's the rsync mirror who has a bad ebuild file
no, do not talk to the maintainer, we will have one of our dev's handle it :)
I allready sent a message to ftpcom@snt.utwente.nl They did not respond yet but that's not very strange since 90% of the people in Holland are enjoying their evening now. The others have a boring evening ;)
To start with the important stuff: The corrupt file has been removed.-------------------------------------Newer info:the problem is back. so i downloaded the file myself from rsync2.de.gentoo.org, the server we use for mirroring and it seems they are the cause of this problem.-------------------------------------I have experienced this same problem myself once. It was exactly the same bug. The } on the last line was missing from an ebuild. I find it rather strange. If a file is not completely downloaded or something, shouldn't it be deleted by rsync instead of being written? crash of rsync process ???Any thoughts what might cause this and how to prevent it in the future?and now we are on the topic of mirrors. WE ARE STILL WAITING TO BE ADDED TO rsync.gentoo.org.It has been 3 weeks now since we requested this.
The problem with rsync2.de.gentoo.org still exists. i made a seperate bug report of it as well. http://bugs.gentoo.org/show_bug.cgi?id=15733
received an email from Derk-Jan stating the problem was fixed. Also was able to d/l the file successfully myself. I sent DJ the instructions for accessing our private distfile mirror, so hopefully that should resolve this problem permanently. closing bug.
