Description of problem: Evolution requires NetworkManager since very recently, probably via NetworkManager-glib. We have a number of thin clients with enough capacity to run evolution, firefox etc. All the networking, ip addresses, routes are static. However, since very recently, evolution demands that NetworkManager is installed. There is apparently something wrong with the dependency chain, I am not sure whether the fault is evolution's or NetworkManager-glib's. I think it would be sensible to restore the list of dependencies to the previous one, that is, evolution should not (indirectly?) require NetworkManager.
Evolution has had a build requirement on NetworkManager since 2006, which is necessary for synchronizing its online/offline mode with network availability.
Well, how do you explain then that I did not have NetworkManager installed so far and everything worked just fine? I think you confuse NetworkManager and NetworkManager-glib. If you want to close this bug, do it for the right reason. The one you specify does not explain the recent change in dependencies.
Nothing has changed on the Evolution side in this respect.
Thank you. So it is apparently NetworkManager-glib which has started to require NetworkManager package, then. Reassigning.
No, NM-glib has always required NetworkManager indirectly because it requires libnm-util.so, which was provided by the NetworkManager package. libnm-util has now moved into the NM-glib package, but because of multilib issues NM-glib must require NetworkManager as well. So I'm pretty sure that nothing in the dependency chain has changed here either, since anything requiring libnm_glib.so has always required the NetworkManager package as well... Can you get the following for us? rpm -q --requires evolution rpm -q --requires NetworkManager-glib
Created attachment 320642 [details] rpm -q --requires NetworkManager-glib I have checked the output and have come to following conclusions: evolution requires libnm_glib - so far so good. I don't have a problem with evolution requiring NetworkManager-glib. However, NetworkManager-glib requires explicitly NetworkManager! There is no library dependency here. This looks like a redundant requirement to me - what am I missing?
libnm_glib used to live in the main NetworkManager package. To fix #351101 (which this bug is really a dupe of) the library was moved to NetworkManager-glib. That, however, breaks multilib horribly, and thus for F9 and earlier there was an explicit dependency added between NetworkManager-glib and NetworkManager (#451519). This is fixed in rawhide, but cannot be fixed in F9 and earlier due to the multilib issues. You can turn NM off quite easily with 'chkconfig NetworkManager off' in your post-install scripts if you like and continue to use ifup/ifdown. *** This bug has been marked as a duplicate of bug 351101 ***