• Matriks404@lemmy.world
    37·
    25 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·
      25 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·
      25 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

    • seralth@lemmy.worldEnglish
      3·
      24 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
      3·
      24 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·
      23 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. 🤣

    • BunScientist@lemmy.zipEnglish
      1·
      24 days 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

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

      • Ephera@lemmy.mlEnglish
        2·
        25 days 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
      4·
      25 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.

  • PieMePlenty@lemmy.world
    14·
    25 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
      2·
      25 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?

    • Brahvim Bhaktvatsal@lemmy.kde.socialisiZulu
      2·
      25 days ago

      I did it on the GUI all day yesterday! The only problem Debian has is being unbreakable!

      Heck, I switched repos from bookworm to trixie and installed 3 GiB worth of packages - 2.5k packages - and booted into a PERFECTLY WORKING system!

      Installed the other 8 GiB afterwards and booted into a perfectly working system. Just before I thought Steam was broken, I rebooted and it came alive too.

      And my GTX 1650 worked right away! Do you know how many times the daily 1 GiB update on Ubuntu breaks that?!

      Flatpak updates are kinda’ slow, no 4 GiB downloads needed per day, Debian updates arrive at like 200 MiB a month except for apps like VSCode, Signal, or Discord. And - to be honest - that’s the Windows-unlike experience every distro is missing.

      Debian really is unbreakable.

    • Cat_Daddy [any, any]@hexbear.netEnglish
      4·
      25 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.

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

  • Cat_Daddy [any, any]@hexbear.netEnglish
    9·
    25 days 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.

      • Cat_Daddy [any, any]@hexbear.netEnglish
        8·
        25 days 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.

    • deadcade@lemmy.deadca.de
      2·
      24 days 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.

    • Malgas@beehaw.orgEnglish
      3·
      25 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·
        24 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·
          24 days 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.

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