[BUG] RPM package broken on certain rpm versions

[tisoft]

Describe the bug
The mirth RPM is build with Install4J version 8.x. This version creates rpm files, that can't be read by certain rpm versions (rpm-software-management/rpm#1635)

To Reproduce
Steps to reproduce the behavior:

docker run --rm -it fedora:33
curl -O https://s3.amazonaws.com/downloads.mirthcorp.com/connect/3.12.0.b2650/mirthconnect-3.12.0.b2650-linux.rpm
rpm -qip mirthconnect-3.12.0.b2650-linux.rpm

Expected behavior
The RPM information should be displayed:

Name        : mirthconnect
Version     : 3.12.0.b2650
Release     : 1
Architecture: i386
Install Date: (not installed)
Group       : unsorted
Size        : 286909761

Signature   : (none)
Source RPM  : (none)
Build Date  : Thu Sep  2 17:01:34 2021
Build Host  : (none)
Relocations : /opt/mirthconnect 
Vendor      : NextGen Corporation
URL         : http://www.nextgen.com
Summary     : (none)
Description :
Mirth Connect

Actual behavior
An error message is displayed:

error: mirthconnect-3.12.0.b2650-linux.rpm: invalid signature tag Archivesize (1046)
error: mirthconnect-3.12.0.b2650-linux.rpm: not an rpm package (or package manifest)

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• OS: Fedora 33, openSUSE Leap 15.3, probably others
• Connect Version: All Versions

Workaround(s)
Up-/Downgrade to a rpm version, not containing this regression, which may not be possible, depending on distribution used.

Additional context
Updating to Install4J 9.0.2 will fix the problem.