gobby install fails - No package 'renderproto' found

[thewoolleyman@…]

debug output attached

[thewoolleyman@…]

log of gobby failing install with renderproto error

[blb@…]

--->  Activating xorg-renderproto @0.9.3_0
Error: Target org.macports.activate returned: Image error: /opt/local/include/X11/extensions/render.h is being used by the active render port.  Please deactivate this port first, or use 'port -f activate xorg-renderproto' to force the activation.

Okay, there's the problem, the render port has been gone for quite some time, so run

sudo port -f uninstall render
sudo port activate xorg-renderproto
sudo port clean --work xorg-libXrandr

Then give your install another try.

[thewoolleyman@…]

OK, I'll try that. However, (and this may be a dumb question, given my macports ignorance), is there still some bug that prevents this from "just working"? Like shouldn't the render port uninstall itself or be uninstalled as part of some update process?

Thanks, -- Chad

[blb@…]

Usually ports are kept around as a stub for a time, then deleted. Other than that, there isn't a method of denoting this yet, that would be ticket #20157.

[thewoolleyman@…]

I got this working with another command (had tried it myself before your prior comment).

I believe this was the trick (some other random incorrect things omitted):

sudo port clean --work xorg-renderproto
sudo port -f install xorg-renderproto

I'm still wondering if this could have just "fixed itself" - why did I have a long-gone invalid 'render' port, and why didn't it just get autoupgraded or auto-replaced or something, without the need for manual intervention like this.

Anyway, works now. Thanks a lot for your help.

-- Chad

[thewoolleyman@…]

Oh, sorry, missed the last comment. #20157 would have helped this problem. Thanks!!!

[blb@…]

If you had done something like sudo port upgrade outdated during the time render was made into a stub, then it would have ceased to conflict with xorg-renderproto (though remain installed). Unfortunately (as you see with #20157) this isn't a well-supported option yet, since renaming/deprecating ports hasn't happened much; usually ports have been added over time.