| Summary: | emerge sync prints the ACCEPTED_KEYWORDS when updating the portage cache? | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | jochen <jochen.eisinger> |
| Component: | [OLD] Core system | Assignee: | Mr. Bones. (RETIRED) <mr_bones_> |
| Status: | RESOLVED INVALID | ||
| Severity: | trivial | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
qa issue in ebuilds, me thinks You're going to have to track this down closer to the problem area. I can't reproduce this issue here and the only place ~x86 appears in the portage tree are in KEYWORDS and one comment. Try this as root: grep -r --exclude "*xml" ~x86 /etc hum, obviously my fault. after disabling portage overlay i don't get this ~x86 output anymore... probably i should do more qa on my own ebuilds :/ i get those and more on without my own ebuilds. what's qa? |
Since a few days, emerge sync will print my ACCEPTED_KEYWORDS (I guess) just at the end of updating the portage cache: >>> Updating Portage cache... \~x86 ...done! I'm quite sure this "~x86" isn't there on purpose... maybe some typo or something? Reproducible: Always Steps to Reproduce: 1. 2. 3.