• hperrin@lemmy.caEnglish
    442·
    14 days ago

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

    • Glifted@lemmy.world
      17·
      14 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

  • Matriks404@lemmy.world
    22·
    14 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.

  • Comrade_Squid@lemmy.ml
    6·
    14 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.

  • Zanka@lemmy.ml
    5·
    14 days 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.

    • zewm@lemmy.worldEnglish
      1·
      14 days 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.

    • seralth@lemmy.worldEnglish
      1·
      13 days ago

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

    • JackbyDev@programming.devEnglish
      1·
      13 days 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.

    • Valso@lemmy.mlOP
      1·
      12 days 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. 🤣

    • ragas@lemmy.ml
      31·
      14 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·
        13 days 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.

  • PieMePlenty@lemmy.world
    4·
    14 days ago

    Never had an update break on headless Debian. Even when switching from 12 to 13. That shit is solid.
    I’m getting used to arch on my main desktop and I still can’t figure out why the hell “sync” is the wording pacman uses for updating or why ‘y’ is refresh. Sync refresh upgrade my ass. I will admin, it is fast.

    • hperrin@lemmy.caEnglish
      1·
      14 days ago

      Because you’re “sync”ing with the state of the repo. You’re not necessarily upgrading. Sometimes the repos have a lower version than what you have, so you would be downgrading in that case. Or sometimes you’re just using it to install a new package and its dependencies.

      -u is upgrade. And -uu is upgrade or downgrade. It’s used to filter the packages that sync operates on, so basically you’re syncing any packages that have a different version than the repo.

      -y for refresh? No idea. -r is root, so I guess it was already in use by the time someone added refresh?