Summary: | sys-apps/portage: postinst failure of packages does not stop emerge, but result in non zero exit code later | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Piotr Karbowski (RETIRED) <slashbeast> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=547778 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 373807 | ||
Attachments: | emerge update log |
Description
Piotr Karbowski (RETIRED)
2017-10-27 16:44:24 UTC
Created attachment 500426 [details]
emerge update log
Just to clarify. I would expect emerge to stop after the post-inst failure, rather than keeping going, like with `--keep-going`. Yes, I suppose we can make --keep-going control this behavior. I am not sure if I got you right. I did not run it with `--keep-going`, but from what I see, the emerge acts just like I would expect it, if I added it there, so ignoring the failure. The current behavior is expected, since emerge mostly ignored postinst failures until bug 547778. |