Red Hat Bugzilla – Bug 819209
Last modified: 2013-09-16 02:15:30 EDT
Description of problem:
This file is not provided.
Version-Release number of selected component (if applicable):
Don't really understand the sub-package splitting.
Installing libgearman-1.0 AND libgearman-1.0-devel workaround the problem.
This should be dependencies of libgearman-devel
Any news ?
Upstream split out the libgearman sources like that, so I packaged it (the older 1.0 library version) separately. Do you have any suggestion of doing it another way?
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Bumping to Rawhide to avoid auto-closing
Thanks for this bug. I'm not sure why pkgdb didn't re-assign this bug when the ownership changed... anyways, re-assigning manually now.
The latest version of libgearman-devel (1.1.8-4) provides the /usr/include/libgearman-1.0 directory and header files. Would you mind confirming that this is working for you? If so, we can close this bug.
Yes, new version is working.
Awesome! Thank you Remi. Closing.