John Covici wrote: > On Wed, 14 Dec 2016 00:06:00 -0500, > Philip Webb wrote: >> I just updated Qt5 to 5.6.2 & ran into a familiar Portage problem. >> >> The emerge command responds with a list of "conflicts", >> all involving 5.6.1 vs 5.6.2 versions of the c 15 pkgs. >> The only way to get around this is to unmerge the existing pkgs via '-C', >> then install the new versions. That works, but it's brute force. >> >> Portage sb able to resolve this kind of conflict for itself. >> If not, then at least it should advise users intelligently >> to do what I've just described. It can happen with other sets of pkgs. >> >> Yes, I did do 'backtrack==30'. >> >> Before I send in a bug, does anyone else have useful comments ? > I wonder if a larger backtrack=120 or higher would fix your problem or > get portage to detect the blocks? 30 seems hardly enough these days. >
I set mine to 100 at least a year ago. As you say, 30 just didn't go quite deep enough in some situations. It takes emerge longer to resolve it but it seems to resolve it better which is better than being fast but not able to complete the job. Dale :-) :-)
