Hi Sergio, we have a full example in our docs: https://packit.dev/docs/fedora-releases-guide#full-example or you can check the configuration of packages that have Packit set up, e.g. https://src.fedoraproject.org/rpms/qownnotes/blob/rawhide/f/.packit.yaml or https://src.fedoraproject.org/rpms/micropipenv/blob/rawhide/f/.packit.yaml (you can find more usages from our dashboard: https://dashboard.packit.dev/jobs/pull-from-upstreams).
You could try a similar setup and test it from a dist-git pull request as described here: https://packit.dev/docs/fedora-releases-guide#first-setup. If you would like to further discuss your setup or you need more help, feel free to ask or reach out directly on #packit:fedora.im <https://chat.fedoraproject.org/#/room/#packit:fedora.im>. Laura On Wed, Nov 15, 2023 at 12:02 AM Sérgio Basto <ser...@serjux.com> wrote: > Hi, > > have we an example working ? > > I'd like had packit > for https://src.fedoraproject.org/rpms/libphonenumber > > Upstream Release Monitoring report here: > https://bugzilla.redhat.com/show_bug.cgi?id=2237976 > > > I'd like have the pull request , koji_build and bohi update > > > Thank you, > > > > > On Fri, 2023-09-15 at 09:22 +0200, Laura Barcziova wrote: > > If you're a Fedora package maintainer, we've got an exciting > > automation solution for you! > > > > At the beginning of the year, we announced a new feature called > > pull_from_upstream that eases the process of bringing upstream > > releases into Fedora. This feature can be easily configured directly > > in the dist-git repository without access to the upstream (as opposed > > to our previously introduced automation). It is most suitable for > > simple packages with straightforward update processes (e.g. without > > patches, or need to build in side tags). > > > > Our automation works on top of the Upstream Release Monitoring [1], > > and here's how to set it up: > > > > 1. Enable Upstream Release Monitoring for your Fedora package: set > > the mapping of the project in Anitya and in the left column in > > https://src.fedoraproject.org/rpms/$YourPackage, change Monitoring > > status to Monitoring. > > 2. Add the Packit configuration with the pull_from_upstream job to > > your dist-git repository (see example > > https://packit.dev/docs/configuration/downstream/pull_from_upstream#e > > xample). > > Once set up, here's how it works: > > * Upstream Release Monitoring creates a Bugzilla bug when new > > upstream versions are detected. > > * As a reaction to that, Packit: > > - automatically uploads the upstream archive to the lookaside > > cache, > > - creates dist-git pull request(s) at > > https://src.fedoraproject.org/ with all the necessary changes, like > > updates to the specfile and sources. > > If you are interested in this, read the previously published full > > post with the details of the setup here: > > https://packit.dev/posts/pull-from-upstream. Since the publication of > > this post, many users have adopted this feature and provided valuable > > feedback, allowing us to enhance the UX. We're now excited to assist > > you in automating the process as well! > > > > In addition to creating pull requests in dist-git, Packit can also > > automate Koji builds and Bodhi updates: > > * https://packit.dev/docs/configuration/downstream/koji_build > > * https://packit.dev/docs/configuration/downstream/bodhi_update > > > > For complete automation documentation, don't miss our comprehensive > > Fedora release guide at: https://packit.dev/docs/fedora-releases- > > guide. It contains all the essential information and setup tips. > > > > For any questions, feel free to contact us: > > https://packit.dev/#contact. > > > > Best regards, > > > > Packit team! > > > > [1] https://docs.fedoraproject.org/en-US/package- > > maintainers/Upstream_Release_Monitoring/ > > _______________________________________________ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > 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@lists.fedoraproje > > ct.org > > Do not reply to spam, report it: https://pagure.io/fedora- > > infrastructure/new_issue > > -- > Sérgio M. B. > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
