| Summary: | Emerging gentoolkit-dev fails | ||
|---|---|---|---|
| Product: | Gentoo/Alt | Reporter: | Rabbe Fogelholm <rabbe> |
| Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Rabbe Fogelholm
2010-11-04 07:32:52 UTC
does upgrading portage still work? I think this is actually a bug in portage that was resolved already I tried to do `emerge --sync' followed by `emerge gentoolkit-dev' and `emerge portage' in a Prefix tree that was bootstrapped on November 5. Emerging gentoolkit-dev succeeded (version number 0.2.7 unchanged). Upgrading portage (from 2.2.01.17133 to 2.2.01.17168) failed with * ERROR: sys-apps/portage-2.2.01.17168 failed: * Aborting due to QA concerns: invalid shebangs found * * Call stack: * misc-functions.sh, line 1692: Called install_qa_check * misc-functions.sh, line 210: Called install_qa_check_prefix * misc-functions.sh, line 855: Called die * The specific snippet of code: * die "Aborting due to QA concerns: invalid shebangs found" * * If you need support, post the output of 'emerge --info =sys-apps/portage-2.2. 01.17168', * the complete build log and the output of 'emerge -pqv =sys-apps/portage-2.2.0 1.17168'. * The complete build log is located at '/local/scratch/portage/sys-apps/portage -2.2.01.17168/temp/build.log'. * The ebuild environment file is located at '/local/scratch/portage/sys-apps/po rtage-2.2.01.17168/temp/environment'. * S: '/local/scratch/portage/sys-apps/portage-2.2.01.17168/work/prefix-portage- 2.2.01.17168' !!! post install failed; exiting. can't reporduce with same portage version, you'll need to provide more output No longer a problem; gentoolkit-dev emerges fine today. Versions are: gentoolkit-dev: 0.2.8 portage: 2.2.01.17168 |