2025-12-07, 07:55 PM
An additional suggestion on the topic, the upgrade script could be made sufficiently smart to NOT kill a working installation.
Until today, I had a working, but older, Jellyfin installation. I became aware that a newer release was available, and found the following installation command at https://jellyfin.org/downloads/server/;
curl -s https://repo.jellyfin.org/install-debuntu.sh | sudo bash
That seemed official, and I naively assumed that it would be safe, so I ran it.
Now I have zero Jellyfin installations, because that has rendered my previously-working installation, dead. Suggest that it is likely possible to add a check to that script to prevent this from occurring. At a minimum,
a warning to the user to check their installed version, and ensure that it is sufficiently-recent to allow upgrading to the current release, would be friendlier than silently clobbering.
Until today, I had a working, but older, Jellyfin installation. I became aware that a newer release was available, and found the following installation command at https://jellyfin.org/downloads/server/;
curl -s https://repo.jellyfin.org/install-debuntu.sh | sudo bash
That seemed official, and I naively assumed that it would be safe, so I ran it.
Now I have zero Jellyfin installations, because that has rendered my previously-working installation, dead. Suggest that it is likely possible to add a check to that script to prevent this from occurring. At a minimum,
a warning to the user to check their installed version, and ensure that it is sufficiently-recent to allow upgrading to the current release, would be friendlier than silently clobbering.