libtool failed to emerge because the bash version at /bin/bash did not support the '=~' operator if ! hasq "${EAPI:-0}" 0 1 && \ [[ $x =~ (.*)\.([a-z][a-z](_[A-Z][A-Z])?)\.(.*) ]] ; then name=${BASH_REMATCH[1]##*/}.${BASH_REMATCH[4]} Reproducible: Always Steps to Reproduce: 1. /bin/bash has to be a version which does not support '=~' and portage has to be a sufficient version as to assume '=~' is supported 2. emerge libtool (or possibly any other package that runs 'doman') Actual Results: Towards the end of the emerge, portage spat out: /home/project-pool/graphics/fluids/environment/usr/lib/portage/bin/doman: line 35: unexpected argument `(' to conditional binary operator /home/project-pool/graphics/fluids/environment/usr/lib/portage/bin/doman: line 35: syntax error near `(.' /home/project-pool/graphics/fluids/environment/usr/lib/portage/bin/doman: line 35: ` [[ $x =~ (.*)\.([a-z][a-z](_[A-Z][A-Z])?)\.(.*) ]] ; then' Expected Results: Sucessful emerge
What version of portage are you running? Portage 2.2.00.10760-prefix appears to have this fixed already. I vaguely recall having this fixed before. But maybe the older version in the bootstrap tarball still has the problem? In what stage do you hit this problem?
(In reply to comment #1) > What version of portage are you running? Portage 2.2.00.10760-prefix appears > to have this fixed already. I vaguely recall having this fixed before. But > maybe the older version in the bootstrap tarball still has the problem? In > what stage do you hit this problem? > I appear to be running 2.2.00.10625-prefix so that could be the issue. Higher versions do not seem to be in the prefix tree I have at the moment (which was generated via 'bootstrap-prefix.sh $EPREFIX tree'), but it could turn up when I later do 'emerge --sync'. When the machine gets around to the 'emerge --sync' part of the bootstrap process I'll check again for the portage versions > 10625 and whether or not this issue is fixed. Does that help at all?
I can confirm that doing an 'emerge --sync' gives an update to portage which seems to fix the problem. The issue seems to be only with the bootstrap tarball.
ok, so the tarball clearly needs updating.
tarball updated, bug should be resolved now.
