• 0 Posts
  • 9 Comments
Joined 2 years ago
cake
Cake day: July 29th, 2023

help-circle

  • I am using bazzite for gamedev and it is AWESOME.

    It is immutable but ships with distrobox and boxbuddy, which lets you easily create linux containers with mutable systems (i.e. I am currently developing on a fedora container with Qt Creator, for example) and you can install your packages in that terminal.

    No chances of breaking your main OS.

    I set up my instance like follows:

    Boxbuddy -> New distrobox container -> Fedora -> Give it a name.

    Wait for the installation (should be about 300MB IIRC).

    In the start menu you will now be able to run your instance’s terminal (search for your instance name).

    sudo dnf install qt-creator

    Back in boxbuddy, in my instance I selected “show installed gui applications”, selected Qt Creator -> Add to applications menu.

    Qt Creator then shows up in the start menu (search for either Qt Creator, or your instance name).

    It will run in the container, but has full access to your home directory for development.

    I could then install all my other required packages from the same terminal that I installed qt-creator from.

    Easy peasy.

    Disclaimer: Typing from my phone. The instructions may not be exactly like I said, but those are the steps.

    No terminal magic is needed in Bazzite to make this work.





  • sgh@lemmy.mltoLinux@lemmy.mlJellyfin assistance
    link
    fedilink
    arrow-up
    5
    ·
    2 months 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.