Bug 28067

Summary:	emerge portage fails on grep: Invalid regular expression
Product:	Portage Development	Reporter:	John Bartoszewski <johnb>
Component:	Unclassified	Assignee:	Portage team <dev-portage>
Status:	RESOLVED INVALID
Severity:	major
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description John Bartoszewski 2003-09-06 11:52:14 UTC

I emerge rsynced and it recommened portage upgrade.
emerge portage worked well until:

...
--- !targe sym /usr/bin/emerge
>>> original instance of package unmerged safely.

 * NOTICE: PLEASE *REPLACE* your make.globals. All user changes to variables
 * in make.globals should be placed in make.conf. DO NOT MODIFY make.globals.

 * Feature additions are noted in help and make.conf descriptions. Update
 * them using 'etc-update' please. Maintaining current configs for portage
 * and other system packages is fairly important for the continued health
 * of your system.

Recalculating the counter... Counter updated successfully.
>>> Clearing invalid entries in dependancy cache...grep: Invalid regular expression
wc: write error: Broken pipe
wc: write error: Broken pipe
wc: write error: Broken pipe
... (infinate wc errors)

Comment 1 John Bartoszewski 2003-09-06 12:39:56 UTC

Found problem
I had left in make.conf 
ACCEPT_KEYWORDS="~arch ~x86"
when I changed it to:
ACCEPT_KEYWORDS="~x86"
emerge portage finished.
A typo in ACCEPT_KEYWORDS should not cause an infinate loop

Comment 2 Nicholas Jones (RETIRED) gentoo-dev

2003-09-14 20:40:05 UTC

It's not infinate, but it is an aweful lot.
~arch is warned about in new portages.