reinstalling Macports

[pagani laurent]

Before you mention it,I tried to force activations, I tried to deactivate tk, everything fails at some point. 
I tried indeed to uninstall and reinstall MacPorts too but apart from erasing all my tools, I am still bumping against this problem (and xemacs running has nothing to do with it). So it is even worse today… I am running Sierra 10.12.6 by the way and XCode 8.3.3. However, trying to open XCode, it asked for some components to be installed. Not sure it has something to do with all that, but I mention just in case.

I attach the output of port contents tk

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: tk_contents.txt
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20180418/f8583135/attachment.txt>
-------------- next part --------------

> Le 18 avr. 2018 à 05:23, Ryan Schmidt <ryandesign at macports.org> a écrit :
> 
> 
> On Apr 17, 2018, at 06:08, pagani laurent wrote:
> 
>> --->  Activating xorg-xproto @7.0.31_0
>> Error: Failed to activate xorg-xproto: Image error: /opt/local/include/X11/X.h is being used by the active tk port.  Please deactivate this port first, or use 'port -f activate xorg-xproto' to force the activation.
>> 
>> The log is attached (compressed… otherwise above 500 kb)
>> Should I force activation and relaunch the .restore_ports.tcl or should I totally erase the /opt/local branch, reinstall Macports and launch the restore_ports.tcl or will the later fail because everything has been erased ? Or did it fail because I run XEmacs (from opt/local/bin/xemacs) in parallel ?
> 
> You should not force the activation.
> 
> Since we don't yet know why this problem happened for you, uninstalling and reinstalling MacPorts again might result in the same problem again, so I would not recommend doing that at this point.
> 
> tk should not provide /opt/local/include/X11/X.h. What else does it provide that it should not? What's the output of:
> 
> port contents tk
> 
> If we could see the log of the tk build, that might help us understand why it is providing files it should not, but unfortunately, MacPorts automatically removes the logs of builds it considers successful.
>