Michael Orlitzky wrote: > On 4/22/20 11:58 AM, John Covici wrote: >> Yes, portage agrees with that statement, maybe I didn't give you the >> whole log, I thought it said that in there -- I did see that, I am >> sure. My question is how does this work normally, when you merge a >> package and update is this not always the case that there are files >> owned by the previous version on the system? >> > Yeah, but the package manager knows which files are owned by the version > being replaced and it doesn't complain about those. > >
Correct. OP, a little more detail, someone correct me if I'm not clear enough here. If you install abc-1 with one set of files but the package is slotted and abc-2 is installed, portage knows what files are where and what version of the package they belong too. Thing is, this is different. Portage/emerge thinks those file belong to another package. Whether it is a different version or a package with a different name doesn't matter. Portage keeps a database of every file it installs and what package it belongs to, including version if slotted. When there is a clash, emerge detects that and spits out the message you see. If you are certain that those files should be replaced and do not affect other packages, I'd either disable the protection with the FEATURES thingy or manually remove those files. Once you do that, update/re-emerge the package and test it. Dale :-) :-)
