[WBEL-devel] Unable to install gimp-perl (missing dependencies)

John Morris jmorris@beau.org
Sun, 14 Dec 2003 20:37:34 -0600 (CST)


On Sun, 14 Dec 2003, Milan Kerslager wrote:

> I'm unable to satisfy dependencies in RC2 for gimp-perl:
> 
> $ yum install gimp-perl
> [...]
> package gimp-perl needs perl(Gtk) (not provided)
> package gimp-perl needs perl(Gtk::Atoms) (not provided)
> package gimp-perl needs perl(Gtk::Gdk) (not provided)
> package gimp-perl needs perl(PDL) (not provided)
> 
> 
> I miss perl-PDL and Gtk-Perl (it requires libglade, gtkhtml, gal). Why
> these packages are in lostRPMS when there is no chance to use gimp-perl?
> I read about "packages required to make WBEL".

Basically the lostRPMS are packages needed to rebuild the distro but not 
included in RHEL3.  An everything install of WBEL installs gimp-perl so 
some research is apparently called for to find out why yum isn't figuring 
out how to satisfy dependencies that anaconda solves.  Anaconda has no 
access to the lostRPMS btw.

> It seems that gimp package should be recompiled whithout dependencies
> above or these packages should be placed in main distro or gimp-perl
> should be not included in WBEL (like is not in Taroon).

As far as I can tell, Gimp is compiled the same as in RHEL which is the
goal.  Interesting that RH left gimp-perl out though.  Just checked and it
isn't even in the beta.  But including the full output of rebuilding their
SRPMS should not be a problem.  There are several other known cases like
this, such as msql and rh-postgresql only including the client packages in
RHEL3 and moving the server to the extras disk while WBEL3 includes them
in the base.  Because RH charges extra for support on the databases and
WBEL doesn't support any of it anyway.

> I'm woting to include them but it could be worth to include updated
> packages from Fedora Core because (already) fixed bugs (if only relase
> is bumped up and not version or simply test the packages - like
> Gtk-Perl).

Only want to deviate from the exact packages in RHEL3 when forced to by
either trademark issues or in the case of yum & up2date to allow a method
of errata distribution apart from RHN.

Any serious bugs should get reported to and fixed by RH and WB will pick
them up that way.  Any other course risks either forking or backing out a
local fix and picking up a possibly different solution when RH fixes a
problem we tried to jump the gun on and fix ourselves.  Remember, WBEL not 
only has to track Red Hat's changes during this cycle, it has to remain 
faithful enough that when RHEL4 drops and we clone it, upgrades can happen 
from WBEL3 to WBEL4, from RHEL3 to WBEL4, etc. with minimum suprises.

-- 
John M.      http://www.beau.org/~jmorris        This post is 100% M$ Free!
Geekcode 3.1:GCS C+++ UL++++$ P++ L+++ W++ w--- Y++ b++ 5+++ R tv- e* r