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>
* 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
* chore: remove aurora-incus
this is not referenced anymore
* chore: remove aurora-dx-groups.service
This is super old tech debt, we must have used this in the past to add
users to the dx groups when we still made ISOs for them, instead of the
current post-install rebase
xref: https://github.com/ublue-os/aurora/issues/2584
I reinstalled Aurora on my laptop and afterwards I wanted to connect to
another WiFi Network other than the one I specified in Plasma Setup and
in the network applet you have the option to scan a QR-Code with the
camera and connect to the wifi that way, if we preinstall qrca[1] then
this is just gonna work out of the box.
For desktops it wouldn't be useful for this purpose, but at least you
could still scan QR-Codes from images.
It's a small KDE app so I think it's fine to include by default.
[1]: https://github.com/flathub/org.kde.qrca
Fedora already discussed this effort [1] and they made some great points
against shipping it by default, even though I use it myself quite often,
it should just not be a default on modern systems. I can totally see
this change being made in KDE itself in the future.
[1]: https://forge.fedoraproject.org/kde/tracker/issues/681
We should have a way to update firmware, gnome firmware is maintained
and shouldn't significantly add on to the ISO size as we are already
shipping bazaar and dejadup where the runtime is shared.
This was originally added in
https://github.com/ublue-os/bluefin/pull/1231.
It seems to not be needed anymore, I tested this with bootc install and
upgrading an existing system with the workaround and the /usr/bin/swtpm
has the right selinux label `system_u:object_r:swtpm_exec_t:s0`.
You can verify this with `ls -lZ /usr/bin/swtpm`.
I am not sure what change caused this to be not needed anymore. Maybe it
was the way rpm-ostree handles selinux things nowadays, rechunking
related?
Fixes: https://github.com/ublue-os/aurora/issues/2152
You can test this by pinning ptyxis on the panel and then running this
script inside `plasma-interactive-console` or upgrade an F43 Aurora
image to an image that has this change.
It should make Ptyxis disappear and konsole should show up instead, this
should make the transition easier as ptyxis won't just vanish with no
replacement when we remove it from the image.
How this is supposed to work can be read on here.
https://develop.kde.org/docs/plasma/scripting/#running-scripts
I did not get this working for the favorites section in the kickoff
widget, so for that ptyxis will just disappear with no replacement, but
at least it will not leave a blank icon behind and will not look as
broken.
This might annoy a small minority of people that have been running the
Beta/Latest stream where ptyxis has been removed already and they have
explicitly installed it again via flatpak. This change is intended to
reach the Stable stream when we flip the switch on F44 on that.
Related: https://github.com/ublue-os/aurora/issues/1741
