Bug 1257681 - nm-version.h: #include glib.h, but NetworkManager.pc has no dependency on glib-2.0
nm-version.h: #include glib.h, but NetworkManager.pc has no dependency on gli...
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Lubomir Rintel
Fedora Extras Quality Assurance
: Patch, Upstream
Depends On:
  Show dependency treegraph
Reported: 2015-08-27 12:18 EDT by Rex Dieter
Modified: 2016-07-19 13:41 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 13:41:36 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add Requires.private: glib-2.0 (813 bytes, application/mbox)
2015-08-27 12:18 EDT, Rex Dieter
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 754186 None None None Never

  None (edit)
Description Rex Dieter 2015-08-27 12:18:09 EDT
Created attachment 1067829 [details]
Add Requires.private: glib-2.0

Per upstream bug,

Since commit,

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 13:41:36 EDT
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

Thank you for reporting this bug and we are sorry it could not be fixed.

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