`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>
