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

  • chingadera@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    22 hours ago

    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

    • Kelp@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      15 hours ago

      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

      • nom_nom@lemmy.ml
        link
        fedilink
        arrow-up
        7
        ·
        15 hours ago

        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 :)

        • Kelp@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          3
          ·
          14 hours ago

          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

    • grue@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      edit-2
      21 hours ago

      He had added a Jellyfin repo to his apt sources.list file 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

      • chingadera@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        21 hours ago

        Grue, I only really see you when it has to do with Linux.

        Come hang out more with the degens, you’d be appreciated

    • sgh@lemmy.ml
      link
      fedilink
      arrow-up
      4
      ·
      21 hours ago

      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:

      • It’s supposed to be an apt repository URL (To experienced users, it effectively looks like a repository URL)
      • This repository URL does not work
      • As in 99% of cases, this URL is likely located in a configuration file in the standard location, /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.d you 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.