While building portage in stages, QA errors occuring with save-ebuild-env.sh. This doesn't happen with portage reinstalling under daily use BOX. Reproducible: Always Steps to Reproduce: 1. build stages 2. notice a QA error with portage reinstalled 3. Actual Results: /var/tmp/portage/._portage_reinstall_.ut3hqv/bin/save-ebuild-env.sh: line 86: compgen: command not found /var/tmp/portage/._portage_reinstall_.ut3hqv/bin/save-ebuild-env.sh: line 86: compgen: command not found * QA Notice: command not found: * * /var/tmp/portage/._portage_reinstall_.ut3hqv/bin/save-ebuild-env.sh: line 86: compgen: command not found * /var/tmp/portage/._portage_reinstall_.ut3hqv/bin/save-ebuild-env.sh: line 86: compgen: command not found * /var/tmp/portage/._portage_reinstall_.ut3hqv/bin/save-ebuild-env.sh: line 86: compgen: command not found * /var/tmp/portage/._portage_reinstall_.ut3hqv/bin/save-ebuild-env.sh: line 86: compgen: command not found * /var/tmp/portage/._portage_reinstall_.ut3hqv/bin/save-ebuild-env.sh: line 86: compgen: command not found * /var/tmp/portage/._portage_reinstall_.ut3hqv/bin/save-ebuild-env.sh: line 86: compgen: command not found * /var/tmp/portage/._portage_reinstall_.ut3hqv/bin/save-ebuild-env.sh: line 86: compgen: command not found * /var/tmp/portage/._portage_reinstall_.ut3hqv/bin/save-ebuild-env.sh: line 86: compgen: command not found
bash-4.2_p37
post the full build log as an attachment and `emerge --info`. this should be in every bug report as documented.
this happens during stage building, only warnings, so no logs recorded.
(In reply to comment #3) > this happens during stage building, only warnings, so no logs recorded. There are logs. If you can't get them I can, but I need more specific information on when you get these messages. Is it stage2? stage3? Near the start, near the end?
maybe your builds wrongly disable USE=readline when building bash
Portage now uses compgen. I suggest that: 1. sys-apps/portage depend on ">=app-shells/bash-3.2_p17[readline]". 2. gentoo-x86/profiles/base/package.use.force contain "app-shells/bash readline" entry.
building bash with readline flag in stage1 fixing this issue.
(In reply to comment #6) > Portage now uses compgen. I suggest that: > 1. sys-apps/portage depend on ">=app-shells/bash-3.2_p17[readline]". > 2. gentoo-x86/profiles/base/package.use.force contain "app-shells/bash > readline" entry. Thanks, this is fixed in cvs now.
(In reply to comment #6) > Portage now uses compgen. I suggest that: > 1. sys-apps/portage depend on ">=app-shells/bash-3.2_p17[readline]". > 2. gentoo-x86/profiles/base/package.use.force contain "app-shells/bash > readline" entry. This is not valid for all the older versions of bash in portage, as they do not have a readline USE, and explicitly force it off: (from <=app-shels/bash-4.1_p11) # Always use the buildin readline, else if we update readline # bash gets borked as readline is usually not binary compadible # between minor versions. #myconf="${myconf} $(use_with !readline installed-readline)" myconf="${myconf} --without-installed-readline" I have not upgraded to bash-4.2 as it used to be broken in how it expanded variables during path tab completion. So, this essentially tries to force an upgrade to bash-4.2, during an emerge -uD and produces confusing output if those guys are masked...
(In reply to comment #9) > (In reply to comment #6) > > Portage now uses compgen. I suggest that: > > 1. sys-apps/portage depend on ">=app-shells/bash-3.2_p17[readline]". > > 2. gentoo-x86/profiles/base/package.use.force contain "app-shells/bash > > readline" entry. > > This is not valid for all the older versions of bash in portage, as they > do not have a readline USE, and explicitly force it off: > (from <=app-shels/bash-4.1_p11) > # Always use the buildin readline, else if we update readline > # bash gets borked as readline is usually not binary compadible > # between minor versions. > #myconf="${myconf} $(use_with !readline installed-readline)" > myconf="${myconf} --without-installed-readline" > > I have not upgraded to bash-4.2 as it used to be broken in how it > expanded variables during path tab completion. > > So, this essentially tries to force an upgrade to bash-4.2, during an > emerge -uD and produces confusing output if those guys are masked... Okay, I've updated the dependency to allow for older bash as follows: || ( >=app-shells/bash-4.2_p37[readline] ( <app-shells/bash-4.2_p37 >=app-shells/bash-3.2_p17 ) ) It would better be expressed as >=app-shells/bash-3.2_p17[readline(+)], but that would require EAPI 4, and I don't want to use that in the portage ebuilds yet.
