Martin Gansser venit, vidit, dixit 2024-09-05 13:20:16: > First i converting the specfile with: > > [martin@fc40 SPECS]$ rpmautospec convert pyliblo3.spec > Converted to %autorelease and %autochangelog. > > and then I create the src.rpm file with > > [martin@fc40 SPECS]$ rpmbuild -bs pyliblo3.spec > Einstellung SOURCE_DATE_EPOCH=1725494400 > Created: /home/martin/rpmbuild/SRPMS/pyliblo3-0.16.2-1.fc40.src.rpm > > but why is the src.rpm not created with the git extension ? > pyliblo3-0.16.2-0.5.git91d1781.fc40.src.rpm > > I would then like to import these with: > fedpkg import ~/rpmbuild/SRPMS/pyliblo3-0.16.2-0.5.git91d1781.fc40.src.rpm So I think the problem is more in the versionning itself. First of all: Where does 0.16.2 come from? The latest upstream tag I see is 0.12. Important for autospec: You seem to be using the tradiotonal versionning scheme which mixes version and release (part of version in the release field). This cannot work with autorelease, as you found out. Please see https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/ for the current scheme. It includes examples for upstream version of the type "named upstream release plus snapshot from git". You'd have to read "release" as "released upstream version", not as something that goes into our release field. Cheers Michael -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
