2024-03-24, 01:01 AM
This is a rather obscure situation that I understand if no one wants to look at... Probably only effects me and my ridiculous setup, so I don't mind if it's a won't fix situation.
I have my media on a very old Debian container on my Proxmox server set up years ago as a 32 bit (i386) container. I've since added 64 bit as a foreign architecture to allow a few other 64 bit only tools to be installed. The primary arch on this container is still i386. When I attempted to install Jellyfin, I ran into a few dependency issues.
1) jellyfin (the meta package) depends on jellyfin-web and jellyfin-server. Apt/dpkg can't figure out the amd64 version of jellyfin-server is valid for this, but because the jellyfin and jellyfin-web are "all" arch, it also won't allow specifying amd64 as an alternative arch. I'm not sure if this one is actually fixable without breaking something else, but in case a Debian packaging guru can see a way, I'm mentioning.
I worked around this one by simply installing jellyfin-web from a deb file, which it was happy to do. If that's what I have to keep doing going forward, then that's fine.
2) This is the more broken one... It appears to me that jellyfin-server depends on libstdc++6 and some version of libicu, but doesn't specify them as dependencies... It happily installed all the other 64 bit dependencies, but trying to start it failed. Installing the 64 bit versions of those 2 packages (32 was already on - not sure if that was a dependency from the other jellyfin packages or they were just already there) resulted in a working install.
Final result is I have a working install, so I don't need any assistance right now with that.
I understand if this is just not worth fixing when I'm probably the only one who has such a silly setup... But I thought it might be worth mentioning in case it's easier to fix than I expect or could be effecting other people in some way.
I have my media on a very old Debian container on my Proxmox server set up years ago as a 32 bit (i386) container. I've since added 64 bit as a foreign architecture to allow a few other 64 bit only tools to be installed. The primary arch on this container is still i386. When I attempted to install Jellyfin, I ran into a few dependency issues.
1) jellyfin (the meta package) depends on jellyfin-web and jellyfin-server. Apt/dpkg can't figure out the amd64 version of jellyfin-server is valid for this, but because the jellyfin and jellyfin-web are "all" arch, it also won't allow specifying amd64 as an alternative arch. I'm not sure if this one is actually fixable without breaking something else, but in case a Debian packaging guru can see a way, I'm mentioning.
I worked around this one by simply installing jellyfin-web from a deb file, which it was happy to do. If that's what I have to keep doing going forward, then that's fine.
2) This is the more broken one... It appears to me that jellyfin-server depends on libstdc++6 and some version of libicu, but doesn't specify them as dependencies... It happily installed all the other 64 bit dependencies, but trying to start it failed. Installing the 64 bit versions of those 2 packages (32 was already on - not sure if that was a dependency from the other jellyfin packages or they were just already there) resulted in a working install.
Final result is I have a working install, so I don't need any assistance right now with that.
I understand if this is just not worth fixing when I'm probably the only one who has such a silly setup... But I thought it might be worth mentioning in case it's easier to fix than I expect or could be effecting other people in some way.
