After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 316867 - DBus' gtk-sharp dependency causes endless loop
DBus' gtk-sharp dependency causes endless loop
Status: RESOLVED FIXED
Product: GARNOME
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GARNOME Maintainers
garnome list
Depends on:
Blocks:
 
 
Reported: 2005-09-21 18:51 UTC by Torsten Schoenfeld
Modified: 2005-10-21 18:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Torsten Schoenfeld 2005-09-21 18:51:45 UTC
DBus' dependency on gtk-sharp causes an endless loop:

  dbus-0.36.2 <----------.
  -> gtk-sharp-1.0.10     |
  -> gtkhtml-3.8.0        |
  -> libbonoboui-2.10.1   |
  -> libgnome-2.12.0.1    |
  -> gnome-vfs-2.12.0 ----'

(I spent more time drawing this ASCII diagram than to actually track down the
bug. :-))
Comment 1 Joseph Sacco 2005-09-21 19:16:27 UTC
(1) what version of GARNOME are you attempting to build?
(2) in which directory did you start the build?

-Joseph
Comment 2 Torsten Schoenfeld 2005-09-21 19:41:20 UTC
I'm using garnome-2.12.0.1 and I started the build in "desktop" via "make
paranoid-install".
Comment 3 Joseph Sacco 2005-09-21 20:16:28 UTC
You were "doing the right thing", building with "make paranoid-install" 

hmmm...???

The mono dependencies for dbus came about because beagle needed dbus-sharp. As
of beagle-0.0.10 that dependency has been removed, so "we" need to rethink these
dependencies.

To get you going
-----------------
You can remove the mono dependencies from dbus an roll on. Afterwards you can
rebuild dbus with the mono dependencies.

where did the circular dependency come from?
--------------------------------------------
Not sure [yet]... I would have thought that gnome-vfs, which does not explicitly
use dbus-sharp, would have been built and installed long before any of the mono
stuff. The post-install target in the mono Makefile was put there to rebuild
dbus *after* mono had been built.

What was being built when this happened? The following grep commands may help,

     grep "BUILDING" make_paranoid-install.log
     grep "\[install\]" make_paranoid-install.log


-Joseph
Comment 4 Joseph Sacco 2005-09-22 15:58:49 UTC
Something is amiss. I am guessing that mono was installed before you started or
restarted a build in ./desktop.

The first app to be built in ./desktop is bug-buddy. Building bug-buddy requires
that 52 other packages be first built and installed.  This dependency set
includes, among other things:

   * libbonobo
   * dbus
   * gnome-vfs
   * libgnome
   * libbonoboui

The bug-buddy dependency set does *not* include mono.

If the apps in the ./mono directory are built after the apps in ./desktop have
been built, dbus will be rebuilt [see post-install target in
./mono/mono/Makefile] in order to build the mono plugin, dbus-sharp. At that
point gnome-vfs will have already been installed so no cyclic dependency will be
seen.

-Joseph
Comment 5 Torsten Schoenfeld 2005-09-24 18:56:21 UTC
> Something is amiss. I am guessing that mono was installed before you started or
> restarted a build in ./desktop.

Yes, I think this was the case.  I installed 2.12.0.1 into the same prefix I
used for 2.12.0 -- so Mono was already installed.

I just tried a clean run with a different prefix and the problem didn't occur.

Now, if you don't want to support installing into an existing prefix, this is
not a bug and be closed.
Comment 6 Bob Kashani 2005-10-21 18:59:52 UTC
This has been fixed...and will be in garnome-2.12.2.

It was a LIBDEPS issue.