Arch Linux

I think I got this fixed.

I noticed the same problem as experbia did, although during the install: chown: invalid user: ‘emby:emby’

emby-server.install seems to do "chown -R emby:emby /var/lib/emby-server" before checking if the user and the group do exist. You might want to move that chown.

If you're having trouble getting the service to start as I was, I noticed permission complaints about /var/lib/emby-server in journalctl, so with a chown of that dir to emby:emby everything seems to start up naturally.

It was freshly installed, never having had any mediabrowser or emby installations on this system previously.

New package going up. I made one other change to better conform to the naming scheme used in /etc/conf.d by other packages. The environment file is now name simply emby-server instead of emby-server.conf.

If you are using a custom environment file, please rename it to the new standard. If you are using a custom systemd service file, please rename the EnvironmentFile value to reflect the name change.

Thanks for the bit about the backup. I wasn't sure how to keep users from needing to reconfigure their settings on every update. Now I guess I know. :)

I will make the changes.

It its current state, the systemd service fails to start. It is trying to load this file.

EnvironmentFile=/etc/conf.d/emby-server.conf

But the PKGBUILD is installing the config in a different location.

install -Dm644 ${srcdir}/emby-server.conf ${pkgdir}/usr/share/emby-server/emby-server.conf

Here's a suggestion: change both of these to a standard location in /etc.

EnvironmentFile=/etc/emby-server.conf
install -Dm644 ${srcdir}/emby-server.conf ${pkgdir}/etc/emby-server.conf

And don't forget properly mark that file so it doesn't get overwritten on updates.

backup=('etc/emby-server.conf')

No, that is not possible unless you implemented a script that grabs some info from the old folder. It will work if the media is named according to media browse requirements but not otherwise.

I tried replacing the absolute paths in library.db sqlite database file but then I started getting "Cannot cast from source type to destination type." I couldn't find anything on that error so I just re-installed and will stick with partial metadata on some movies for now (identifying one by one would take far too long).

I am pretty sure that is the case. The forum thread led me to believe that at least. He just had to refresh the library which doesn't make you reidentify anything. It just uses the existing database IDs to query the databases for what the new metadata paths are.

Oh, so the library is saved and only metadata is lost? All I need is the media path / id pairs as well as the settings (which I have already). I don't so much mind re-downloading metadata as long as I don't have to identify movies one by one again...

Did you select the option to save the metadata to the media folders? If so, all of your metadata is safe and you can do a library rescan without having to worry about a rescan missing things. Everything should have the same metadata that it had before.