[Bug 235293] Review Request: adminutil - Utility library for Fedora Directory Server administration

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: adminutil - Utility library for Fedora Directory Server administration
Alias: adminutil

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235293





------- Additional Comments From mtasaka at ioa.s.u-tokyo.ac.jp  2007-05-24 12:22 EST -------
(In reply to comment #28)
> (In reply to comment #27)
> > (In reply to comment #26)
> > > (In reply to comment #25)

> > Okay. Then if you release new tarball (1.1.2), it is not a problem.
> 
> Is it necessary to re-version from 1.1.1 to 1.1.2?  1.1.1 has not yet been
> officially released.  I'd like to get all of these changes for fedora extras
> into 1.1.1.

I didn't know it...

> 
> > > > * For Requires problem of mozldap-devel against cyrus-sasl-devel,
> > > >   please see my comment (bug 240516 comment 2)
> > So please add "BuildRequires: cyrus-sasl-devel" to this package
> > (adminutil).
> 
> But I thought since adminutil does not use any 
> cyrus-sasl include files nor link
> directly to any cyrus-sasl libs, it doesn't need 
> BuildRequires: cyrus-sasl-devel?

Then please fix configure or the option of configre. 
Actually the lastest tarball I have locally checks the existence of
sasl.h and mock build fails without cyrus-sasl-devel.
-----------------------------------------------------
configure: checking for sasl...
checking for --with-sasl... no
checking for --with-sasl-inc... no
checking for --with-sasl-lib... no
checking for sasl.h... no
configure: error: sasl not found, specify with --with-sasl.
error: Bad exit status from /var/tmp/rpm-tmp.16648 (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.16648 (%build)
---------------------------------------------------------



-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.