I updated the system, and an update to portage was present. I used the -a option when I did that and answered yes to the question. After the portage package was merge, I was asked again for the other packages to be installed past it. I already answered that question. From a user point of view, the restart of portage shouldn't remove the user's answer unless the package list differ. Now I understand that this may be seen as difficult, but still it is annoying as I am used to have emerge system complete its task without interactivity need. And I am in love with the -a option now ;-) Reproducible: Always Steps to Reproduce: 1. 2. 3.
-a implies interactive... It's another special case.
I agree with the problem here - I update a large number of machines and having to check up on them every 10 minutes to make sure that it's not sitting and waiting for me to type yes is anoying, to say the least. Perhaps we can simply remove the -a flag upon any recursive invocation of emerge? I'm not familiar with the code so I don't know how the restart/reload is implemented but I cannot imagine that this should be too difficult.
Still not resolved and a major pain in the backside.
Will be in >portage-2.0.50_rc1
I'm running portage-2.0.50-r11 and it still asks twice when portage is being updated. Did the fix really get merged?
Another typo... Fixed (and the fix fixed) in >=portage-2.0.51_rc6
Bug has been fixed and released in stable portages on or before 2.0.51-r2
