Richard Grainger kirjoitti 8.6.2018 klo 11.32:
On Thu, Jun 7, 2018 at 6:27 PM, Anssi Johansson <epel@xxxxxxxxx> wrote:
Is it considered a bug if you cannot build an EPEL package with the
current point release of CentOS or is it not? My understanding is that
older point releases are not supported or is that incorrect?
So this is a FTBFS bug (fails to build from source). The package
maintainer will need to address this issue eventually, for example when
the package needs to be rebuilt to fix some other bug. In this view the
bug is useful as a "heads up" that there is something to take into account.
I also wonder about the "high" priority of your bug. Why do you need to
compile the rpm yourself? Is "yum install dbus-c++-devel" not possible?
Well...I just need to...for my own reasons. The issue is high priority
to me, but I won't be offended if the priority is lowered by an admin
on bugzilla.
See, the reason I asked about this is that I would like to know what you
are really trying to achieve. This would help us to give you the best
assistance for moving forward.
Not knowing the details -- if you are not concerned about backwards
compatibility and just want to rebuild dbus-c++ for your own use, I
would suggest getting the latest SRPM for dbus-c++, getting the latest
bleeding edge version from
https://sourceforge.net/projects/dbus-cplusplus/ and modifying the
dbus-c++ spec file to reference the new tarball and updating the version
identifier in the spec file accordingly.
If you need to use the same 0.5.0 version as is currently in EPEL, you
may need to set up a separate 7.0.1406 (or perhaps something slightly
newer) build environment for this package.
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx/message/QQTJBGVSCG4EW6CLS32ZQGY43CJLXNCS/
