Hello, I yet again come, hat in hand, for assistance from those wiser in the ways of the Linux. I’m having a bit of an issue downloading Jellyfin on my ElementaryOS laptop. I’ve tried all the guide on the first few pages of ddg only to receive errors after entering the comman “ sudo apt-get update “. I get ERR:3 https//repo.jellyfin.org/debian circle Release 404 Not found.
If someone can point me the way I’d be most appreciative
Seems like you followed some random AI generated guide like this one:
https://www.ipv6.rs/tutorial/Elementary_OS_Latest/Jellyfin/
Whenever you’re downloading a Linux (or any) package, always try to look for the official documentation, like here:
https://jellyfin.org/docs/general/installation/linux#debian--ubuntu-and-derivatives
Where it will tell you to install Jellyfin on a Debian/Ubuntu based system is simply:
curl https://repo.jellyfin.org/install-debuntu.sh | sudo bashand it also tells you that if you don’t have curl already installed, either install it first or instead run:
wget -O- https://repo.jellyfin.org/install-debuntu.sh | sudo bashwhich is their official installer.
If you want to undo what you did before installing (assuming you followed the bad guide linked above), just remove the file it created here first:
/etc/apt/sources.list.d/jellyfin.listI just wanted to add a small follow up comment because I remember being young and copy-pasting commands into Linux and eventually getting really frustrated. Therefore, he’s a (brief) explanation of the commands:
curlis just an open source tool for making Web requests from the command line. It’s a great tool to have in general.https://repo.jellyfin.org/install-debuntu.shthe URL of a shell script from repo.jellyfin.org (Jellyfin’s official website)What is a shell script? It’s a script that runs a whole bunch of commands by itself, so you don’t have to copy-paste them from the internet. Basically the official Jellyfin people in this case made a file with all of the commands the computer needs to run to install the package. This is great because it means the people who made Jellyfin tested these commands and they’re responsible for keeping it up to date if anything changes.
| bashThe ‘pipe’ or|symbol in Linux is a cool Unix philosophy of ‘connecting’ programs together. You run one program, and tell it to pass the results to another program. In this case, you’re tellingcurlto download the script athttps://repo.jellyfin.org/install-debuntu.shand then passing that file tobash(which is the shell program in the terminal that runs commands) and to run it assudoor ‘super-user’.Hope this was helpful. The last thing you should know is the command you probably copy-pasted before made you add a source to the
/etc/apt/sourcesfiles, which are basically just a list of sources forapt, the package manager to download from, and since the command was wrong or outdated,aptis complaining that the Jellyfin source was not found.GOOD FOLLOW UP!!
I was about to shit a brick that you went from “go to the official trusted source” to “just trust me: curl [x] | sudo bash”
https://youtu.be/dT7X2IxBDjc
You can do some wild shit with pipes:
head -10 /var/log/syslog- Look at the first ten lines of one of your log files, with timestamps on the frontcat /var/log/syslog | cut -d' ' -f1- Splits the lines by a space delimiter (the-d' 'part), and grabs the first “field” (the one with the timestamp, using-f1)cat /var/log/syslog | cut -d' ' -f1 | cut -dT -f1- Splits the timestamp at the “T”, and leaves only the datecat /var/log/syslog | cut -d' ' -f1 | cut -dT -f1 | sort | uniq -c- Gives you a count of each dategrep systemd /var/log/syslog | cut -d' ' -f1 | cut -dT -f1 | sort | uniq -c- For only the lines with ‘systemd’ on it, gives you a count of each dateThe standard GNU toolkit has a ton of utilities like that for doing stuff with text files.
At work whenever we need to build little command line tools, my team is always vexxed by my guideline to have the meat+potatoes in a script that reads well-formatted data off stdin , and outputs well formatted-data to stout. They always wanna have some stupid interactive prompts and saving to files baked right in.
This is exactly why. You wanna save to a file?? > file
You want to read from a file? cat |
You want to save to a file but swap commas for colons? Sed.
You get so much FOR FREE w/ the GNU toolkit, even for what you build yourself, by thinking in streams.
When trying to explain that concept, I like showing people this: https://www.youtube.com/watch?v=tc4ROCJYbm0&t=296
Wow, this was a treat to watch. Never would have imagined Brian Kernighan would be explaining shell pipeline to me in such a cosy setting
I find it unbelievably cool that the guys who came up with this got it so right the first time, that its still incredibly powerful today.
Me, a simpleton,
“Wut dat mean”
The one thing I’d add is to say don’t run a shell script from the Internet unless you’re damn sure that (a) you trust the entity providing it, and (b) you’re downloading via https and haven’t typo’d the URL.
Agreed, but I didn’t want to overwhelm the guy with too much info :P The official guide even recommends checking the cryptographic signature of the script and reading its contents first. I’m sure like all of us they’ll nuke their system several times and before long will be writing their own shell scripts.
How the fuck did you deduce that from the post above?
I’m not doubting you at all, you’ve got the Linux aura, but please share so more people can hope to do this
He had added a Jellyfin repo to his apt
sources.listfile for some reason, which is weird and likely not the right way to do it these days. But it might have been in the past, so it could be OP was following some obsolete procedure (or one AI-hallucinated from an obsolete procedure).After realizing that OP was completely going about it the wrong way, the guy you replied to just looked up the correct way and relayed that to him.
See also: https://wiki.debian.org/DontBreakDebian
Grue, I only really see you when it has to do with Linux.
Come hang out more with the degens, you’d be appreciated
This dude is a wizard cause that was the exact “guide” I was using. I had to look over my shoulder for a sec lol
Because, contrary to what it might seem like, we ALL start out this way using Linux. Everyone makes the same mistakes, so its easy to retrace the logic once you understand what the commands you used to copy-paste are doing. OP you’re clearly just making the switch and want to dive head-first into self-hosting as well as Linux, which will be a ton of fun, just try not to get discouraged as there is a lot to learn. Take it one step at a time, and try to understand the commands as there’s really not that many, and you re-use these in many scenarios.
I see many people recommending Docker, which is great, but imho a little too early to dive in to if you haven’t experimented with Linux at all. Docker is just a container of Linux inside of Linux, so you’ll still need to use the command line, and it has its own set of tools. Just my two cents. Somebody else posted but this was the video that also made Linux ‘click’ for me:
https://www.youtube.com/watch?v=tc4ROCJYbm0&t=296
Don’t be afraid to break things and start over. Have fun :)
Thanks so much for the kind words on top of the invaluable info you’ve provided. You are a true gentle-person and a scholar
Seriously an absolute witch.
@nom_nom@lemmy.ml
If you’re not being paid an insane amount of money for your insight, you are fucking up bud. People would pay crazy money for that type of deduction.
We are being paid the most though through secondhand knowledge, keep being you, and OP you also keep being you, I love this whole post.
Not OP, but it was very simple if you have already seen that error.
First of all, there is one single easily parsable error.
https://repo.jellyfin.org/debian produced a 404 error, thus the URL is invalid.
Let’s ignore why it’s invalid for a second.
This error happens after
apt update, thus we can deduce the following:/etc/apt/sources.list.d/Back to why it’s invalid, maybe it used to be valid in the past, or there is a temporary server error, this can be verified with the official documentation.
If the documentation does not mention this repository URL, then it’s a mistake to use it.
This is a good moment to google this URL and find out why/which guide tells you to use it, and to analyze which steps they made you take.
From there, reverse those steps.
Even if you hadn’t found this guide, you can be sure that by looking into
/etc/apt/sources.list.dyou would’ve found that file containing that URL, simply removing the file or URL would’ve removed the error.Lastly, you look for either the official documentation, or a more reliable guide.
This was cool, thank you for doing it.
Sometimes it’s hard to switch gears and understand this OS/language, but you did an excellent job of bridging that gap. Thank you.
This
Well now I feel really dumb cause that is the exact guide I was using. Oh well, live and learn I guess. Thank you very much for educating me