• NorthWestWind@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      7 hours ago

      The only difference is that -Syyu forces the database to update

      To explain what database means in short, it tells pacman what packages are available in different repos (e.g. core, extra). In some rare cases, the time of the database update may be incorrectly marked, and pacman would not know there are new packages/versions. -Syyu should be used in this case.

  • Randelung@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    17 hours ago

    Upgraded three systems to Debian 13 in the last few days. Went without a hitch. One Proxmox, one media server and player, one workstation.

    Wayland still doesn’t work, but that’s apparently because of the noVideo drivers.

  • Laser@feddit.org
    link
    fedilink
    arrow-up
    3
    ·
    22 hours ago

    The second y in Syyu is almost always unneeded and just wastes time and bandwidth. Is i remember correctly, it only makes sense when for example you switch mirrors

    • Eldritch@piefed.world
      link
      fedilink
      English
      arrow-up
      11
      ·
      1 day ago

      You don’t even have to use the aur are to have breaking changes. Most recently they changed how vlc was packaged. And broke it causing a lot of problems for users.

        • Eldritch@piefed.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          57 minutes ago

          Oh wow? You still suffering. In case you haven’t found the solution. Uninstall VLC. Then reinstall all the VLC bits. Now instead of then all bring in one or two packages. There’s tens of then now. MKV support had is own package even.

      • redsand@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 day ago

        That’s pretty rare. I ran arch for years and my only issues were from AUR or trying to update extremely out of date machines.

        • Eldritch@piefed.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 day ago

          I’ve run arch for years as well. It happens nearly yearly. I’ve had updates break completely several times. Partial updates. That required significant manual intervention. Etc Etc Etc. Meanwhile my Debian and fedora systems haven’t had a hitch in years.

            • Eldritch@piefed.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              24 hours ago

              I haven’t installed gentoo in 20 years. I still like arch for it’s glaring flaws. And I do like BSDs ports etc. I probably should go through a gentoo install again to see how it changed. Last time I ran it. Was on a first generation Pentium.

    • bleistift2@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 day ago

      update pulls the metadata about your packages (to see if there are new versions, and which), while upgrade applies the patches.

      • Zwiebel@feddit.org
        link
        fedilink
        English
        arrow-up
        11
        ·
        1 day ago

        I’ve never understood why the update part isn’t included in the upgrade command, since upgrade is useless without it

        • Upgrade will upgrade the system to whatever is newest in your package cache. If, for example, you’ve just performed a partial upgrade and put yourself into an unsupported state, running upgrade without first running update will put your system back in line with itself.

          There probably almost never a reason for this, but its the equivalent of running pacman -u which under normal circumstances you will never do

  • henfredemars@infosec.pub
    link
    fedilink
    English
    arrow-up
    26
    ·
    2 days ago

    Really should keep that PPA use to a minimum. They’re potentially a source of not just instability but possible malware as you’re putting a lot of trust in whoever maintains that resource.

    • thorhop@sopuli.xyz
      link
      fedilink
      arrow-up
      1
      ·
      22 hours ago

      I think Fedora’s COPR carries on the torch, besides Arch’s AUR. But generally, yeah, avoid PPA’s like the plague. It’s been garbage for years now. You’d be better off actually compiling the software yourself.

    • manxu@piefed.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 day ago

      Especially because there is no way to limit the packages installed from a PPA AFAIK. If the PPA has a “new” version of NGINX, or of libc, or of Wayland - you get it, too!!!

      • henfredemars@infosec.pub
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 day ago

        Absolutely. Ideally you should have zero PPAs. There’s definitely a cost for using this feature. Most commonly it comes in the form of instability when you end up with incompatible or broken packages because the maintainer wasn’t playing an active enough role. YMMV!

      • zorro@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 day ago

        You can set packages from a particular repo to a lower priority so that they are only installed when you expressly ask for them

    • jim3692@discuss.online
      link
      fedilink
      arrow-up
      4
      ·
      1 day ago

      When I use Debian/Ubuntu, I prefer installing missing/outdated software from Nix package manager or Flatpaks.

      This way, I can keep a stable core, while being able to enjoy all the latest versions of the apps that I need.

  • jim3692@discuss.online
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    1 day ago
    nix flake update
    nixos-rebuild --switch --flake .
    
    # Just to keep an update history
    git add flake.lock
    git commit -m "update"
    

    This may seem like too much work, but it guarantees an all-or-nothing procedure. If some package is broken, the entire upgrade process is canceled, and the system remains in the state that it was.

    I have had a couple of partial upgrade cases on Arch. It was not fun live booting to repair it, every time this happened.

    • Something Burger 🍔@jlai.lu
      link
      fedilink
      arrow-up
      2
      ·
      1 day ago

      I’ve had updates fail on NixOS. A kernel update didn’t generate the initramfs and the system wouldn’t boot. Booting to a previous generation and reapplying the update fixed it.

      This is very rare, though, and unlike Arch can be fixed without a Live USB.

      • jim3692@discuss.online
        link
        fedilink
        arrow-up
        2
        ·
        1 day ago

        A kernel update didn’t generate the initramfs

        This sounds like a bug on Nix configuration, or the kernel build process.

        If NixOS had caught the error, you wouldn’t have gotten a faulty generation at all. This is different from pacman/apt/dnf, which will happily continue the upgrade, resulting in a broken system with no easy way to fix it.