Re: Add a push update mechanism for https://release-monitoring.org/
We have the packit even recommended in the-new-hotness documentation (it's the application responsible for creating tickets in bugzilla when release-monitoring.org finds new version). https://the-new-hotness.readthedocs.io/en/stable/user-guide.html#opening-pull-requests-in-dist-git Michal On 28. 08. 23 18:19, Frantisek Lachman wrote: Hello, as Fabio has pointed out, you can use Packit to get your releases to Fedora via pull-requests. Packit supports both push and newly also pull workflow. (So you don't need to have access to the upstream repository because it gets the info about the new version from Release Monitoring.) Thanks to it being pull-request-based, there is a Fedora CI involved and you, as a maintainer, can see the build/test results and decide if this should go to Fedora or not. Plus, an automatic Koji build and Bodhi update is possible as well. It's easy to set up. Here is the documentation for the Fedora automation: https://packit.dev/docs/fedora-releases-guide#pull-from-upstream-job And don't be afraid to ask. We, as a Packit team, are happy to help. František Packit Product Owner..;) #packit:fedora.im (Element / Matrix) #packit:libera.chat (IRC) he...@packit.dev @pac...@fosstodon.org (Mastodon) On Mon, Aug 28, 2023 at 3:01 PM Sérgio Basto wrote: On Mon, 2023-08-28 at 13:52 +0100, Sérgio Basto wrote: On Mon, 2023-08-28 at 03:28 +, Ryan Bach via devel wrote: Faster updates are always as plus. Should this be under infrastructure list? Thoughts? if you got a scratch build completed in a bugzilla for example : https://bugzilla.redhat.com/show_bug.cgi?id=2231971 you may use my helper script update_from_bugzilla.sh `fedpkg clone package-foo; cd package-foo ; ../update_from_bugzilla.sh` forgot to add bugzilla number, so should be `fedpkg clone package-foo; cd package-foo ; ../update_from_bugzilla.sh 2231971` Thanks in advance for all the work done to make this distro great. ___ 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 -- 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 -- 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 ___ 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
Re: Add a push update mechanism for https://release-monitoring.org/
> On Mon, Aug 28, 2023 at 5:29 AM Ryan Bach via devel > > There's a problem with an approach like this: You need to check > *manually* that the new version builds and doesn't violate any of our > policies, for example, that it doesn't contain any prohibited items > (like new code or content that's under non-FOSS / non-commercial / > non-redistributable licenses). > > For projects where the people who are responsible for the upstream > project are the same people who maintain the Fedora package, this is > mostly a non-issue - and for these cases, there's Packit [0] (which I > think does what you are looking for). > > Fabio > > [0]: https://packit.dev I mean for anitya https://release-monitoring.org https://github.com/fedora-infra/anitya/issues ___ 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
Re: Add a push update mechanism for https://release-monitoring.org/
Hello, as Fabio has pointed out, you can use Packit to get your releases to Fedora via pull-requests. Packit supports both push and newly also pull workflow. (So you don't need to have access to the upstream repository because it gets the info about the new version from Release Monitoring.) Thanks to it being pull-request-based, there is a Fedora CI involved and you, as a maintainer, can see the build/test results and decide if this should go to Fedora or not. Plus, an automatic Koji build and Bodhi update is possible as well. It's easy to set up. Here is the documentation for the Fedora automation: https://packit.dev/docs/fedora-releases-guide#pull-from-upstream-job And don't be afraid to ask. We, as a Packit team, are happy to help. František Packit Product Owner..;) #packit:fedora.im (Element / Matrix) #packit:libera.chat (IRC) he...@packit.dev @pac...@fosstodon.org (Mastodon) On Mon, Aug 28, 2023 at 3:01 PM Sérgio Basto wrote: > > On Mon, 2023-08-28 at 13:52 +0100, Sérgio Basto wrote: > > On Mon, 2023-08-28 at 03:28 +, Ryan Bach via devel wrote: > > > Faster updates are always as plus. > > > > > > Should this be under infrastructure list? > > > > > > Thoughts? > > > > > > > if you got a scratch build completed in a bugzilla for example : > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2231971 > > > > you may use my helper script update_from_bugzilla.sh > > > > `fedpkg clone package-foo; cd package-foo ; > > ../update_from_bugzilla.sh` > > forgot to add bugzilla number, so should be > > `fedpkg clone package-foo; cd package-foo ; ../update_from_bugzilla.sh > 2231971` > > > > > > Thanks in advance for all the work done to make this distro great. > > > ___ > > > 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 > > > > -- > > 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 > > -- > 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
Re: Add a push update mechanism for https://release-monitoring.org/
On Mon, 2023-08-28 at 13:52 +0100, Sérgio Basto wrote: > On Mon, 2023-08-28 at 03:28 +, Ryan Bach via devel wrote: > > Faster updates are always as plus. > > > > Should this be under infrastructure list? > > > > Thoughts? > > > > if you got a scratch build completed in a bugzilla for example : > > https://bugzilla.redhat.com/show_bug.cgi?id=2231971 > > you may use my helper script update_from_bugzilla.sh > > `fedpkg clone package-foo; cd package-foo ; > ../update_from_bugzilla.sh` forgot to add bugzilla number, so should be `fedpkg clone package-foo; cd package-foo ; ../update_from_bugzilla.sh 2231971` > > > Thanks in advance for all the work done to make this distro great. > > ___ > > 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 > > -- > 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 -- 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
Re: Add a push update mechanism for https://release-monitoring.org/
On Mon, 2023-08-28 at 03:28 +, Ryan Bach via devel wrote: > Faster updates are always as plus. > > Should this be under infrastructure list? > > Thoughts? > if you got a scratch build completed in a bugzilla for example : https://bugzilla.redhat.com/show_bug.cgi?id=2231971 you may use my helper script update_from_bugzilla.sh `fedpkg clone package-foo; cd package-foo ; ../update_from_bugzilla.sh` > Thanks in advance for all the work done to make this distro great. > ___ > 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 -- 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
Re: Add a push update mechanism for https://release-monitoring.org/
On Mon, Aug 28, 2023 at 5:29 AM Ryan Bach via devel wrote: > > Faster updates are always as plus. There's a problem with an approach like this: You need to check *manually* that the new version builds and doesn't violate any of our policies, for example, that it doesn't contain any prohibited items (like new code or content that's under non-FOSS / non-commercial / non-redistributable licenses). For projects where the people who are responsible for the upstream project are the same people who maintain the Fedora package, this is mostly a non-issue - and for these cases, there's Packit [0] (which I think does what you are looking for). Fabio [0]: https://packit.dev ___ 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
Add a push update mechanism for https://release-monitoring.org/
Faster updates are always as plus. Should this be under infrastructure list? Thoughts? Thanks in advance for all the work done to make this distro great. ___ 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
