I don't know if this is a bug, but it is definitely a "feature" I do not want. After syncing, I use emerge -f (or more completely emerge -Dfu world) to download the required sources before doing updates (yes, I know about parallel-fetch, no, this doesn't have anything to do with it). With the previous portage (2.1.6.13), these fetches did not get logged period. These fetches now get logged in /var/log/emerge.log (using 2.1.7.16). I do not want them logged. How do I stop them from being logged? A typical occurance looks like this (with the first six lines from emerge --sync): 1265243144: Started emerge on: Feb 04, 2010 00:25:44 1265243144: *** emerge --with-bdeps --verbose sync 1265243144: === sync 1265243145: >>> Starting rsync with rsync://172.28.228.168/gentoo-portage 1265243231: === Sync completed with rsync://172.28.228.168/gentoo-portage 1265243238: *** terminating. 1265243541: >>> emerge (1 of 5) media-sound/alsa-headers-1.0.21 to / 1265243542: >>> emerge (2 of 5) media-libs/alsa-lib-1.0.21a to / 1265243554: >>> emerge (3 of 5) dev-libs/libgcrypt-1.4.5 to / 1265243567: >>> emerge (4 of 5) sys-apps/util-linux-2.16.2 to / 1265243604: >>> emerge (5 of 5) media-sound/alsa-utils-1.0.21-r1 to / 1265243616: *** Finished. Cleaning up...
Created attachment 218467 [details, diff] fix emerge.log disabling code Save as /tmp/emergelog.patch and apply as follows: cd /usr/lib/portage patch -p0 < /tmp/emergelog.patch
*** Bug 119049 has been marked as a duplicate of this bug. ***
This is fixed in 2.1.8 and 2.2_rc64.
