Bug 1006169

Summary: Can't rebuild repository with sblim-sfcb-1.4.5-1.fc21
Product: [Fedora] Fedora Reporter: Jan Safranek <jsafrane>
Component: sblim-sfcbAssignee: Vitezslav Crhonek <vcrhonek>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 22CC: praveen_paladugu, srinivas_g_gowda, tsmetana, vcrhonek
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: 2016-07-19 19:27:07 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:

Description Jan Safranek 2013-09-10 07:02:34 UTC 
Version-Release number of selected component (if applicable):
sblim-sfcb-1.4.5-1.fc21

How reproducible:
always

Steps to Reproduce:
1. yum update

Actual results:
  Updating   : sblim-sfcb-1.4.5-1.fc21.x86_64
Sf format being used.
sfcbmof: symbol lookup error: /usr/lib64/sfcb/libsfcUtil.so.0: undefined symbol: newList
Failed compiling the MOF files.

Expected results:
Updated OK

Additional info:
Also "sfcbrepos -f" reports the same error.
Comment 1 Jaroslav Reznik 2015-03-03 15:03:11 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 2 Fedora End Of Life 2016-07-19 19:27:07 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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 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.