When I run 'revdep-rebuild -- -a' I expect to be presented with a list of packages that will be re-emerged and prompted to chose Yes or No. Instead, the prompt appears to be interrupted. Reproducible: Always Steps to Reproduce: 1. Run revdep-rebuild -- -a Actual Results: Checking reverse dependencies... Packages containing binaries and libraries broken by any package update, will be recompiled. Collecting system binaries and libraries... using existing /root/.revdep-rebuild.1_files. Collecting complete LD_LIBRARY_PATH... using existing /root/.revdep-rebuild.2_ldpath. Checking dynamic linking consistency... using existing /root/.revdep-rebuild.3_rebuild. Assigning files to ebuilds... using existing /root/.revdep-rebuild.4_ebuilds. Evaluating package order... using existing /root/.revdep-rebuild.5_order. All prepared. Starting rebuild... emerge --oneshot --nodeps -a =net-www/mozilla-firefox-bin-1.0 .......... These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] net-www/mozilla-firefox-bin-1.0 Total size of downloads: 0 kB Do you want me to merge these packages? [Yes/No] Interrupted. Result is not OK, you have following choices: - if emerge failed during build, fix the problems and re-run revdep-rebuild or - use -X or --package-names as first argument (try to rebuild package, not exact ebuild - ignores SLOT!) or - set ACCEPT_KEYWORDS="~<your platform>" and/or /etc/portage/package.unmask (and remove /root/.revdep-rebuild.5_order to be evaluated again) or - modify the above emerge command and run it manually or - compile or unmerge unsatisfied packages manually, remove temporary files and try again (you can edit package/ebuild list first) To remove temporary files, please run: rm /root/.revdep-rebuild*.?_* ------------- At the point where the prompt is presented the emerge command seems to recieve an interrupt, and does not allow me to input an answer. Expected Results: Allowed me to answer the prompt in the same way that emerge -av does.
This is a duplicate of #37485
*** This bug has been marked as a duplicate of 37485 ***
