I don't see anything explicitly wrong with your KS file. I've never tried to get the i386 seamonkey package, but I am able to install some xorg i386 files in RHEL4-x86_64 via kickstart. So my guess is you're hitting a RHEL3 bug. On 10/20/06, Jamie Bohr <jamiebohr@xxxxxxxxx> wrote:
KS for Fedora acts the same way and I know there are several RH Engineers on this list. I think it is something on my part, something I don't understand or am missing. On 10/20/06, Lonni J Friedman <netllama@xxxxxxxxx> wrote: > > On 10/20/06, Jamie Bohr <jamiebohr@xxxxxxxxx> wrote: > > I am trying to install the only the 32 bit version of seamonkey (RHEL v3) on > > a system. There are plugin issues with the 64 version. I have > > seamonkey.i386 in my ks.cfg, the 64 version still gets installed. In my > > kickstart config. file I have the following for packages: > > > > %packages --resolvedeps > > @ X Window System > > @ GNOME Desktop Environment > > @ KDE Desktop Environment > > #@ Graphical Internet > > @ Sound and Video > > @ legacy-software-development > > @ compat-arch-support > > @ development-tools > > @ workstation-common > > @ x-software-development > > @ gnome-software-development > > @ development-tools > > @ development-libs > > @ kde-software-development > > @ ruby > > seamonkey.i386 > > evolution > > evolution-connector > > gaim > > gnomemeeting > > xchat > > kernel-source > > -sendmail > > postfix > > -dailup > > -office > > -games > > This is likely the wrong place to be asking about RHEL3 problems. > Have you checked whether there's a bugzilla bug for this?
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama@xxxxxxxxx LlamaLand http://netllama.linux-sxs.org
