Summary: | slocate hard blocks mlocate | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | JMW <jessemichaelwilson> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | alex_y_xu, bkohler |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
JMW
2014-01-23 01:25:21 UTC
Is slocate in your world file? It's not now because I did "emerge -C slocate". But it almost certainly was before. Nothing depends on slocate as far as I can tell, so I would have had to either "emerge -1 slocate" or explicitly merge it, and I recall explicitly merging it on several systems in the past. However, the move from slocate to mlocate should be a trivial update, so the block should be blue. That auto-unmerge to resolve the blocker cannot happen if slocate is in your world file. This is by design, as far as I know. They are separate packages. If you have one in world, portage *must not* replace one with the other automatically. Maybe a "virtual/locate" or even "virtual/mlocate" would resolve this. Actually, slocate has not been in portage for over three years, so this is even more invalid. http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-apps/slocate/ChangeLog?view=log Ah, I didn't realize I was that out of date. I just did an emerge --ask --newuse --deep @world last week but I guess that doesn't take care of all old packages. |