Bundle luet versions in the framework #1748
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
PR messages looks like: Bump of Kairos repositoriesWarning There were changes to installed packages --- build/versions.old.yaml 2023-08-21 13:05:18.190300544 +0200
+++ build/versions.new.yaml 2023-08-21 13:05:18.208300883 +0200
@@ -1,6 +1,6 @@
- name: grub-config
category: static
- version: "0.4"
+ version: "0.5"
- name: grub2-efi
category: system
version: 2.06-150404Important Full package list from new repo - name: grub-config
category: static
version: "0.5"
- name: grub2-efi
category: system
version: 2.06-150404
- name: immucore
category: dracut
version: 0.1.2
- name: immucore
category: system
version: 0.1.2
- name: kairos-agent
category: system
version: 2.2.7
- name: kcrypt
category: system
version: 0.7.0
- name: kcrypt-challenger
category: system
version: 0.5.0
- name: network
category: systemd-default
version: "1.0"
- name: network-legacy
category: dracut
version: "0.9"
- name: suc-upgrade
category: system
version: 0.2.1
- name: sysext
category: dracut
version: "0.9"
- name: systemd
category: init-svc
version: 0.8.0 |
Itxaka
force-pushed
the
versions_luet_packages
branch
from
6cc8533
to
8d6caad
Compare
jimmykarily
reviewed
Aug 21, 2023
Itxaka
force-pushed
the
versions_luet_packages
branch
from
f96b7e5
to
5c454a7
Compare
Use the new luet 0.35 which provides a way of storing the installed artifacts in the system to bundle the versions file with the framework files so we always have a reference for what was installed in the framework and what versions. Also reworks the CI pipeline for the bump repos to provide a diff of changes to **installed** packages, not to the full repo unfortunately, as part of the PR creation so its easily visible what changed that directly affects kairos By cleaning at the end of the actual targets we carry the luet database to the end of the target so we can generate ALL the packages for whaverer artifact we are building so we dont need to mangle the different versions. Either the framework-image or the core/standard base-image will provide a final /etc/kairos/versions.yaml which provider all the artifacts installed by luet Signed-off-by: Itxaka <itxaka@kairos.io>
Itxaka
force-pushed
the
versions_luet_packages
branch
from
5c454a7
to
4804201
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use the new luet 0.35 which provides a way of storing the installed artifacts in the system to bundle the versions file with the framework files so we always have a reference for what was installed in the framework and what versions.
Also reworks the CI pipeline for the bump repos to provide a diff of changes to installed packages, not to the full repo unfortunately, as part of the PR creation so its easily visible what changed that directly affects kairos
Also during iso building, extract and upload the versions to the artifacts so its easier to check what packages were installed in a given iso during CI.
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #