Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 735176 - Rebuild of koffice fails
Summary: Rebuild of koffice fails
Keywords:
Status: CLOSED DUPLICATE of bug 736659
Alias: None
Product: Fedora
Classification: Fedora
Component: koffice
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-01 17:26 UTC by Marek Kašík
Modified: 2011-09-14 17:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-14 17:17:28 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
logs (58.75 KB, application/x-bzip)
2011-09-01 17:26 UTC, Marek Kašík 		no flags Details
View All

Description Marek Kašík 2011-09-01 17:26:12 UTC 
Created attachment 521063 [details]
logs

Description of problem:
Rebuild of koffice fails. I wanted to rebuild it because of new poppler but this is not the reason of the fail. It fails if I do scratch build in koji with the current version of koffice and poppler (which previously worked).


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


How reproducible:
always


Steps to Reproduce:
1. fedpkg srpm
2. koji build --scratch f16 koffice-2.3.3-9.fc16.src.rpm
  

Actual results:
build fails with logs attached


Expected results:
build succeed


Additional info:
see http://koji.fedoraproject.org/koji/taskinfo?taskID=3318878
Comment 1 Marek Kašík 2011-09-01 17:28:45 UTC 
(the version is the koffice-2.3.3-9, not koffice-2.3.3-4 (a typo))
Comment 2 Rex Dieter 2011-09-14 17:17:28 UTC 

*** This bug has been marked as a duplicate of bug 736659 ***
Note You need to log in before you can comment on or make changes to this bug.