@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.
This update has been submitted for testing by jvymazal.
This update test gating status has been changed to 'waiting'.
This update test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Please update this ticket. In the package and the #1716391 ticket, rsyslog is in version 8.1907.0.
[root@laPtak ~]# rsyslogd -version rsyslogd 8.1907.0 (aka 2019.07) compiled with: PLATFORM: x86_64-redhat-linux-gnu PLATFORM (lsb_release -d): FEATURE_REGEXP: Yes GSSAPI Kerberos 5 support: Yes FEATURE_DEBUG (debug build, slow code): No 32bit Atomic operations supported: Yes 64bit Atomic operations supported: Yes memory allocator: system default Runtime Instrumentation (slow code): No uuid support: Yes systemd support: Yes Config file: /etc/rsyslog.conf PID file: /var/run/rsyslogd.pid Number of Bits in RainerScript integers: 64
@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.
Works
This update has been submitted for stable by bodhi.
This update has been pushed to stable.