From 1df61b445b6ee763d6987f160c782b9c778208c5 Mon Sep 17 00:00:00 2001 From: Nitjsefnie Date: Thu, 22 Oct 2026 20:16:36 +0200 Subject: [PATCH 1/2] docs: warn about non-reproducible generated sources during release syncing Co-Authored-By: GPT-6.1 Sol Signed-off-by: Nitjsefnie --- docs/configuration/examples.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/configuration/examples.md b/docs/configuration/examples.md index 9fc50d84d3..02d191e50c 100644 --- a/docs/configuration/examples.md +++ b/docs/configuration/examples.md @@ -114,6 +114,16 @@ to place the commands necessary for the creation. You also have to include the a be moved to the dist-git repo so that it is then handled by Packit from there. **Note:** Beware of how Packit uploads files to lookaside cache or adds them to dist-git (see [this note][files_to_sync_info] for more details). +**Note:** During `propose-downstream` / `pull-from-upstream`, the configured `post-upstream-clone` +and `pre-sync` actions run once per target dist-git branch processed by the release-sync loop +(when reached), not once per invocation. A non-reproducible generator (e.g. including changing +timestamps or randomness) can therefore produce a different archive hash on each run, triggering +another upload for each branch when that content is absent from the lookaside cache and uploads +are enabled. Make your generation reproducible: identical inputs should produce byte-identical +archives. Packit automatically checks the lookaside cache by content hash before uploading. +It skips the upload call when all archives already exist there for the same package and filenames, +their filenames occur in the branch's `sources` file, and `--force-new-sources` is not set. +
Creating an archive using tito and syncing it to dist-git repo From 23917afccdb1e4ed4c93b1d30de88beab83d3ef4 Mon Sep 17 00:00:00 2001 From: Nitjsefnie Date: Wed, 28 Oct 2026 12:56:37 +0100 Subject: [PATCH 2/2] docs: clarify lookaside cache reuse during release syncing Signed-off-by: Nitjsefnie Co-Authored-By: GPT-6.1 Terra --- docs/configuration/examples.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/docs/configuration/examples.md b/docs/configuration/examples.md index 02d191e50c..0c7dbee24c 100644 --- a/docs/configuration/examples.md +++ b/docs/configuration/examples.md @@ -120,9 +120,15 @@ and `pre-sync` actions run once per target dist-git branch processed by the rele timestamps or randomness) can therefore produce a different archive hash on each run, triggering another upload for each branch when that content is absent from the lookaside cache and uploads are enabled. Make your generation reproducible: identical inputs should produce byte-identical -archives. Packit automatically checks the lookaside cache by content hash before uploading. -It skips the upload call when all archives already exist there for the same package and filenames, -their filenames occur in the branch's `sources` file, and `--force-new-sources` is not set. +archives. If that is not possible, have the action check Fedora's lookaside cache for the archive by +name and, if present, download an appropriate copy instead of generating it again. The cache lists +each package's files at `https://src.fedoraproject.org/repo/pkgs//`; when configured, the +package name is available in `PACKIT_DOWNSTREAM_PACKAGE_NAME`. When handling sources, Packit still +runs the upload step if an archive's filename does not occur in the branch's `sources` file, but +fedpkg/centpkg do not upload a file whose name and hash are already in the cache for the same package. +Packit skips the upload step entirely only when all archives already exist in the cache for the same +package and filenames, their filenames occur in the branch's `sources` file, and `--force-new-sources` +is not set.