Arch is different...

you are viewing a single comment's thread
view the rest of the comments
[–] 51 points 5 days ago* (last edited 5 days ago) (6 children)

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.

  • source
  • parent
  • hideshow 12 child comments
  • [–] 15 points 5 days ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 5 days ago (1 child)

    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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 5 days ago* (last edited 4 days 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.

    Edit: this is a completely different thing. I had two issues.

  • source
  • parent
  • [–] 2 points 4 days ago (2 children)

    this year

    And one post earlier (2025-12-20) that the image likely could be about:

    NVIDIA 590 driver drops Pascal and lower support

    Install nvidia-580xx-dkms from the AUR

    Impact: Updating the NVIDIA packages [without manually changing to AUR packages] on systems with Pascal, Maxwell, or older cards will fail to load the driver, which may result in a broken graphical environment.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 5 days ago* (1 child)

    Active AUR malicious packages incident (the AUR is locked)

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 4 days ago (1 child)

    To be fair, adoption as a concept is the problem not the actual aur.

    The fundamentals of the aur was fine though that entire ordeal. It's just one optional choice layered on top that wasn't

    Blaming the aur fundamentally for that choice is like blaming the city planner for when a idiot turns down the wrong way on a one way street.

    We kinda just accepted the risk because the upsides were worth it. But some people are assholes and gotta ruin it for everyone.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 4 days ago

    This isn't the first type of problem that the AUR has had. A few years ago it had problems staying up, because it had no scalability to speak of.

    "Best hopes and wishes" is not an accepted engineering design strategy. If something can be abused, it will be. Not planning for it is just that, poor planning.

    The AUR has been poorly put together and this wave of malware is just another symptom of a deeper problem.

  • source
  • parent