Because the default Portage behavior has changed.
Old: $ emerge world
New: $ emerge -u world
New Portage thinks that a simple “emerge world” means you want to reinstall everything.
Shame on you for not zealously reading and memorizing everything that Portage has to tell you. Bad Admin. Bad.
Something else I should have known about long ago. To turn on logging in portage, simply add the following to /etc/make.conf:
PORTAGE_ELOG_CLASSES="warn error log"
PORTAGE_ELOG_SYSTEM="save"
The will add log files for each package to /var/log/portage/elog/:
# ls -lah
total 108K
drwxrws--- 2 portage portage 4.0K 2008-06-06 01:13 .
drwxr-xr-x 3 root root 4.0K 2007-10-04 12:29 ..
-rw-r--r-- 1 root portage 200 2008-06-06 00:58 dev-db:postgresql-8.0.15:20080605-155810.log
-rw-rw-r-- 1 root portage 72K 2008-06-06 00:44 summary.log
-rw-r--r-- 1 root portage 67 2008-06-06 01:06 sys-apps:coreutils-6.10-r2:20080605-160624.log
-rw-r--r-- 1 root portage 108 2008-06-06 01:08 sys-apps:shadow-4.0.18.2:20080605-160842.log
Useful to have around when you miss a barrage of announcements after a large emerge.
Looks like mktemp is now provided by coreutils. No wonder. This block has been bugging me (read: I’ve been ignoring it) for months.
To fix just unmerge mktemp and update coreutils.
Update: Same for the setarch / util-linux block should you come across it. Unmerge setarch.
Twitter: nurikabe