https://bugzilla.redhat.com/show_bug.cgi?id=1750506
--- Comment #4 from Alessio <alciregi(a)gmail.com> ---
(In reply to Philip Kovacs from comment #2)
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.
The point is, as you have seen, that I'm not the developer/maintainer of this
software. And I'm not the owner of such git repository.
This project is very old, true, but it still works, and it looks that the
developer replies to the issues.
Let's see what upstream says.
Thank you.
--
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