[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#83434: "apt-get install gnome-panel" complains about broken packages



Daniel Jacobowitz wrote:

> On Fri, Jan 26, 2001 at 09:39:03AM -0500, Adam C Powell IV wrote:
> > I think this is just because gnome-core and gnome-applets haven't been built and
> > uploaded for PPC in a *very* long time.  Building those two packages (and their
> > Build-Depends before them) should fix this.  If this user has the guts to use
> > unstable, he/she should be able to recognize such a missing dependency for what it
> > is. :-)
> >
> > If I get some time this weekend I'll bulid the latest everything (through nautilus
> > and gnumeric) and upload myself.
>
> Here's something I should really have announced on this list:
>
> Build logs are now available!  Look at:
> <http://voltaire.debian.org/buildd/buildlogs/<sourcepackage>/latest>
>
> Gnome-core, it tells me, is waiting on "libgtkhtml-dev".  That comes
> from gtkhtml, which waits on libcapplet-dev, from control-center.  That
> is in turn waiting on libglade-gnome0-dev (>= 0.13-2), from libglade.
> At last attempt (a while ago), libglade utterly failed to build.
> Currently, it doesn't build because libbonobo-dev is not installable.
>
> libbonobo-dev is not installable because bonobo is out of date, I
> think, and possibly because gnome-print is out of date.  In turn,
> bonobo is not built because it has an unsatisfiable build dep on
> gnome-print, because gnome-print is out of date.  It looks to me like
> gnome-print didn't build because of a gdk-pixbuf dependency somewhere.
>
> In fact, it all comes back to a missing build dependency in
> gnome-print (libgdk-pixbuf-dev)!  I -hate- doing this, but I'm going to
> force the issue and build it myself.
>
> Vincent, mind fixing this?  Meanwhile, I've uploaded a new (binary)
> gnome-print.  It may take a few days to propogate the dependency chain,
> but the rest of gnome should build now.

So I got fed up and just decided to build and upload everything over the weekend.  Not
everything was as smooth as could be hoped...

   * gnucash needs to have -fsigned-char removed from debian/rules in order to display
     currency fractions.  I built and uploaded accordingly.  See bug #69866.
   * libglade building is broken.  I've submitted a patch as part of bug #84298, and
     built and uploaded with that patch.  This is pretty high in the build-depends
     chain for most everything new, so its breakage was keeping back a lot of packages.
   * A few packages are still missing Build-Depends, in spite of my suggested lists,
     e.g. in bugs 59394 (gwrapguile) and 75636 (gnumeric).
   * gtkhtml (->gnome-db) and nautilus no longer build because upstream has changed the
     bonobo interface again...  (nautilus also requires non-US ammonite to build, and
     recommends it; I can't upload this from the U.S.)  But a new nautilus was released
     in the last day or two, which may build with a current system, as soon as it's
     debianized.
   * If you can get the new gtkhtml to build (e.g. if you have old bonobo), then
     gnome-core will not build with the libgtkhtml-dev package installed, because of
     very significant API changes.

The 2.2.10-1 libs packages reached me before I built, so it all got linked to
libgnomeui33, then 2.2.11-1 decremented it back to 32!  What the heck?!  So, everybody
gets stuck with an extra libgnomeui shared libs package until all of those packages are
rebuilt again.

It looks like between the major releases (e.g. 1.2 and 1.4), the GNOME authors are not
doing a great job of coordinating releases.  Then again, this is labeled as "unstable"
on the GNOME site, so as much could be expected.  Of course, the Debian packages could
(should?) have just stuck with stable 1.2, with the 1.4 release being pushed farther
and farther into the future (last summer they said October, last September they said
December, now they're saying March!).

Some schedule slippage is unavoidable of course, but packaging unstable GNOME stuff
without decent feature projections for 1.4 was IMHO premature, as it's breaking
testing/unstable all over the place, and could land us in the awkward position of
having to downgrade everything in advance of the Woody freeze. :-(

-Adam P.

GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

                 Welcome to the best software in the world today cafe!



Reply to: