Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 635604

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) gentoo-dev 2017-10-27 16:44:24 UTC
Today when creating frash gentoo stage4 I came across a situation where vim's post-inst failed, which resulted in the whole `emerge -NuD @world` to later return code 1, but the execution of emerge was not stopped, so I had to go thru thousands of log lines to find what was the problem here.

The problem is reproducable on  sys-apps/portage-2.3.12.

the whole build.log is attached, witht eh update process, it's execution, failed post-steps.
Comment 1 Piotr Karbowski (RETIRED) gentoo-dev 2017-10-27 16:45:00 UTC
Created attachment 500426 [details]
emerge update log
Comment 2 Piotr Karbowski (RETIRED) gentoo-dev 2017-10-27 16:53:30 UTC
Just to clarify. I would expect emerge to stop after the post-inst failure, rather than keeping going, like with `--keep-going`.
Comment 3 Zac Medico gentoo-dev 2017-10-27 17:43:31 UTC
Yes, I suppose we can make --keep-going control this behavior.
Comment 4 Piotr Karbowski (RETIRED) gentoo-dev 2017-10-27 18:01:58 UTC
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.
Comment 5 Zac Medico gentoo-dev 2017-10-27 18:08:54 UTC
The current behavior is expected, since emerge mostly ignored postinst failures until bug 547778.