Proposing keeping multiple versions of the same package in the updates repo

Hi, We run a diverse fleet of Linux laptops and desktops (at Facebook), and sometimes there are regressions that affect some of our fleet but not others. To pick the latest example: - pulseaudio 1.3.99.1 (both -1 and -2) breaks Bluetooth support on a Dell XPS 15:

Re: Bodhi 5.2.0 deployed in production.

On Mon, 23 Mar 2020 at 15:33, Clement Verna wrote: > > > On Mon, 23 Mar 2020 at 10:39, Igor Gnatenko < > ignatenkobr...@fedoraproject.org> wrote: > >> Hello Clement, >> >> On Mon, Mar 23, 2020 at 10:30 AM Clement Verna >> wrote: >> > >> > Hi all, >> > >> > I have just deployed Bodhi 5.2.0 in

[PATCH] s3-mirror: try to set 'max-age' cache opt for repomd.xml files

--- roles/s3-mirror/files/s3.sh | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/roles/s3-mirror/files/s3.sh b/roles/s3-mirror/files/s3.sh index 70046d21f..c157b0cdb 100644 --- a/roles/s3-mirror/files/s3.sh +++ b/roles/s3-mirror/files/s3.sh @@ -93,8 +93,9 @@ excludes=(

Re: Bodhi 5.2.0 deployed in production.

On Mon, 23 Mar 2020 at 10:39, Igor Gnatenko < ignatenkobr...@fedoraproject.org> wrote: > Hello Clement, > > On Mon, Mar 23, 2020 at 10:30 AM Clement Verna > wrote: > > > > Hi all, > > > > I have just deployed Bodhi 5.2.0 in production. This version should > improve the performance of updates

Re: Bodhi 5.2.0 deployed in production.

Hello Clement, On Mon, Mar 23, 2020 at 10:30 AM Clement Verna wrote: > > Hi all, > > I have just deployed Bodhi 5.2.0 in production. This version should improve > the performance of updates creation since the expansive task of tagging > builds in koji has been moved to an async process using a

Bodhi 5.2.0 deployed in production.

Hi all, I have just deployed Bodhi 5.2.0 in production. This version should improve the performance of updates creation since the expansive task of tagging builds in koji has been moved to an async process using a celery workers. Also this version will also allow the use of side-tags to all

[PATCH 2/2] s3-mirror: delay the `sync --delete` a bit

So the running DNF processes can finish transaction. --- roles/s3-mirror/files/s3.sh | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/roles/s3-mirror/files/s3.sh b/roles/s3-mirror/files/s3.sh index 4b300e370..70046d21f 100644 --- a/roles/s3-mirror/files/s3.sh +++

[PATCH 1/2] s3-mirror: only skip repomd.xml files in first sync run

.. and include _only_ those in second sync run. --- roles/s3-mirror/files/s3.sh | 17 + 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/roles/s3-mirror/files/s3.sh b/roles/s3-mirror/files/s3.sh index 163e3dc36..4b300e370 100644 --- a/roles/s3-mirror/files/s3.sh +++