Ouch. Rerunning install script puts system into unusable state

[sepulworld]

Hi! I wrongfully assumed that re-running the installer script will give me the option to upgrade or update. Instead, it immediately put my system into an unusable state.

It seemed to break the Waybar and themes. And put the system into an odd state where I couldn't move workspaces and had to force reboot. Upon reboot no theme is loaded and waybar is not starting. I am able to start up applications, but system is definitely in a bad state. I see now I should have ran omarchy-update instead :( Ill run this now and report back.

I think the installer should detect system is already setup and offer option to upgrade + backup or wipe clean.

Thoughts?

We need some sort of check to prevent this from happening.

[sepulworld]

system reboots to a black screen with active mouse. No waybar or background.

[sepulworld]

I removed some broken symlinks and re-ran the installer.

I think maybe a "warning" or something might be nice to have on the installer to perhaps prevent others from accidentally shooting themselves in the foot? 🤷

[VolodymyrVorona]

I ran the omarchy-update script and ended up in the same situation. There are some Git conflicts in the Omarchy defaults. I ran git reset --hard origin/master and re-ran the omarchy-update script, but it didn’t help the same conflicts appeared. Also, some stashed changes showed up.

[rmacklin]

The issue with manually-stashed changes being popped has been fixed in #215 (which is already merged so it will be in the next release). And I have an open PR to avoid leaving your repo in a conflicted state: #220