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.
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.