Hi Jun, thanks for reaching out! I'd suggest CCing someone from our team in future to make sure we see your message. It's good though you started the discussion on fedora-devel. On Thu, Apr 2, 2020 at 8:54 PM Jun Aruga <jaruga@xxxxxxxxxx> wrote: > > I am considering using Packit-as-a-Service [1] for an upstream > project, as the maintainer of the project suggested managing the RPM > spec file on the upstream's repository in Github. > > Could you tell me some case studies of the upstream project using > Packit-as-a-Service? > I know rebase-helper [2] is using it. There is a bunch of projects who are already integrated with packit-service at this point: * https://github.com/beaker-project/restraint/blob/master/.packit.yaml * https://github.com/abrt/faf/blob/master/.packit.yml * https://github.com/containerbuildsystem/atomic-reactor/blob/master/.packit.yaml * https://github.com/fedora-modularity/libmodulemd/blob/master/.packit.yml * https://github.com/packit-service/ogr/blob/master/.packit.yaml (and us obviously) * ... > What I want to do is > * to check the RPM spec file at the pull-request timing on GitHub, > building it on specified build targets (rawhide or fNN). This the basic use case which packit is helping to solve. > 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. > For example, in case of rawhide, the RPM spec file's release version > is sometimes automatically updated. > I am thinking of managing the RPM spec file on the upstream without > %changelog to synchronize it easily. Packit does not sync changelogs b/w the two places because they tend to differ. As for release number -- those can get out of sync. Luckily everything is git so changes can be seen easily and reverted or updated. > * Is it possible to manage the RPM spec file including %PatchN and the > patch file on the upstream repository? It is, just include the patch file in the repo. Please let us know if you need any help with setting everything up. [1] https://packit.dev/docs/configuration/#supported-jobs (propose_downstream job) _______________________________________________ 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
