https://bugzilla.redhat.com/show_bug.cgi?id=2048456 --- Comment #16 from Parag AN(पराग) <panemade@xxxxxxxxx> --- 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_hosting_services 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. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2048456 _______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
