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

docs(genesis): define current release completeness

Browse Source
This commit is contained in:
Vinícius Ferrão
2026-09-04 17:15:25 -03:00
parent f522398456
commit 64ecf10b41
2 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
BUILD.md
+3 -3
View File
@@ -247,9 +247,9 @@ generation, and signing have succeeded. If a stopped publisher leaves staging
or backup directories behind, rerun it with ``--force-unlock`` to recover the
previous repository before starting a new publication.
Repository publication requires a complete release for its manifest version.
Version 1 contains seven architectures; version 2 also requires `s390x`. The
packages are `noarch`, and each publication contains that release's full set.
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.
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
+6 -5
View File
@@ -89,11 +89,12 @@ 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. Seven-architecture version
1 releases remain publishable. Building a version 2 release requires an
xcat-core revision with the `s390x` OpenEmbedded target. Merge or deploy that
xcat-core change first. A management node can install an image for a different
target architecture.
Version 2 releases require all eight architectures. Version 1 remains readable,
but current publishers refuse it because replacing the repository would remove
`s390x`. 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.