Suddenly, portage as stopped (don't remember exactly when this happened and in whic context). It download an unpack nicely, apply patches, then just stop quietly after ">>> Source unpacked" line (command result (echo $?) is 1, but I ad no message). After running an "emerge -d portage" I finally found which line was provoquing the shell script error: there are 2 'export PWORKDIR="$WORKDIR"' lines in /usr/lib/portage/bin/ebuild.sh I've replaced them with 'export PWORKDIR="${WORKDIR}"' and bingo! I can use my gentoo again. Reproducible: Always Steps to Reproduce: 1.emerge portage 2. 3. Actual Results: stops after ">>> Source unpacked" here is the patch: --------------- cut here ----------------------------------------- --- ebuild.sh 2007-03-10 11:19:31.000000000 +0100 +++ ebuild.sh~ 2007-03-10 11:18:42.000000000 +0100 @@ -966,7 +966,7 @@ export S D #some packages use an alternative to $S to build in, cause #our libtool to create problematic .la files - export PWORKDIR="${WORKDIR}" + export PWORKDIR="$WORKDIR" vecho ">>> Compiling source in ${srcdir} ..." qa_call src_compile vecho ">>> Source compiled." @@ -1056,7 +1056,7 @@ export S D #some packages uses an alternative to $S to build in, cause #our libtool to create problematic .la files - export PWORKDIR="${WORKDIR}" + export PWORKDIR="$WORKDIR" qa_call src_install touch "${PORTAGE_BUILDDIR}/.installed" vecho ">>> Completed installing ${PF} into ${D}" ----------------------------------------------------
That makes no sense. That change shouldn't have any effect on anything. Both ways are proper syntax.
(In reply to comment #1) > That makes no sense. That change shouldn't have any effect on anything. Both > ways are proper syntax. > I'm sorry about this response... It may make no sense, however, my system used to be useless before I did this simple correction, and now it works fine. Take it the way you want, that's a fact on my system (amd64 BTW). I don't know if this actually comes from a bug from bash, or another strange side effect caveat, but things happened the way I told (in a very poor english with many typos and missing words, I must admit. Sorry about that). This kind of reaction does not encourage me to try to help... Yours, Davis
And if you revert that change it breaks again? It's just *very* hard to believe that this change has any effect.
Something wrong with bash?
