The directory in tarball is extracted with d--------- rights, so the build fails. Reproducible: Always Steps to Reproduce: The required change is: --- /root/poster-0.1.ebuild.oryginal 2005-09-09 06:19:18.000000000 +0200 +++ poster-0.1.ebuild 2005-09-09 06:19:43.000000000 +0200 @@ -16,6 +16,7 @@ src_unpack() { unpack ${A} + chmod u+rwx ./poster cd ${S} tar -zxf ./poster.tar.gz || die "tar failed" }
It installed fine for me. Maybe the tarball was updated? Try removing it from $DISTDIR and re-emerging?
Wouldn't it fail on md5 check if the tarball was changed? hq distfiles # md5sum poster.tgz cbd9368cf632bc56e1a7d5c80a82c659 poster.tgz hq distfiles # tar -tzvf poster.tgz d--------- root/other 0 2000-09-14 11:07:44 poster/ -rw-r--r-- root/other 21547 1995-09-27 17:02:47 poster/poster.tar.gz -rw-r--r-- root/other 2414 1995-09-20 11:41:40 poster/getopt.c -rw-r--r-- root/other 3783 1995-09-21 09:52:35 poster/README -rw-r--r-- root/other 38128 1995-09-28 15:16:34 poster/poster.exe
Not if you haven't sync'd since they updated it.
In this case oryginal tarball is really old (~1999?). Can you check md5sum on your tgz and check the contents?
I have exactly the same issue with the ebuild as Marcin Gryszkalis. I resynced the portage and deleted the file from the distfiles, but the problem still stays.
The patch I posted in comment is working (steve - maybe you could test it and confirm) - couldn't someone commit it?
I can confirm that I see the same thing on my notebook (as of Oct 30, synced today).
You see this problem only if you have the userpriv feature selected
Disabling userpriv helps :)
*** Bug 117870 has been marked as a duplicate of this bug. ***
thanks, I added the chmod to the ebuild