Bug 1318967

Summary: provide burp-1.4.40 to EPEL5
Product: [Fedora] Fedora EPEL Reporter: yopito <pierre.bourgin>
Component: burpAssignee: Andrew Niemantsverdriet <andrewniemants>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el5CC: andrewniemants, i, pierre.bourgin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-06 10:03:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
burp.spec patch for epel5 building none

Description yopito 2016-03-18 09:34:22 UTC 
Created attachment 1137732 [details]
burp.spec patch for epel5 building

Description of problem:
burp 1.4.40 is not provided for EPEL5. 
With few modifications, it can be provided.
I was able to build it in my COPR environment.

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

How reproducible:
always

Steps to Reproduce:
1. yum search burp\*
2. 
3.

Actual results:


Expected results:
burp-client-1.4.40
burp-server-1.4.40


Additional info:
1. wait for yajl-devel to be provided by EPEL5 (see bug #1318933)
2. update el5 branch of http://pkgs.fedoraproject.org/cgit/rpms/burp.git/ with the content of master branch
3. apply patch on burp.spec provided as attachment

my COPR environment: https://copr.fedorainfracloud.org/coprs/yopito/burp2/
Comment 1 Fedora End Of Life 2017-04-06 10:03:53 UTC 
Fedora EPEL 5 changed to end-of-life (EOL) status on 2017-03-31. Fedora EPEL 5
is no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora
or Fedora EPEL, please feel free to reopen this bug against that version. If
you are unable to reopen this bug, please file a new report against the current
release. If you experience problems, please add a comment to this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.