https://bugzilla.redhat.com/show_bug.cgi?id=2048456
--- Comment #16 from Parag AN(पराग) <panemade(a)gmail.com> ---
Ah, this is not the way any software upstream should do. You need to maintain
proper commits.
I request to first commit your font development related files in upstream. Tag
them for initial release.
Release tarball and use it for Fedora packaging.
e.g. See this font project
https://gitlab.com/rit-fonts/MeeraNew/-/tree/main
how they are maintaining their development history.
Then see how when they want to release they are tagging
https://gitlab.com/rit-fonts/MeeraNew/-/tags
At least I will ask for proper tarball release. You are keep updating tarball
for every fix I suggested.
Remember once your package is in Fedora and you need to fix minor thing and you
do the same thing, its problem in Fedora.
Fedora packaging store sha512sum of your tarball and it MUST be same whenever
someone verifies it.
Once released tarball, any fix you should bump the tarball version and release
it.
I really think you should take some time to learn how to host a project and
release a tarball.
If the forge macros are not working for you then you can use
https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/#_git...
but again you need to provide git commit id or tag.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2048456