[syslog-ng] [Bug 185] Use upstream ivykis (>= 0.30) instead of a fork

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=185





--- Comment #10 from Jose Oliveira <jpo at di.uminho.pt>  2012-07-01 20:24:03 ---
(In reply to comment #9)
> (In reply to comment #8)
> > I forgot to mention that I'm using ivykis 0.30.
> 
> You could be hitting the iv_work deadlock issue in 0.30 that will be
> fixed in 0.31.  I'll release 0.31 shortly.
> 

Yep. Applying the ivykis patch 
https://github.com/buytenh/ivykis/commit/38d7359103ab988cc4a7b8089b81a455c5a69145
against the 0.30 tarball fixed the problem.

SRPMs:
ivykis-0.30-0.3.fc17.src.rpm
    ----------
    ivykis-0.30.tar.gz
    ivykis-0.31-deadlock-38d73591.patch
    ivykis.spec
    ----------
syslog-ng-3.3.6-0.1.2.fc17.src.rpm
    ----------
    syslog-ng-3.2.5-tests-functional-control.py.patch
    syslog-ng-3.3.5-20120701-v3.3.5-30-g9020.tar.gz
    syslog-ng-3.3.6-fix-core-dumps-in-some-tests.patch
    syslog-ng-3.3.6-syslog-ng.service.patch
    syslog-ng-3.3.6-tests-functional-sql-test.patch
    syslog-ng.conf
    syslog-ng.logrotate
    syslog-ng.spec
    ----------

Build logs and binary RPMS:
http://um-pe09-2.di.uminho.pt/fedora/build.logs/


We just need to bump the ivykis requirement to 0.31 :)


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.