Bug 1257681

Summary: nm-version.h: #include glib.h, but NetworkManager.pc has no dependency on glib-2.0
Product: [Fedora] Fedora Reporter: Rex Dieter <rdieter>
Component: NetworkManagerAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: dcbw, lkundrak, psimerda
Target Milestone: ---Keywords: Patch, Upstream
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 17:41:36 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:
Embargoed:
Attachments:
Description Flags
Add Requires.private: glib-2.0 none

Description Rex Dieter 2015-08-27 16:18:09 UTC 
Created attachment 1067829 [details]
Add Requires.private: glib-2.0

Per upstream bug,
https://bugzilla.gnome.org/show_bug.cgi?id=754186

Since commit,
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/libnm-core/nm-version.h.in?h=nm-1-0&id=6f616d4c4b04d5478f60d0311317bc84c5459ea4

nm-version.h has
#include <glib.h>

So, NetworkManager.pc should pull glib-2.0 as a dependency, I'd suggest adding:
Requires.private: glib-2.0

(Only noticed when some kde-related fedora builds were failing)
Comment 1 Fedora End Of Life 2016-07-19 17:41:36 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.