Arch is different…

    • diaphragmwp@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      40
      ·
      edit-2
      15 hours ago

      News from this year:

      • virtualbox-ext-vnc >= 7.2.12-2 requires manual intervention (package won’t install)
      • Active AUR malicious packages incident (the AUR is locked)
      • Arch Linux 2026 Leader Election Results
      • Breaking changes for all users of varnish, which is renamed to vinyl-cache (it’s a proxy, only affects servers)
      • kea >= 1:3.0.3-6 update requires manual intervention (dhcp server, affects routers)
      • iptables now defaults to the nft backend (affects pretty much nothing)

      Repost.

      Also, my Mint install broke, uh, shit I don’t remember, 5 times? Arch broke zero times. Zero times not my own fault for forgetting I was installing something and shutting off the computer, of course. Except for the times I tried the fucking installer python script, but since I never even booted the install it doesn’t count.

      • silasmariner@programming.dev
        link
        fedilink
        arrow-up
        3
        ·
        3 hours ago

        Iptables change actually fucked me because I’d tweaked something stupid 12 years ago and forgot. Took lime 45-60 mins to fix

      • Kabutor@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        5
        ·
        7 hours ago

        I dont get the bad press arch got. I use arch (btw) and can’t remember last time it wont boot after an update. It maybe happened to me twice in 20 years and at least once was my fault and the other was because i didn’t read the pacman post warning me

        • silasmariner@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          3 hours ago

          Once it happened to me because 6 years prior I’d made a change thinking ‘hah. That makes more sense’ and then things changed under me and I had to read journalctl in a tty. Low key enjoyed dealing with it. But here’s the thing: most ppl are dead at that point. No idea what to do. Arch is for nerds.

      • hirihit640@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        6
        ·
        9 hours ago

        Mint broke for you? That’s the first I’ve heard of it.

        Also if you have a habit of shutting down the PC during updates, check out atomic/immutable distros. They are almost impossible to break. You can pull the power during an update and it’ll be fine.

    • kolmaskommentoija@sopuli.xyz
      link
      fedilink
      arrow-up
      7
      ·
      13 hours ago

      Reminds me of my try of Nobara. I do clean install, it installs and starts updating itself for a long while. Afterwards it tells me to reboot, and that the update has failed. I am??? Since I am a noob, so I reboot. And the whole system fully breaks, and no trouble-shooting helps, so I have to re-install. No biggie, just mildly annoying, it was a clean install after all. Then I do some searching to figure out, what went wrong, and find out, that updates failing and the system fully breaking, and having to re-install it if you reboot, is apparently normal behavior for Nobara.

      • sunnyjim@lemmy.zip
        link
        fedilink
        arrow-up
        4
        ·
        12 hours ago

        I’ve had Nobara on my PC for several years and not had a problem, though I know others have

        Having said that, if I could be bothered I would probably just return to regular Fedora again so that I could have a decent package manager and updater…