obmtool:WARNING install failure. Missing [[many, many packages]]
Jonathan Guilbault
jonathang at canril.com
Tue Jun 19 16:18:10 CEST 2007
On June 14, 2007 02:10:36 pm Alain Spineux wrote:
> Please read the wiki about install in Fedora Core 6
Thanks Alain for the help. Unfortunately, the advice there did not resolve my
issue.
The wiki offers two suggestions. The first suggestion is to build with GCC
3.4; I attempted this and had the same issues.
The second is to disable SELinux for perl. SELinux is already set to
permissive in this installation of CentOS so this could not have been an
issue.
The error bootstrap gives after I try & run it is:
-bash: /kolab/etc/kolab/kolab_bootstrap: /kolab/bin/perl: bad interpreter: No
such file or directory
I believe this occurs because autopackage fails to install perl in the
autopackage environment; just like it is failing to install numerous other
packages.
Anyone have any insight? My original email has a list of the missing
packages. It starts with gcc-4.0.2-2.5.0.amd64-rhl5-kolab.rpm & ends with
kolab-horde-fbview-2.1.0-20070420.amd64-rhl5-kolab.rpm.
Thanks for your time & help.
> On 6/13/07, Jonathan Guilbault <jonathang at canril.com> wrote:
> > Hello,
> > First of all, I think that this problem could be related to the gcc
> > version
> > I'm using to build Kolab from source (as per the instructions on the
> > wiki).
> > I'm using gcc 4.1.1 on CentOS 5 to install Kolab 2.1.0 from source.
> >
> > Essentially, the install script completed and I discovered on bootstrap
> > that
> > perl was missing. I examined the log and found suggestions that numerous
> > other packages were missing.
> >
> > My last message had a log file attached and was too large. I've attached
> > two
> > files to this post that are much smaller:
> >
> > 1. "install-failure.log" is a grep for "failure" of the
> > kolab-build.logfile produced by the install command suggested in the
> > wiki. It lists dozens upon
> > dozens of install failures due to missing dependencies.
> >
> > 2. "unsatisfied-dependencies.log" is the product of "/kolab/bin/openpkg
> > rpm -Va", which was a check I found suggested in the output I examined in
> > the
> > log. It lists several packages as missing.
> >
> >
> > So:
> > 1. If this is due to the gcc version, what version of gcc do I need to
> > use to
> > compile Kolab 2.1.0 & the associated OpenPKG stuff from source?
> >
> > 2. If it's not my gcc version (I though OpenPKG >=2.5.x was supposed to
> > fix
> > the gcc >=4.0 issue), then does anyone have any idea what it is?
> >
> > Thank you for your time,
> > Jonathan Guilbault.
> >
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-users at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-users
--
Jonathan Guilbault,
Project Coordinator & Sales Manager.
Canril Corporation.
Office: 613 234-2296 ext. 229
More information about the users
mailing list