• Consti@lemmy.world
    0·
    7 months ago

    Of course it won’t do anything, you need to update (refresh the index) before you upgrade (download and install updates), silly you

    • poweruser@lemmy.sdf.orgEnglish
      0·
      7 months ago

      Yep. I’m on Debian for many years now. Every broken update I can recall was either caused by an undocumented PPA or nvidia drivers (which have finally been fixed, for my card at least)

  • Zanka@lemmy.ml
    0·
    7 months ago

    Fedora: sudo dnf update, type the letter y, done.

    I don’t understand why apt still has update and upgrade as two separate things.

      • Ephera@lemmy.mlEnglish
        0·
        7 months ago

        You can have a separate refresh/update command and still make the upgrade-command auto-refresh.

        (You can also have a --no-refresh flag on the upgrade-command, in case you don’t want the refresh for whatever reason.)

    • zewm@lemmy.worldEnglish
      0·
      7 months ago

      I’m more of a fan of just adding the -y parameter to skip the question and go straight to updating. Works with the install command too.

  • Cat_Daddy [any, any]@hexbear.netEnglish
    0·
    7 months ago

    Pacman sucks ass and this is a hill I will die on. Sure, it’s fast, but there’s such a thing as too fast. Like when I was updating the system once and it decided to delete bash to replace it, but it couldn’t replace it because bash was gone already and my shell died since that’s what I was logging in with. Oops! System is completely unusable now, got to reinstall arch again, because pacman pulls stunts like this.

    • deadcade@lemmy.deadca.de
      0·
      7 months ago

      This type of shit happens if you intentionally mess up your own system (or use Manjaro). pacman requires extra confirmation (instructions only found in its man page) before even allowing you to delete bash (base requires it). bash has also never been replaced, and even if you deleted it, it would still be loaded in RAM. Even still, if you deleted it and immediately rebooted, it would be a quick fix for anyone familiar with the distribution they’re using, and would not require reinstalling the whole thing.

      • Cat_Daddy [any, any]@hexbear.netEnglish
        0·
        7 months ago

        You would think that, but it happened to me several times over the course of about five years, with different parts of the core of the os. Granted, this was back when arch was in its infancy, before systemd was even a thing, so pacman may be smarter now. But I’ve completely written it off since it happened so many times. And reinstalling arch back them took the better part of a weekend, so it’s not like it was an easy fix.

  • Matriks404@lemmy.world
    0·
    7 months ago

    Debian users:

    What do you mean by PPA?

    Also: apt-get is intended as low-level APT interface for scripts, just use apt instead. I get why people are confused nowadays, because APT documentation is terrible.

    • MonkderVierte@lemmy.zip
      0·
      7 months ago

      apt-get is intended as low-level APT interface for scripts

      Ah, that’s what they call it now.

      I wonder to what they degraded dpkg then?

    • notarobot@lemmy.zip
      0·
      7 months ago

      I thought apt-get was a transitional command made so that the devs could make a breaking change, but now that that is done, its no longer needed

    • Cat_Daddy [any, any]@hexbear.netEnglish
      0·
      7 months ago

      zypper is unironically the best package manager. Absolute s-tier god-mode. It’s slow as hell, but that’s because it makes atomic updates. If the install doesn’t go well, it just rolls it back. I fucking love zypper, and I want to shake the hands of the people responsible for it.

    • Malgas@beehaw.orgEnglish
      0·
      7 months ago
      nix flake update
nix flake check --no-build
git commit -a
nh os switch

      Is the routine I’ve settled into. Flake update because I use flakes, flake check because it’s easier to see any warnings about deprecated options and the like so I can fix them preemptively, git commit after the check to avoid back-to back commits where the second is fixing some issue with the first, and nh because I like the pretty dependency graph and progress bar.

      • NuclearDolphin@lemmy.mlEnglish
        0·
        7 months ago

        Lots of useful stuff here. Taking all of it.

        Does nh use fast-nix-build (or whatever the fancy nix builder CLI is called) to build your system?

        • Malgas@beehaw.orgEnglish
          0·
          7 months ago

          I honestly don’t know how nh works under the hood, but it does seem to do concurrent builds, so it’s probably something like that.