On 06/17/2011 10:45 PM, Jose Pedro Oliveira wrote:
On 2011-06-17 22:30, JP Vossen wrote:
I'm trying to get the EPEL6 syslog-ng-3.2.4-1.el6.src.rpm [1] to rpmbuild on CentOS-5 (eventlog-0.2.12-1.el6.src.rpm worked fine). I'm
FYI: You already have eventlog-0.2.12-1 in the EPEL5 stable repositories.
Oh thanks, I didn't even think to look because the target machines don't use EPEL and I'll need to rebuild anyway for policy reasons. ...
First, I had to comment out "BuildRequires: tcp_wrappers-devel" since that does not exist in CentOS-5. I am assuming/hoping that that's simply because the packages were split in RHEL6.
tcp_wrappers in RHEL 5 is still monolithic: just drop the "-devel" substring from the build requirement name. See also: https://bugzilla.redhat.com/show_bug.cgi?id=705486
Duh, that's a better idea. ...
[...] Assertion strcmp(name, dyn_name) == 0 failed at line 69 FAIL: test_nvtable [...] ...
I still haven't found the time to look into the test failure (low priority item in my todo list) but maybe someone from Balabit could ;)
So that's a known issue that is not a problem? RHEL5 only, or 6 too? If 6, how does the rpm even build with that spec file?
You should be aware that you will be plagued by at least two more problems by building syslog-ng for EPEL5 using the EPEL6 specfile: a logrotate related problem and a nasty macro expansion that causes the pidfile to be created in the wrong directory.
OK, thanks for the head's up, I'll look for those.
Feel free to create a ticket against the EPEL5 syslog-ng package [1] requesting the update to version 3.2.4 and I'll keep up to date.
Oh I like that idea even more. I'll do that tomorrow. Thanks for the quick reply! JP