• vrighter@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    20
    ·
    1 day ago

    always read the news before updates. There was one that said manual intervention was needed, and gave you the exact command you needed to run

    • thevoidzero@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      1
      ·
      1 day ago

      I only read it when I get error like this to know what I shouldn’t do. Is that acceptable? Always checking the news seems superfluous because most times it goes smoothly, and packman will fail and let you know if it can’t do something.

      • ThotDragon@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        1
        ·
        1 day ago

        I use this approach and there’s never been an unrecoverable situation over the decade plus I’ve used Arch Linux.

      • Tenkard@lemmy.ml
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 day ago

        I’ve learnt to check the endeavouros forum before a kernel update (normal updates are fine), it can save you from having to chroot and tweak stuff… It takes 5 minutes to check against 2 hours to fix

        • thevoidzero@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          20 hours ago

          Interesting. I’ve never had anything serious than updating keyring and removing before reinstalling packages. Pacman hasn’t failed me enough to need more than

          • error msg is obvious (like keyring), conflicts, fix it
          • if not check archlinux.org, follow fix from there,
          • new problem I need to search, mostly happens because I haven’t learned about it. Like first time I came across keyring problem.