Summary: | portage-2.2_rc2 and rc3: emerge allows parallel-fetch to keep running when it shouldn't | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | lordcris |
Priority: | High | Keywords: | InVCS |
Version: | 2007.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077 | ||
Attachments: | cancel fetchers when they are all that's keeping the main loop alive |
Description
Juergen Rose
2008-07-26 09:29:40 UTC
same here *** This bug has been marked as a duplicate of bug 232978 *** I would like to reopen the bug. I mean it is not a duplicate of bug 232978. The core of this bug is not the missing tar file, but the long hanging of emerge without any message about the problem. Which Portage version are you using? I did override FETCHCOMMAND locally, because default wget time out values suck completely, but I don't know, if this really is the reason Portage stalls here. Hi Carsten, I am using portage-2.2_rc3. Juergen Created attachment 161413 [details, diff]
cancel fetchers when they are all that's keeping the main loop alive
Somebody reported this yesterday and it was fixed in svn r11185.
This is fixed in 2.2_rc4. |