Am Donnerstag, 3. Juli 2008 schrieb ext James Homuth: > I went to run emerge update, and it threw this curious little block > loop at me. "emerge --pretend --quiet --update --deep world" produces: > [blocks B ] sys-apps/mktemp (is blocking > sys-apps/coreutils-6.10-r2) > > [blocks B ] >=sys-apps/coreutils-6.10 (is blocking > sys-apps/mktemp-1.5) > > Anyone else having this particular problem? Is it a compatibility > issue with either coreutils or mktemp? I'm assuming removing the one > will eliminate it, but if it's a needed package I'd rather not chance > it. Any info on this one would be greatly appreciated.
If you just searched the archives...
New coreutils contains mktemp -> coreutils blocks mktemp -> emerge -C mktemp
&& emerge coreutils
HTH...
Dirk
--
Dirk Heinrichs | Tel: +49 (0)162 234 3408
Configuration Manager | Fax: +49 (0)211 47068 111
Capgemini Deutschland | Mail: [EMAIL PROTECTED]
Wanheimerstraße 68 | Web: http://www.capgemini.com
D-40468 Düsseldorf | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net
signature.asc
Description: This is a digitally signed message part.
