Comments
jvymazal
I would not like to remove include statement by default for compatibility resons, however I filed #1608304.
~ should have been relaced simply by the word "stop" years ago
Unfortunately this is caused by included config which is controlled by systemd
LGTM
karma
LGTM
karma
LGTM
BZ#1505191 libfastjson-v0.99.7 is available
karma
works for me
BZ#1465894 rsyslog-8.29.0 is available
Test Case rsyslog
karma
Work for me as well
BZ#1465894 rsyslog-8.29.0 is available
Test Case rsyslog
karma
Works for me (tested with 8.27.0 rsyslog)
BZ#1462723 libfastjson-v0.99.6 is available
karma
Tested with 8.27.0 rsyslog and works for me
BZ#1462723 libfastjson-v0.99.6 is available
karma
BZ#1462723 libfastjson-v0.99.6 is available
Works here as well
BZ#1422542 Missing chdir call after chroot
BZ#1419625 Write new default config
BZ#1418720 Enable omkafka module for rsyslog
BZ#1379638 rsyslog does not start remote logging at boot
BZ#1426830 rsyslog-8.25.0 is available
Test Case rsyslog
karma
works
BZ#1343132 Dangling symlink /etc/systemd/system/syslog.service
works for me (x86_64)
BZ#1404209 Wrong BuildRequiers
BZ#720299 rsyslog-8.23.0 is available
@szydell, AFAIK fedora upstream monitoring which creates the "new-version available" BZ tickets works the way it creates it for first version newer then current and then leaves it that way until maintainer performs the rebase, so if I am not rebasing every version then the ticket summary can have older one.