From 8d240f3e56a7c9906894d521ea90f0167aba3b1f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dylan=20A=C3=AFssi?= <dylan.aissi@collabora.com> Date: Tue, 29 Oct 2024 09:47:40 +0100 Subject: [PATCH] Clarify how to trigger rebuild of packages in case of last minute changes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The effect is the same as removing rebuild="local", but it removes doubt about default OBS behavior. See: https://openbuildservice.org/help/manuals/obs-user-guide/cha-obs-build-scheduling-and-dispatching#id-1.2.10.14.5.7 Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com> --- content/guides/maintenance/apertis_release_process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/guides/maintenance/apertis_release_process.md b/content/guides/maintenance/apertis_release_process.md index 6bd3fcf1..a0983753 100644 --- a/content/guides/maintenance/apertis_release_process.md +++ b/content/guides/maintenance/apertis_release_process.md @@ -251,7 +251,7 @@ Some notes about the `Archive Rebuild` task - Once all packages have been successfully built, delete `rebuild` repositories. * Never trigger an archive wide rebuild on the primary `default` repositories. * In case of last minute changes in a package which could trigger dependencies issues, it is possible - to trigger the rebuild of packages in the dependency chain by removing rebuild="local". This will + to trigger the rebuild of packages in the dependency chain by setting `rebuild="transitive"`. This will instruct OBS to compute the list of packages that depend on new version of packages and schedule a rebuild of them. -- GitLab