https://bugzilla.redhat.com/show_bug.cgi?id=1750506 --- Comment #2 from Philip Kovacs <pkdevel@xxxxxxxxx> --- Can you issue a release on your github instead of using git commit hashes in the spec? Just create an annotated tag then issue a release tarball, e.g. hasciicam-1.1.2.tar.bz2 (or whatevcer version you use), along with sha and md5 checksums? Then come back here and use a conventional, release-oriented spec instead of a git commit hash spec. The latter implies a very active project and this project is very old and dead. On git hub, create an annotated tag and sign it with your gpg key. Upload the public gpg key to github so that the tag will appear as "verified" 1. Create gpg key pair 2. Upload public key to github 3. git tag -a -s -m "Release of vX.Y.Z" 4. Issue a release, e.g. hasciicam-1.1.2.tar.bz2 5. Display sha1sum hasciicam-1.1.2.tar.bz2 6. Display md5sum hasciicam-1.1.2.tar.bz2 7. Rewrite the rpm spec and remove all git commit features, use release syntax instead. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
