https://bugzilla.redhat.com/show_bug.cgi?id=2106611 --- Comment #17 from Fabio Valentini <decathorpe@xxxxxxxxx> --- (In reply to Stefano Brivio from comment #15) > I'm not actually using the {{{ git_dir_changelog }}} rpkg-utils macro, I > wrote a different one for this purpose, because git_dir_changelog would > report a line for every single upstream commit (with possibility of > editing), which clearly conflicts with packaging guidelines. If one day Copr > stops allowing macro usage altogether, I would rather call my macro (a > rather simple shell function) from the upstream Makefile, I guess. > > As to the unavailability on Fedora's build system, yes, I already planned > for that -- I would simply copy the spec file as processed by rpkg, and keep > it updated in Fedora's git. Note that the canonical location for the .spec file for a package is supposed to be the Fedora dist-git repository: https://docs.fedoraproject.org/en-US/packaging-guidelines/#_spec_maintenance_and_canonicity i.e. you are not allowed to override changes that are made to the Fedora spec file with things from upstream. -- 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=2106611 _______________________________________________ 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
