First, thanks to all who responded with hints and suggestions. On Fri, Dec 05, 2003 at 05:44:32PM +0100, Spider wrote: > Currently you cant, see last weeks big flameage in -dev for possible > solutions, reasoning and whatnot. They should be google-able. (hint, > ACCEPT_LICENSE is a nice searchword for google )
Heh, what timing, eh? :-) > Not serious, i haven't found the real source here, but its a lockfile > that doesn't go away after devfsd. The "couldn't find match" are simply > messages stating that it cannot uninstall a previous version, because > none was installed. Hmm, why was it trying to uninstall it then? (I'm a little confused on that.) I'm also a little confused about two other things: 1. What is the way to safely remove software from the system? I observed the warning in emerge(1) about unmerge doing no dependency checking. So I could unmerge something that half a dozen other programs depend on, thus causing nasty breakage. Is there an unmerge command somewhere that *does* do this dependency checking, and aborts with an error if I try to unmerge something that others depend on? 2. Excepting the slots mechanism for a minute, it still appears possible to have multiple versions of a single package installed at once. However, I've noticed that when this happens, generally only a single version is *actually* installed; portage just thinks that two are on the system (and I can safely remove the older one, which is mostly a no-op). What is the point of this, and how can I make it stop? It seems that portage is lying to me, saying that an older package is installed when really the version on the system is newer. Thanks, John -- [EMAIL PROTECTED] mailing list
