Red Hat Bugzilla – Bug 480347
Please build libgsasl for EPEL 5
Last modified: 2009-01-23 04:35:37 EST
Description of problem:
Please build libgsasl for EPEL 5.
The Spacewalk project is interested in moving from our own version of jabberd to something more standard, so we'd like to get jabberd to EPEL. However, jabberd BuildRequires libgsasl-devel. Therefore, we'd like to get libgsasl to EPEL.
Version-Release number of selected component (if applicable):
The one from F10, 0.2.29-1.
Please let me know, if you do not want to be the maintainer for the
libgsasl EPEL packages.
My only concern is that I know nothing about EPEL and it's policies about updates and such. So it's maybe better if someone who already maintains EPEL packages does this.
This package is very low maintenance for a year it's been only rebuilds for new versions.
I'll do it if nobody steps up.
(In reply to comment #1)
> My only concern is that I know nothing about EPEL and it's policies about
> updates and such.
The policies are here: https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies
The Digest is:
have a mostly stable set of packages that normally to not
change at all and only changes if there are good reasons
for it -- so no "hey, there is a new version, it builds,
let's ship it" mentality.
So it's a very low-change thing.
(In reply to comment #2)
> I'll do it if nobody steps up.
Ok. It will take some time. It should be ready by the end of the week.
libgsasl requires libntlm so I've built it for EPEL5.
As I remember from fedora7's plague a packages in plague are build against stable. Not sure about this.
So as I understand I have to wait about a month to get the package to stable and then build libgsasl.
Please clarify this for me.
Based on info found at
you should be able to ask for the package to be moved to EPEL repos faster via email to epel_signers-members AT fedoraproject DOT org.
My request to epel_signers was denied.
Well, we can push things to stable if there is a great need: Serious
bug fix or security issue, but I would be reluctant to push a new
package direct to stable.
I've checked with epel_signers and Dennis Gilmore says:
> In EPEL built packages are immediately available to the buildroot. as long as
> libgsasl is built you will be able to build against it. there is a short
> period while createrepo runs that it wont be available. but very quickly
> after being built it will be available. all packages will then sit in testing
> for a few weeks until the next stable push.
So if I understand it correctly, if you build libntlm, it should be immediately available in buildroot for libsasl to use, and if you build libgsasl, jabberd will be able to BuildRequire it (again, for build in testing). Which would be just fine. We do not really care that it will take some more time before the resulting jabberd gets to stable repo.
Can you verify that now that libntlm is built, you can build libgsasl as well?
1258 (libgsasl): Build on target fedora-5-epel succeeded.
Build logs may be found at http://buildsys.fedoraproject.org/logs/fedora-5-epel/1258-libgsasl-0.2.29-1.el5/
Ok. I'm closing this.