* chore: Remove usage of `yq` in favor of `jq`
* fix: Missed bracket in `default-flatpaks`
* fix: `get_json_array` complaining about unpopulated arrays
* fix(files): Forgot to input `-r` flag for some `jq` calls
* fix(gschema-overrides): Use `try` in `get_json_array`
* chore(default-flatpaks): Replace `yq` with `jq` in run-time setup binaries
* chore: Switch to simplified `jq` syntax without brackets
* chore(default-flatpaks): Switch `repo-info` file from `yml` to `json`
* fix(default-flatpaks): Some `yq` calls
* chore: Revert back to bracket syntax for more reliable `jq` parsing
* chore(files): Missed bracket syntax
* chore: Approve bot suggestion about quoting
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* Update modules/files/files.sh
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* fix(yafti): Populating custom flatpaks
It's populated in reverse order compared to the format in recipe, but it works
* fix(fonts): Variable substitution is needed
* fix: Typo
* fix(fonts): Forgot to assign FONTS variable
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
recipes with aurora/bluefin as a base image will already have the staging repo present but disabled, meaning wget won't overwrite it.
we don't want to change the repos in the base image in this module, so this backs up the original staging repo, runs the module steps, then restores the original staging repo
* docs(files): Recommend to put files in `/etc/` instead in `
This also modifies build-time part of modules to work with `/etc/` instead of `/usr/etc/`
* docs(files): Revert the `/usr/etc/` & `/etc/` docs
* chore: Revert `signing` module transition due to upstream issue
* docs: Clarify note better regarding /etc
`rpm-ostree` method is not capable of installing yafti's older version of `python3-pydantic` instead of being confused between both system's & yafti's version of that package.
I tried to increase `ublue-os staging` repo priority, where yafti resides, but that doesn't work.
Pip method while not flawless with its hardlinking errors when same system package tries to get installed, it at least finishes yafti install successfully.
Assures that users won't get suddenly get refactored yafti someday. It would also let us have more time to update yafti docs before merging updated yafti version.
I switched my custom ublue image from using
"ublue-os/silverblue-nvidia" to "ublue-os/bazzite-gnome-nvidia" and
received the following error when the build action kicked off:
`ln: failed to create symbolic link '/usr/etc/profile.d/ublue-firstboot.sh': File exists`
The yafti module should be the only thing creating this symlink, so it
should be safe to use the `-f` flag to force creating it.
Signed-off-by: Micah Abbott <miabbott@redhat.com>
* docs: chore: rn ":" from "Example configuration"
* docs: correct title casing for fonts module title
* docs: document OS_VERSION in example,...
non-copr example for rpmrepos
* docs: remove bling fonts option from bling example
* docs: start yafti README the same way as others
"The yafti module..."
