repo #87

Closed
opened 2026-02-06 19:17:04 +03:00 by OVERLORD · 19 comments
Owner

Originally created by @penfolduk on GitHub (Dec 14, 2018).

Originally assigned to: @joshuaboniface on GitHub.

repo not working

sudo apt install jellyfin
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package jellyfin

Originally created by @penfolduk on GitHub (Dec 14, 2018). Originally assigned to: @joshuaboniface on GitHub. repo not working sudo apt install jellyfin Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package jellyfin
OVERLORD added the question label 2026-02-06 19:17:04 +03:00
Author
Owner

@Camotoy commented on GitHub (Dec 14, 2018):

Did you add the package repository as mentioned in the Readme?

@Camotoy commented on GitHub (Dec 14, 2018): Did you add the package repository as mentioned in the Readme?
Author
Owner

@penfolduk commented on GitHub (Dec 14, 2018):

yeh that failed as well

Ign https://repo.jellyfin.org buster/main Translation-en_US
Ign https://repo.jellyfin.org buster/main Translation-en
W: Failed to fetch https://repo.jellyfin.org/debian/dists/buster/main/binary-amd64/Packages gnutls_handshake() failed: Handshake failed

W: Failed to fetch https://repo.jellyfin.org/debian/dists/buster/main/binary-i386/Packages gnutls_handshake() failed: Handshake failed

E: Some index files failed to download. They have been ignored, or old ones used instead.

@penfolduk commented on GitHub (Dec 14, 2018): yeh that failed as well Ign https://repo.jellyfin.org buster/main Translation-en_US Ign https://repo.jellyfin.org buster/main Translation-en W: Failed to fetch https://repo.jellyfin.org/debian/dists/buster/main/binary-amd64/Packages gnutls_handshake() failed: Handshake failed W: Failed to fetch https://repo.jellyfin.org/debian/dists/buster/main/binary-i386/Packages gnutls_handshake() failed: Handshake failed E: Some index files failed to download. They have been ignored, or old ones used instead.
Author
Owner

@penfolduk commented on GitHub (Dec 14, 2018):

get Welcome to nginx! when click on repo URL

@penfolduk commented on GitHub (Dec 14, 2018): get Welcome to nginx! when click on repo URL
Author
Owner

@joshuaboniface commented on GitHub (Dec 14, 2018):

@penfolduk The Welcome is intended - only the /debian folder is valid.

The handshale failed is odd, it seems to indicate old SSL libraries are in use - exactly what distro and release are you using? I can tweak the server config to fix that.

@joshuaboniface commented on GitHub (Dec 14, 2018): @penfolduk The Welcome is intended - only the `/debian` folder is valid. The handshale failed is odd, it seems to indicate old SSL libraries are in use - exactly what distro and release are you using? I can tweak the server config to fix that.
Author
Owner

@joshuaboniface commented on GitHub (Dec 14, 2018):

Also at the moment, there's no i386 in the repo so I recommend ensuring you aren't trying to use multiarch here.

@joshuaboniface commented on GitHub (Dec 14, 2018): Also at the moment, there's no i386 in the repo so I recommend ensuring you aren't trying to use multiarch here.
Author
Owner

@penfolduk commented on GitHub (Dec 14, 2018):

ubuntu 14.04.5 LTS

@penfolduk commented on GitHub (Dec 14, 2018): ubuntu 14.04.5 LTS
Author
Owner

@penfolduk commented on GitHub (Dec 14, 2018):

am using a vps server

@penfolduk commented on GitHub (Dec 14, 2018): am using a vps server
Author
Owner

@joshuaboniface commented on GitHub (Dec 14, 2018):

@penfolduk Can you try it now and let me know? If it still doesn't work, please post the exact contents of your repo .list file and a test of curl -v https://repo.jellyfin.org/debian/dists/buster/main/binary-amd64/Packages && date via a pastebin please, as that will help troubleshoot. 14.04 isn't that old so I'd like to make sure it works!

@joshuaboniface commented on GitHub (Dec 14, 2018): @penfolduk Can you try it now and let me know? If it still doesn't work, please post the exact contents of your repo `.list` file and a test of `curl -v https://repo.jellyfin.org/debian/dists/buster/main/binary-amd64/Packages && date ` via a pastebin please, as that will help troubleshoot. 14.04 isn't that old so I'd like to make sure it works!
Author
Owner

@thejacer87 commented on GitHub (Dec 14, 2018):

14.04 isn't that old so I'd like to make sure it works!

well LTS for it ends in 4 months... so it might not be crucial to support going forward IMO

@thejacer87 commented on GitHub (Dec 14, 2018): > 14.04 isn't that old so I'd like to make sure it works! well LTS for it ends in 4 months... so it might not be crucial to support going forward IMO
Author
Owner

@joshuaboniface commented on GitHub (Dec 14, 2018):

