(2024-01-11, 03:07 PM)Host-in-the-Shell Wrote:

(2024-01-11, 12:58 PM)Takane7 Wrote: I did have to go through the basic jellyfin setup again though

Seems like that is a known issue: https://wiki.archlinux.org/title/Jellyfin#Web_interface_redirects_to_setup_wizard_after_update.

(2024-01-11, 12:58 PM)Takane7 Wrote: I tried importing the users through the backup i made, but couldnt seem to find whatever config file is responsible for them

I believe it is not possible to migrate users due to the way databases are structured, although I'm basing this information on an old reddit post from 2020 I found online, and not sure if it's still the case.[1]

Well this could have gone much, much worse so I'm happy the transition left the service mostly intact. That said, I think this case exemplifies why I don't recommend to use pacman wrappers such as yay or paru in the first place; not only do they introduce unsafe flags,[2] but they also abstract a lot of the manual build process and can certainly create broken/messy situations very quickly. What I recommend is to use an AUR helper that is not a pacman wrapper. I personally use auracle to handle everything such as checking for updates, updating repositories, etc. Then, I build manually using makepkg. However, AUR helpers are unsupported so keep that in mind as well... but then again, AUR in general is unsupported too.

I get the convenience of wrappers, but the main problem is that they will break your system at one point, specially if you run them blindly without really understanding the manual build process and how to unscrew anything a wrapper can cause.

[1] https://www.reddit.com/r/jellyfin/comments/jwwr05/where_are_the_user_settings_stored/gctyq0k/?context=3
[2] https://wiki.archlinux.org/title/AUR_helpers#Pacman_wrappers