Themes migration used from [1].
Part of [2].
[1] https://github.com/ublue-os/bazzite/pull/6122
[2] https://github.com/ublue-os/aurora/issues/3038
no preinstall files
probably the better way to handle this with a notification instead of
preinstalling everything, also makes it easier because we would need to
wait for preinstall to have finished, which we can't easily do from the
systemd user service
this takes up 400MiB on disk, if people want to have it they can just
download it. We also already include thunderbird which has a lot of
overlap with this.
* move to upstream Zed
* use opencode from upstream
* fix antigravity-ide cask name
* remove zed@preview
* kpt is now on core
* tremor is removed from tap and core
This got added in [1]. We should not override this for all software, we
should fix our stuff. Also I'm not sure if this is even relevant
anymore.
1: 065b90bdd7
* feat(just): use bootc upgrade when possible
The reason why we are not using uupd, which would completely handle the
bootc rpm-ostree compatibility dance is because the output is not super
useful from a troubleshooting perspective and people like their bling.
What we want is to use bootc for upgrades when it is possible to use it.
We currently don't do this as we just check for the `LockLayering` value
in `rpm-ostreed.conf`. Users don't change this so this will always call
to `rpm-ostree`. We have this because it used to be a shared recipe with
bluefin-lts which sets `LockLayering=True` because it doesn't support
package layering.
Bootc upgrade is slightly faster than rpm-ostree and more importantly
does not mess with any RPMs or calls to any repos, which are all steps
that might fail. There have also been bugs in recent times in
`rpm-ostree` that broke image updates [1]. Bootc is simpler and the
likelihood seems to be lower for `upgrade` to straight up be broken.
The disadvantage compared to always using rpm-ostree for everything is
that bootc doesn't have polkit rules to allow members of the wheel group
to execute it without authentication, even if rpm-ostree ends up being
used which does exactly that.
More complex and probably more buggy alternative to
https://github.com/get-aurora-dev/common/pull/252
[1] https://github.com/coreos/rpm-ostree/issues/5567
* handle container case
* why it needs root password
Final solution for the new just completion engine ended up being; For
`bash` we have to change the script to set `JUST_JUSTFILE` while having
an autocomplete script where `just` is substituted to `ujust`. This was
based on feedback from Casey in
https://github.com/casey/just/discussions/3683#discussioncomment-17804984
For `fish` the only method i found to get the completions working
properly was to alias `ujust` to `just --justfile
"/usr/share/ublue-os/justfile"`
now for zsh i had to write a custom compdef that hardcodes in
`--justfile "/usr/share/ublue-os/justfile"` and passes it to the
completion definitions for `just`, i do not want to go into how long i
spent on this stupid compdef...
Hikari's words, he figured everything out here. Thanks. It's an exact
clone of https://github.com/ublue-os/packages/pull/1319.
resolves: https://github.com/get-aurora-dev/common/issues/220
Co-authored-by: HikariKnight <2557889+HikariKnight@users.noreply.github.com>
* feat(ci): dual-sign image with OIDC and static key
container-libs doesn't support our new keyless signatures here, let's
support both
* chore: pin cosign
this is a ticking time bomb, renovate should pick this up automatically
* chore: add all the things from aurorafin-shared
Bluefin is not interested in the lack of AI in the development process
of it, let's put everything here.
It still makes sense to have this repo to avoid fetching the
wallpapers/udev rules in an image build every single time.
* fix: correct path for binary
* remainings
* chore: remove ai stuff we don't use
* redo brew validation
* use bbrew from main homebrew
* remove tiup
this is broken, is it gone from some tap?
* remove kcl from brewfiles
something is broken here as well
Upstream is dead, still leave the option for users to switch back to
wpa_supplicant if they enabled it. Migrating people away from IWD
automatically would be bad because it would break internet connections
for users.
Let's leave this in for a couple months.
I don't know why the desktop doesn't dictate this to applications. We
ship firefox by default so we have to change it there as well. This
leaves chromium with the bad stock behavior, but we can't really ship
configurations for the entirety of flathub.
It will only affect new installations.
Follow up of https://github.com/get-aurora-dev/common/pull/224
