Re: [Heads up]: python-PyGithub major update coming to rawhide soon

2024-07-23 Thread Sandro via devel
On 23-07-2024 20:30, Sandro via devel wrote: PyGithub will be updated to 2.3.0 in rawhide soon. This is a major update and according to upstream's changelog [1] it comes with breaking changes. The first update containing breaking changes is 1.59.0. We are currently on 1.58.2. Please take

[Heads up]: python-PyGithub major update coming to rawhide soon

2024-07-23 Thread Sandro via devel
Hi, PyGithub will be updated to 2.3.0 in rawhide soon. This is a major update and according to upstream's changelog [1] it comes with breaking changes. The first update containing breaking changes is 1.59.0. We are currently on 1.58.2. Please take a look yourself if it affects your package.

Re: The future Fedora Copr "rolling" chroot cleanup policy

2024-07-15 Thread Sandro via devel
On 15-07-2024 10:24, Pavel Raiskup wrote: TL;DR: We plan to start monitoring build activity in Copr projects. If no builds appear for a long time in these "rolling" chroots (such as Fedora Rawhide), we'll disable such chroots, preserve the built results for a while, and then delete them if no

Re: PR for rebuild and autochangelog

2024-07-09 Thread Sandro via devel
On 09-07-2024 17:22, David Bold wrote: Sandro wrote: On 09-07-2024 17:01, David Bold wrote: Is it possible to have a PR without any code changes? Is there an alternative, recommended way to ask for rebuilds? Specifically in the case of %autorelease, you can bump the release with an empty

Re: PR for rebuild and autochangelog

2024-07-09 Thread Sandro via devel
On 09-07-2024 17:01, David Bold wrote: Is it possible to have a PR without any code changes? Is there an alternative, recommended way to ask for rebuilds? Specifically in the case of %autorelease, you can bump the release with an empty commit: git commit --allow-empty -m 'Rebuild for ...'