I'm using "emerge --nospinner --quite --sync" to update my portage tree via cron.daily. Since this function was changed to display a percentage value when "Updating Portage Cache" I receive a lot of garbage. Reproducible: Always Steps to Reproduce: 1. emerge --nospinner --quite --sync 2. look at output Actual Results: emerge --nospinner --quite --sync: >>> starting rsync with rsync://134.147.32.57/gentoo-portage... >>> checking server timestamp ... >>> Updating Portage cache: ^H^H1%^H^H2%^H^H3%^H^H4%^H^H5%^H^H6%^H^H7%^H^H8%^H^H9%^H^H^H10%^H^H^H11%^H^H^H12%^H^H^H13%^H^H^H14%^H^H^H15%^H^H^H16%^H^H^H17%^H^H^H18%^H^H^H 19%^H^H^H20%^H^H^H21%^H^H^H22%^H^H^H23%^H^H^H24%^H^H^H25%^H^H^H26%^H^H^H27%^H^H^H28%^H^H^H29%^H^H^H30%^H^H^H31%^H^H^H32%^H^H^H33%^H^H^H34%^H ^H^H35%^H^H^H36%^H^H^H37%^H^H^H38%^H^H^H39%^H^H^H40%^H^H^H41%^H^H^H42%^H^H^H43%^H^H^H44%^H^H^H45%^H^H^H46%^H^H^H47%^H^H^H48%^H^H^H49%^H^H^H50 %^H^H^H51%^H^H^H52%^H^H^H53%^H^H^H54%^H^H^H55%^H^H^H56%^H^H^H57%^H^H^H58%^H^H^H59%^H^H^H60%^H^H^H61%^H^H^H62%^H^H^H63%^H^H^H64%^H^H^H65%^H^H ^H66%^H^H^H67%^H^H^H68%^H^H^H69%^H^H^H70%^H^H^H71%^H^H^H72%^H^H^H73%^H^H^H74%^H^H^H75%^H^H^H76%^H^H^H77%^H^H^H78%^H^H^H79%^H^H^H80%^H^H^H81% ^H^H^H82%^H^H^H83%^H^H^H84%^H^H^H85%^H^H^H86%^H^H^H87%^H^H^H88%^H^H^H89%^H^H^H90%^H^H^H91%^H^H^H92%^H^H^H93%^H^H^H94%^H^H^H95%^H^H^H96%^H^H^H 97%^H^H^H98%^H^H^H99%^H^H^H^H100% Expected Results: Is it possible to deactivate the counter when using --nospinner and/or --quite?
Utilized the "--quiet" option to do this.
Fixed on or before 2.0.51.22-r1
Looking through the batch of bugs, I'm not sure that some of these are actually fixed in stable. Others, the requirements have possibly changed after the initial fix was committed. If you think this bug has been closed incorrectly, please reopen or ask that it be reopened.
