On Fri, May 6, 2022 at 5:54 PM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
On 06. 05. 22 17:37, Frantisek Lachman wrote:
The problem is I have not explicitly opted in yet I am afraid this will block
my work. Before a more robust solution is found, please at least provide me a
way how I can temporarily disable this for python-ogr and packit in ~1 month
when we plan to do the Python 3.11 rebuilds.
>> Here is a list of mentioned solutions sorted from the less-fragile to the most
>> (IMHO).
>>
>> 1. Automation only happens when maintainer explicitly starts it
>> 2. Automation only happens when a packit PR was merged*
>> 3. Automation only happens for non-provenpackagers
>> 4. Automation happens on every push (current way)
>>
>> * this could be documented in the PR initial comment
>
> Thanks for the points, I've created an upstream issue on our issue
> tracker for that: https://github.com/packit/packit-service/issues/1490
Ack, will subscribe.
After talking to Franta, we will try to resolve this next week and deploy to production on May 17th: our usual schedule.
Hope that works for you,
Tomas
_______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
