Recently, I tried to install AppImageLauncher using bluebuild.
Since they provide a rpm build, I tried to install it directly using the dnf module.
Unfortunately, I got an error at build time:
- package appimagelauncher-2.2.0-travis995~0f91801.x86_64 does not verify: no digest
And indeed, running rpm -qi appimagelauncher-2.2.0-travis995.0f91801.x86_64.rpm | head confirmed that the rpm file was not signed.
I could install it on a fedora machine with the --no-signature flag, or the more general --no-gpgcheck file (this also skips rpms that do not have metadata).
I think they are other rpm packages that do not have signature, so I think being able to specify this option for specific packages would be very useful.
For now, I installed it using the script module.
I consider contributing to the project if you think this is a useful feature.
Recently, I tried to install AppImageLauncher using bluebuild.
Since they provide a rpm build, I tried to install it directly using the dnf module.
Unfortunately, I got an error at build time:
And indeed, running
rpm -qi appimagelauncher-2.2.0-travis995.0f91801.x86_64.rpm | headconfirmed that the rpm file was not signed.I could install it on a fedora machine with the
--no-signatureflag, or the more general--no-gpgcheckfile (this also skips rpms that do not have metadata).I think they are other rpm packages that do not have signature, so I think being able to specify this option for specific packages would be very useful.
For now, I installed it using the
scriptmodule.I consider contributing to the project if you think this is a useful feature.