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
Bug 1556574 - log4c: FTBFS in F28
Summary: log4c: FTBFS in F28
Alias: None
Product: Fedora
Classification: Fedora
Component: log4c
Version: 28
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: František Dvořák
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F28FTBFS
TreeView+ depends on / blocked
Reported: 2018-03-15 00:09 UTC by Fedora Release Engineering
Modified: 2018-07-09 07:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-07-09 06:50:51 UTC
Type: ---

Attachments (Terms of Use)

Description Fedora Release Engineering 2018-03-15 00:09:34 UTC
Your package log4c failed to build from source in current F28.

For details on mass rebuild see

Comment 1 Zbigniew Jędrzejewski-Szmek 2018-07-09 04:06:40 UTC
Dear Maintainer,

your package has not been built successfully in F28. Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. Following the latest policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks.


Comment 2 František Dvořák 2018-07-09 06:50:51 UTC
It has been build successfully later. (I think there were problem with doxygen+latex BR at the time of the mass rebuild)

Comment 3 Zbigniew Jędrzejewski-Szmek 2018-07-09 07:13:26 UTC
Thanks for the info.

My script didn't close this bug. Although lists log4c-1.2.4-14.fc28 (built by me :P ), but koji -q latest-build f28-build log4c and koji -q latest-build f29-build log4c both return log4c-1.2.4-10.fc26. Oh, log4c-1.2.4-14.fc28 is only tagged into 'trashcan'. Maybe my fault, maybe not, doesn't matter now.

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