Hi Evan,

I think it can be done, yes. I will check it out.
We do not have many "Requires:" in the specfile, and I do not see any reason why we should not have them.

Peter, what do you think about it? Do you have any reason not to add "Requires:" fields to core and the modules?

Cheers,
Attila
From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> on behalf of Evan Rempel <erempel@uvic.ca>
Sent: Friday, February 4, 2022 9:41 PM
To: syslog-ng@lists.balabit.hu <syslog-ng@lists.balabit.hu>
Subject: [syslog-ng] syslog-ng 3.35.1-2.el7
 
CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.

The packaged syslog-ng RPM for RHEL7 from the stable copr repo

https://copr-be.cloud.fedoraproject.org/results/czanik/syslog-ng-stable

fails to have a dependency specified for glib library with a large enough version to satisfy the runtime requirements.

The syslog-ng package has a requirement listed of

"libglib-2.0.so.0()(64bit)"

but if there is an older glib2 package installed that satisfies this requirement syslog-ng will fail to start with an error

/usr/sbin/syslog-ng: symbol lookup error: /usr/lib64/libsyslog-ng-3.35.so.0: undefined symbol: g_ptr_array_find_with_equal_func


Can the package maintainer add a >= version specification to the requirements so that the install of syslog-ng will automatically update to a version of glib2 that works with syslog-ng?

-- 
Evan Rempel