--- portage-2.0.51.22/bin/ebuild.sh 2005-05-15 12:20:58.000000000 +0200 +++ /usr/lib/portage/bin/ebuild.sh 2005-05-19 12:13:56.000000000 +0200 @@ -1075,7 +1075,7 @@ local count=0 find "${D}/" -user portage | while read file; do count=$(( $count + 1 )) - s=$(stat_perms $file) + s=$(stat_perms "$file") chown root "$file" chmod "$s" "$file" done Also stat_perms has a nice 'die' in it, which triggered when i had the error, but its called in a subshell and portage continued on its merry way
i had the quote bug fixed locally, but i'll leave the 'die in a subshell' issue to someone else ;p
Brian, I do believe this is your handiwork. ;)
adding those quotes shouldn't have to take THREE weeks right?
if you wish to be a jackass, do it somewhere else no it didnt take THREE weeks, more like THREE days (or less)
Fixed on or before 2.0.51.22-r1
Looking through the batch of bugs, I'm not sure that some of these are actually fixed in stable. Others, the requirements have possibly changed after the initial fix was committed. If you think this bug has been closed incorrectly, please reopen or ask that it be reopened.
Its back Index: ebuild.sh =================================================================== --- ebuild.sh (revision 2130) +++ ebuild.sh (working copy) @@ -1150,7 +1150,7 @@ if [ -L "${file}" ]; then lchown ${PORTAGE_INST_UID} "${file}" else - s=$(stat_perms $file) + s=$(stat_perms "$file") if [ -z "${s}" ]; then ewarn "failed stat_perm'ing $file. User intervention during install isn't wise..." continue @@ -1166,7 +1166,7 @@ count=0 find "${D}/" -group portage | while read file; do count=$(( $count + 1 )) - if [ -L ${file} ]; then + if [ -L "${file}" ]; then lchgrp ${PORTAGE_INST_GID} "${file}" else s=$(stat_perms "$file")
Released in 2.0.53_rc6
Forgot to mark it..
