https://bugzilla.redhat.com/show_bug.cgi?id=2037863 --- Comment #11 from Fabio Valentini <decathorpe@xxxxxxxxx> --- I would recommend only switching to use rpmautospec macros once you import the package into a dist-git repository. The macros make all kinds of assumptions that are just not broken or wrong outside a dist-git repo. As you have noticed, they don't work with classic "~/rpmbuild/{SOURCES,SRPMS,SPECS}" directory tree layout at all, and unless you work inside a git repository, the Release and changelog will always evaluate to their fallback values: rpm -E %autorelease 1.fc35 and rpm -E %autochangelog * Tue Jan 18 2022 John Doe <packager@xxxxxxxxxxx> - %{version}-%{release} - local build This is almost certainly not what you want. > What should I call the file in ~/rpmbuild/SOURCES/ so that it's included? Which file are you talking about? -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2037863 _______________________________________________ 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
