• pewpew@feddit.it
    2·
    2 hours ago

    That’s because you have to use

    apt

    , not apt-get. Yes, there is a difference

  • ☂️-@lemmy.ml
    173·
    2 days ago

    until a pacman update breaks your system because you didn’t read the release notes telling you it needed manual intervention beforehand 🤣

    • Valso@lemmy.mlOP
      1·
      15 hours ago

      Been using Arch since 2019, that has never happened to me. Apparently it’s all about the device behind the keyboard, not about pacman. 🤣

    • BunScientist@lemmy.zipEnglish
      1·
      1 day ago

      Every time there’s been need for manual intervention the update just fails, I check the news to do the thing, then update as usual

    • JackbyDev@programming.devEnglish
      3·
      1 day ago

      I use informant which in theory fixed this but even then there is an issue on it about some things happening earlier in pacman than the transaction hook it uses so… Bleh. This shit needs to be built into pacman itself, seriously.

    • seralth@lemmy.worldBanned from communityEnglish
      3·
      2 days ago

      That’s happened like once in the last 3 years and the notice was right in pacman before you accepted.

    • poweruser@lemmy.sdf.orgEnglish
      1·
      1 day 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)

  • Matriks404@lemmy.world
    271·
    2 days 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
      6·
      2 days 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
      2·
      2 days 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

  • hperrin@lemmy.caEnglish
    331·
    3 days ago

    And yet I’ve never had an apt upgrade break my whole system.

    • Glifted@lemmy.world
      11·
      3 days ago

      Yeah, maybe I’m just not smart enough but I always have the best luck with Debian/Ubuntu style distros. I’m glad Arch users are happy with Arch, it just doesn’t work for me

    • Devconsole@sh.itjust.worksEnglish
      1·
      2 days ago

      Agreed. I ran a system upgrade at home and then went to a coffee shop. My machine didn’t boot at the coffee shop. I installed Fedora instead of doing what I had gone there to do

      • hperrin@lemmy.caEnglish
        8·
        3 days ago

        Unable to boot after the update. That’s happened to me multiple times with pacman, so I eventually switched to Fedora.

  • Comrade_Squid@lemmy.ml
    10·
    2 days ago

    Using Debian as my main laptop distro, I am usually an arch user but figured with it being a light weight laptop I wouldn’t need arch, its been fine but installing updates can be frustrating, after a few weeks gnomes appstore breaks, then I need to use terminal to apt update, apt --fix-broken install.

    • Hirom@beehaw.org
      5·
      2 days ago

      Which Debian distribution are you using, stable, testing, unstable?

      I take care of a couple machines for family members. Those have Debian stable with automatic update (unattended-upgrade). I can’t recall the system or packages ever breaking. At most users are a bit confused when an update change the UI a bit.

      Sticking to stable and avoiding third party repos gives a pretty solid system. Only developers or sysadmins might consider Debian testing. Only people working on Debian itself should use unstable.

    • ragas@lemmy.ml
      31·
      2 days ago

      sudo emerge -avuDUg world

      –changed-use, -U:

      • Tells emerge to include installed packages where USE flags have changed since installation. This option also implies the –selective option. Unlike –newuse, the –changed-use option does not trigger reinstallation when flags that the user has not enabled are added or removed.

      –getbinpkg [ y | n ], -g:

      • Using the server and location defined in PORTAGE_BINHOST (see make.conf(5)), portage will download the information from each binary package found and it will use that information to help build the dependency list. This option implies -k. (Use -gK for binary-only merging.)
      • Heavybell@lemmy.worldEnglish
        1·
        1 day ago

        Yeah, I used to use -U but I prefer -N personally. I like the system to be consistent with what it would be from a fresh build.

    • Cat_Daddy [any, any]@hexbear.netEnglish
      41·
      2 days 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
      3·
      2 days 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
        1·
        2 days 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
          1·
          1 day 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.