Hi,

Yeah, that's what I also assumed. But I just realized, that the driver part is a separate package: libdbi-drivers. I'll check if I can also add that one to my EPEL6 repo. If not I rather disable libdbi all together not to confuse people.
It's the first time that someone is missing it, so SQL destinations is not much in use...

Bye,

Peter Czanik (CzP) <peter.czanik@balabit.com>
Balabit / syslog-ng upstream
https://www.balabit.com/blog/author/peterczanik/
https://twitter.com/PCzanik

On Wed, Nov 16, 2016 at 9:31 AM, Fabien Wernli <wernli@in2p3.fr> wrote:
On Tue, Nov 15, 2016 at 04:39:41PM -0900, Glen Johnson wrote:
> It appears the syslog-ng38epel6 on COPR uses libdbi 0.9.0 from el7.  When
> attempting to install syslog-ng from here, on an CentOS 6 instance, and
> then install libdbi-dbd-mysql, yum is unable to find appropriate version of
> libdbi-dbd-mysql to install.  On el6, only libdbi 0.8.3 appears to be
> available, which yum does not think is compatible with libdbi 0.9.0.  Not
> sure how to use syslog-ng's mysql destination on CentOS/RHEL 6 due to
> this.  Any insight how to solve this, without creating a separate copr/obs
> build, would be appreciated !

the dependency is also available on COPR [1]

[1] https://copr.fedorainfracloud.org/coprs/czanik/syslog-ng38epel6/package/libdbi/

______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq