xCAT/xcat-dep
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-dep.git synced 2026-09-12 04:26:25 +00:00
Code Issues Projects Releases Wiki Activity

docs(genesis): explain release formats

Browse Source
This commit is contained in:
Vinícius Ferrão
2026-09-06 10:54:29 -03:00
parent c8def3dc02
commit 99d60459e7
2 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
BUILD.md
+3 -2
View File
@@ -248,8 +248,9 @@ or backup directories behind, rerun it with ``--force-unlock`` to recover the
previous repository before starting a new publication.
Repository publication requires all eight current architectures. Version 1
remains readable but cannot replace the current repository because it lacks
`s390x`. The packages are `noarch`, and each publication contains the full set.
release manifests remain readable, but they cannot replace the current
repository because they lack `s390x`. The packages are `noarch`, and each
publication contains the full set.
The release checksums cover the unsigned input packages. If repository signing
is enabled, `rpmsign` changes the deployed RPM bytes after collection.
genesis-openembedded/README.md
+7 -8
View File
@@ -89,14 +89,13 @@ repository with a single rename, under one global publish lock, so a failed or
interrupted publication leaves the previous repository exactly as it was.
Both consumers verify package identities and checksums before publication.
Version 2 releases require all eight architectures. Version 1 remains readable,
but current publishers refuse it because replacing the repository would remove
`s390x`. Builder and publisher hosts must use the same xcat-dep revision when
the release format changes. Building `s390x` requires an xcat-core revision
that reports the target.
Merge or deploy that xcat-core change first. Builds for the other architectures
still accept older xcat-core revisions. A management node can install an image
for a different target architecture.
Releases containing `s390x` use format version 2. Other releases keep version 1
and remain readable by older tools. Current publishers require all eight
architectures, so a version 1 release cannot replace the shared repository.
Building `s390x` requires an xcat-core revision that reports the target. Merge
or deploy that xcat-core change first. Builds for the other architectures still
accept older xcat-core revisions. A management node can install an image for a
different target architecture.
Without `--genesis-release`, both builders keep their existing behavior. The
new packages do not provide, replace, or obsolete the old package names.