https://bugzilla.redhat.com/show_bug.cgi?id=2130607 --- Comment #18 from Sébastien Le Roux <sebastien.leroux@xxxxxxxxxxxxxxxx> --- Hello, so here is my first successful Kojji build: https://koji.fedoraproject.org/koji/taskinfo?taskID=93011742 I had to rename the git repo in: https://github.com/Slookeur/atomes (also rename the 'Atomes' repo in 'Atomes-codeblocks' to keep my things clear) Builds were failing, and likely to fail in the future, when creating a release the archive were in the format specified in the spec file, but after extracting they were in a format unspecified in the spec file, if that is only possible, ex: %global upname Atomes-GNU Source0: https://github.com/Slookeur/%{upname}/archive/refs/tags/v%{version}.tar.gz Download archive: v1.1.7.tar.gz Extracted folder: Atomes-GNU-v1.1.7 And builders are looking for %{name}-${version} And I am not sure where to, if only it is possible, to correct it. And now the spec file looks like: Source0: https://github.com/Slookeur/%{name}/archive/refs/tags/v%{version}.tar.gz I will take some time to work on the doc, because this Koji build thing is so unclear by reading it ... it really did not help me to grasp the meaning behind all this ... now I am starting to understand ;-) Also correct the release number data, and will take car to increment this number in the future. -- 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=2130607 _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue