gdk-pixbuf2 @2.26.5_1+x11 activation failure: conflict with gtk2 on gdk-pixbuf-csource

[tappoz84@…]

I am trying to install gdk-pixbuf2 and I am getting this error. Any hint?

MY_MACBOOK:~MY_USER$ 
MY_MACBOOK:~MY_USER$ 
MY_MACBOOK:~MY_USER$ 
MY_MACBOOK:~MY_USER$ sudo port selfupdate
Password:
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.1.2 installed,
MacPorts base version 2.1.2 downloaded.
--->  Updating the ports tree
--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated
MY_MACBOOK:~MY_USER$ 
MY_MACBOOK:~MY_USER$ 
MY_MACBOOK:~MY_USER$ 
MY_MACBOOK:~MY_USER$ sudo port install gdk-pixbuf2
--->  Computing dependencies for gdk-pixbuf2
--->  Activating gdk-pixbuf2 @2.26.5_1+x11
Error: org.macports.activate for port gdk-pixbuf2 returned: Image error: /opt/local/bin/gdk-pixbuf-csource is being used by the active gtk2 port.  Please deactivate this port first, or use 'port -f activate gdk-pixbuf2' to force the activation.
Please see the log file for port gdk-pixbuf2 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_gdk-pixbuf2/gdk-pixbuf2/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port gdk-pixbuf2 failed
MY_MACBOOK:~MY_USER$ 

[jmroot (Joshua Root)]

As per the ticket guidelines, please select the appropriate ticket type, fill in the Port field, and Cc the maintainer.

What version of gtk2 do you have installed?

[ryandesign (Ryan Carsten Schmidt)]

Prior to 2.22.0, gdk-pixbuf2 was part of gtk2. You would have encountered this problem if you were upgrading from gtk2 < 2.22.0 to gtk2 >= 2.22.0. The workaround would have been to deactivate gtk2 before upgrading:

sudo port -f deactivate gtk2
sudo port upgrade gtk2

If this were a current problem, we would use the deactivate hack to make the upgrade seamless. But ​2.22.0 was released in 2010 and this ticket was filed in 2013 so it wasn't even a current problem back then, and certainly isn't now, so there's nothing to do.