Bug 477728

Summary: changelog does not populate when making an SRPM
Product: [Community] Publican Reporter: eric <eric>
Component: publicanAssignee: Jeff Fearn 🐞 <jfearn>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 1.6CC: jfearn, mail, mmcallis, publican-list
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: 0.40 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-05 03:42:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 476471    

Description eric@christensenplace.us 2008-12-23 04:19:17 UTC
Description of problem: I have data inside the Revision_History.xml file but it is not being incorporated into the SPEC or RPM files when I'm building them.  This is makes rpmlint fail.

Version-Release number of selected component (if applicable): publican-0.39-0.fc10

How reproducible: Always.

Steps to Reproduce:
1. Create SRPM
2. Use rpmbuild --rebuild to create RPM
3. run rpmlint
Actual results: fedora-Linux_Security_Guide-10-en-US.noarch: E: no-changelogname-tag

Expected results: change log is included.

Additional info: 'xsltproc /usr/share/publican/xsl/changelog.xsl en-US/Revision_History.xml' produces an entry properly

Comment 1 Jeff Fearn 🐞 2009-01-05 03:42:59 UTC
Fixed pulling in of change log.

Comment 2 Fedora Update System 2009-01-16 07:40:33 UTC
publican-fedora-0.17-0.fc10,publican-0.40-0.fc10 has been submitted as an update for Fedora 10.

Comment 3 Fedora Update System 2009-01-16 07:43:09 UTC
publican-fedora-0.17-0.fc9,publican-0.40-0.fc9 has been submitted as an update for Fedora 9.

Comment 4 Fedora Update System 2009-01-21 21:32:47 UTC
publican-fedora-0.17-0.fc10, publican-0.40-0.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.