Thought it was 5 years not 4, in that case it may be prudent to upgrade anyways @penfolduk , but I'm curious if this helps. In short I re-enabled SSLv3 support and [NGiNX doesn't enable it, but that's fine] ALL ciphers for the latest NGiNX so that should let slightly older systems work normally. I still get an A rating on the SSLLabs site test so it's still quite secure.

@joshuaboniface commented on GitHub (Dec 14, 2018): Thought it was 5 years not 4, in that case it may be prudent to upgrade anyways @penfolduk , but I'm curious if this helps. In short I re-enabled ~~SSLv3 support and~~ [NGiNX doesn't enable it, but that's fine] ALL ciphers for the latest NGiNX so that should let slightly older systems work normally. I still get an A rating on the [SSLLabs site test](https://www.ssllabs.com/ssltest/index.html) so it's still quite secure.
Author
Owner

@thejacer87 commented on GitHub (Dec 14, 2018):

it is 5 years....

14.04 release april 14, support end april 19

@thejacer87 commented on GitHub (Dec 14, 2018): it is 5 years.... 14.04 release april 14, support end april 19
Author
Owner

@joshuaboniface commented on GitHub (Dec 14, 2018):

Oh right it's the end of 2018... 😆

@joshuaboniface commented on GitHub (Dec 14, 2018): Oh right it's the end of 2018... :laughing:
Author
Owner

@penfolduk commented on GitHub (Dec 14, 2018):

apt update is fine now

@penfolduk commented on GitHub (Dec 14, 2018): apt update is fine now
Author
Owner

@joshuaboniface commented on GitHub (Dec 14, 2018):

Perfect, thanks for confirming. Closing this one out.

@joshuaboniface commented on GitHub (Dec 14, 2018): Perfect, thanks for confirming. Closing this one out.
Author
Owner

@penfolduk commented on GitHub (Dec 14, 2018):

but
get this on install

root@flussonic:~# sudo apt install jellyfin
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
jellyfin : Depends: ffmpeg but it is not installable
E: Unable to correct problems, you have held broken packages.
root@flussonic:~# sudo apt install jellyfin
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
jellyfin : Depends: ffmpeg but it is not installable
E: Unable to correct problems, you have held broken packages.

@penfolduk commented on GitHub (Dec 14, 2018): but get this on install root@flussonic:~# sudo apt install jellyfin Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: jellyfin : Depends: ffmpeg but it is not installable E: Unable to correct problems, you have held broken packages. root@flussonic:~# sudo apt install jellyfin Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: jellyfin : Depends: ffmpeg but it is not installable E: Unable to correct problems, you have held broken packages.
Author
Owner

@joshuaboniface commented on GitHub (Dec 14, 2018):

Jellyfin depends on ffmpeg, so that package needs to be installed. It was removed from 14.04 for some reason, but tthis guide shows how to get it installed: https://www.faqforge.com/linux/how-to-install-ffmpeg-on-ubuntu-14-04/

@joshuaboniface commented on GitHub (Dec 14, 2018): Jellyfin depends on ffmpeg, so that package needs to be installed. It was removed from 14.04 for some reason, but tthis guide shows how to get it installed: https://www.faqforge.com/linux/how-to-install-ffmpeg-on-ubuntu-14-04/
Author
Owner

@JustAMan commented on GitHub (Dec 14, 2018):

Btw Ubuntu 16.04 has libav disguised as ffmpeg (found it out today in a hard way)... We may want to ship our own ffmpeg that is nee enough and is known to support all the switches we throw at it.

@JustAMan commented on GitHub (Dec 14, 2018): Btw Ubuntu 16.04 has libav disguised as ffmpeg (found it out today in a hard way)... We may want to ship our own ffmpeg that is nee enough and is known to support all the switches we throw at it.
Author
Owner

@joshuaboniface commented on GitHub (Dec 14, 2018):

Ulgh damn you Canonical. I don't pike the idea of including our own since I'm sure we'll inevitibly get a "why does feature X not work" if we build it in strict GPL mode, which we'd have to. Do the later Ubuntus still do the same thing with libav? If not we can just add that PPA as part of the install guide.

@joshuaboniface commented on GitHub (Dec 14, 2018): Ulgh damn you Canonical. I don't pike the idea of including our own since I'm sure we'll inevitibly get a "why does feature X not work" if we build it in strict GPL mode, which we'd have to. Do the later Ubuntus still do the same thing with `libav`? If not we can just add that PPA as part of the install guide.
Author
Owner

@JustAMan commented on GitHub (Dec 15, 2018):

I don't think they did revert to ffmpeg, at least I cannot find a word about that.
Though ffmpeg devs list official ppa's for Ubuntu at ffmpeg.org, so we can point people there.

@JustAMan commented on GitHub (Dec 15, 2018): I don't think they did revert to ffmpeg, at least I cannot find a word about that. Though ffmpeg devs list official ppa's for Ubuntu at ffmpeg.org, so we can point people there.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#87