Bug 243310 - SRPM spec file references non-existent Python files
SRPM spec file references non-existent Python files
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: libevent (Show other bugs)
8
i386 Linux
low Severity medium
: ---
: ---
Assigned To: Steve Dickson
bzcl34nup
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-08 10:50 EDT by Alex Dean
Modified: 2008-04-04 08:06 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-04 08:06:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alex Dean 2007-06-08 10:50:12 EDT
Description of problem:
Building libevent-1.3b-1.fc7.src.rpm fails.  The spec file attempts to package 2
Python files which are not part of the build.

How reproducible:
rpmbuild -bb libevent.spec
  
Actual results:
RPM build errors:
    File not found:
/var/tmp/libevent-1.3b-1-root-rpmbuilder/usr/bin/event_rpcgen.pyc
    File not found:
/var/tmp/libevent-1.3b-1-root-rpmbuilder/usr/bin/event_rpcgen.pyo


Expected results:
Completely build libevent and libevent-devel rpms.
Comment 1 Bug Zapper 2008-04-04 07:00:29 EDT
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.

If this bug still exists in rawhide, please change the version back to
rawhide.
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)

Thanks for your help and we apologize for the interruption.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

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