Long time ago a kdelibs-update installed mdnsresponder as a depency. For some reason I didn't like mdnsresponder and substituted mdnsresponder by the avahi-daemon. Some time afterwards I decided to get completely rid of the zeroconf stuff. So on that system there's nothing installed which referes to zeroconf, avahi or mdnsresponder. Today I reinstalled anjuta and checked the system depencies with revdev-rebuild. I got a lot of those errors: libavahi-common.so.3 libavahi-glib.so.1) * broken /usr/lib/anjuta/libanjuta-sourceview.la (requires /usr/lib/libavahi-glib.la) * broken /usr/lib/anjuta/libanjuta-sourceview.la (requires /usr/lib/libavahi-client.la) * broken /usr/lib/anjuta/libanjuta-sourceview.la (requires /usr/lib/libavahi-common.la) * broken /usr/lib/anjuta/libanjuta-sourceview.so (requires libavahi-client.so.3 libavahi-common.so.3 libavahi-glib.so.1) * broken /usr/lib/anjuta/libanjuta-subversion.la (requires /usr/lib/libavahi-glib.la) * broken /usr/lib/anjuta/libanjuta-subversion.la (requires /usr/lib/libavahi-client.la) * broken /usr/lib/anjuta/libanjuta-subversion.la (requires /usr/lib/libavahi-common.la) * broken /usr/lib/anjuta/libanjuta-subversion.la (requires /usr/lib/libsocks.la) * broken /usr/lib/anjuta/libanjuta-subversion.so (requires libavahi-client.so.3 libavahi-common.so.3 libavahi-glib.so.1 libsocks.so.0) * broken /usr/lib/anjuta/libanjuta-symbol-browser.la (requires /usr/lib/libavahi-glib.la) * broken /usr/lib/anjuta/libanjuta-symbol-browser.la (requires /usr/lib/libavahi-client.la) * broken /usr/lib/anjuta/libanjuta-symbol-browser.la (requires /usr/lib/libavahi-common.la) * broken /usr/lib/anjuta/libanjuta-symbol-browser.so (requires libavahi-client.so.3 libavahi-common.so.3 libavahi-glib.so.1) * broken /usr/lib/anjuta/libanjuta-terminal.la (requires /usr/lib/libavahi-glib.la) * broken /usr/lib/anjuta/libanjuta-terminal.la (requires /usr/lib/libavahi-client.la) * broken /usr/lib/anjuta/libanjuta-terminal.la (requires /usr/lib/libavahi-common.la) * broken /usr/lib/anjuta/libanjuta-terminal.so (requires libavahi-client.so.3 I don't know where anjuta invents that Avahi depencies, because at another computer - a complete fresh install that Avahi depency doesn't exist. Also I don't know from where Anjuta could know that there was the Avahi-Daemon installed long time ago. I the meantime since deinstalling the "Avahi-Virus" there were several gcc-, glibc-, binutils- and a lot of other updates. Reproducible: Always Steps to Reproduce: 1. Install Avahi (and do a whole system update) 2. Deinstall Avahi (and do a whole system update again) 3. Install Anjuta 4. Do a revdep-rebuild. Actual Results: revdep-rebuild gives me a lot broken avahi-depencies in anjuta. Reinstalling Anjuta doesn't help. Expected Results: No Avahi-depency where no avahi is installed. locate avahi gives me only the ebuilds with "avahi" in there name. So if there's not something of avahi hardcoded in some libs, there's really nothing avahi-related installed on my system.
What you are facing is a problem very similar (in a way) to bug 158476. See if for a solution.
Ok, I solved the problem. The solucion is to deinstall Anjuta completely and reinstall it. Only to update the package doesn't touch the files in /usr/lib/anjuta. Therefore it seems to be necessary to deinstall Anjuta first. Only that removes the /usr/lib/anjuta-directory. What to do now?
(In reply to comment #2) > What to do now? I'd say we wait for input from the anjuta maintainer
(In reply to comment #2) > Ok, I solved the problem. The solucion is to deinstall Anjuta completely and > reinstall it. > > Only to update the package doesn't touch the files in /usr/lib/anjuta. > Therefore it seems to be necessary to deinstall Anjuta first. Only that removes > the /usr/lib/anjuta-directory. this sounds wrong, I don't see why reinstalling anjuta wouldn't erase existing files unless anjuta somehow relinks against installed anjuta libs all the way. It wouldn't be the first time though.
anjuta 2.24.x was still generated with libtool 1.5 last time I checked and since it was one of the biggest users of "libs linking against other libs within the same project", I would definitely bet a buck that libtool is to blame. Maybe 2.26 is generated with libtool 2.2? In any case, it'd be worth checking.
avahi is picked up somehow by the build system and creeps in every libs installed by anjuta while there is no reason for it being the case. We really need to review their autofoo since we concluded with remi that it was doing way too many suspicious stuff already.
(In reply to comment #5) > anjuta 2.24.x was still generated with libtool 1.5 last time I checked and > since it was one of the biggest users of "libs linking against other libs > within the same project", I would definitely bet a buck that libtool is to > blame. > > Maybe 2.26 is generated with libtool 2.2? In any case, it'd be worth checking. > Still valid with anjuta-2.26* ?
or even better with anjuta-2.28 ;-)
Please get back to us. Thanks
