Can confirm this bug here, and an updated patch fixes this.
See: https://bugzilla.redhat.com/show_bug.cgi?id=2090926 And: https://github.com/logrotate/logrotate/commit/31cf1099ab8514dfcae5a980bc77352edd5292f8 Suggest at the very least, this is updated in Debian for the next point release. This is a very misleading error message as it stands. Very.
