Bug 88172 - build requirement imap-devel not in spec file
build requirement imap-devel not in spec file
Status: CLOSED DUPLICATE of bug 74819
Product: Red Hat Linux
Classification: Retired
Component: php (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-04-07 07:55 EDT by av3
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:52:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description av3 2003-04-07 07:55:45 EDT
Description of problem:
About php source RPM.
build requirement imap-devel not in spec file.

Version-Release number of selected component (if applicable):

How reproducible:
rpmbuild SPECS/php-4.2.2-8.0.5.spec

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 av3 2003-04-07 08:08:13 EDT
also buildreqs byacc and flex not in spec file
Comment 2 Joe Orton 2003-04-07 08:14:24 EDT
imap-devel require fixed per bug 74819 - what error do you get if building
without  flex or yacc?  The generated files are included in the tarball, and I
can't see where buildconf requires you to regenerate them.
Comment 3 av3 2003-04-07 08:21:24 EDT

for the flex and yacc is my fault; I threw in a fresh php tarball from php.net.

I haven't figured out how to search correctly from bugzilla yet, since I
searched for the bugs and didn'd find them. Also needed libelf-devel, but that
was also fixed I guess...

Comment 4 Joe Orton 2003-04-07 08:39:06 EDT
Yep, the lack of a buildrequire for libelf-devel was a netsnmp bug.  I'll mark
this a duplicate of the other bug - please open a new bug if you find more
missing dependencies.

*** This bug has been marked as a duplicate of 74819 ***
Comment 5 Red Hat Bugzilla 2006-02-21 13:52:31 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.