On Wed, 2020-04-08 at 11:39 +0200, Miro Hrončok wrote: > On 08. 04. 20 11:33, Tomas Tomecek wrote: > > > My questions are > > > * How to manage a RPM spec file on the upstream repository, > > > synchronizing it with Fedora rawhide's one. > > Ideally, you'd maintain the spec upstream and packit will copy [1] > > it > > for you when you perform releases. > > Once again I would like to point out that the canonical source of the > spec files > in Fedora is the Fedora git. Copying upstream specfiles to Fedora via > automation > and saying "ideally, you'd maintain the spec upstream" goes against > this principle. > > https://docs.fedoraproject.org/en-US/packaging-guidelines/#_spec_maintenanc As someone who also maintains the code for multiple packages, I say tough luck. The workflow for keeping upstream changes buildable (and having the ability to test the changes) and downstream package specification in sync with said changes could not be worse currently. Packit solves that for me *and* gives me the ability to pull in whatever was done downstream. -- Ernestas Kulik Software Engineer Base Operating Systems - Core Services - ABRT Red Hat Czech, s.r.o. _______________________________________________ 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
