Summary: | ebuild emerge fails but portage reports that it succeded | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Kevyn Shortell (RETIRED) <trance> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | seemant, vapier |
Priority: | Highest | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kevyn Shortell (RETIRED)
![]() Forgot portage rev: 2.0.48-r5 w/out more information (like an log of the original emerge) this bug really cant be tracked ... who is to say that the ebuild isnt at fault ? If you need more info, please let me know specifically what you want, and I'll recreate it, since I've been able to recreate it numerous times. This is a bug in portage. I recommend not control-C'ingout... as that is fairly hazardous to system-health in general. Half-installed glibc or gcc == pain. This has been fixed with lockfiles. It's getting better in cvs. |