1mo ago

Let's update...

Memes @lemmy.ml

Valso @lemmy.ml

1mo ago

Let's update...

38 comments

OP hasn't used AUR much
- 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.
  
  Or the Linux firmware package change that required manual intervention to resolve.
  
  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.
  
  So THAT’S why it wasn’t working 😭😭😭😭
Break your system and it's broken.
How unexpected!
I saw someone on ml point out that update should come before upgrade
Sauce
- update pulls the metadata about your packages (to see if there are new versions, and which), while upgrade applies the patches.
  
  I've never understood why the update part isn't included in the upgrade command, since upgrade is useless without it
- I thought I remembered that correctly from my time with Ubuntu like 20 years ago.
presses the big blue 'update' button in GNOME Software in Fedora
- Checks 'automatic updates' box in Discover
paru
ujust update
- Isn't that just topgrade
  
  I'm honestly not sure. https://github.com/ublue-os/bazzite/blob/main/system_files/desktop/shared/usr/share/ublue-os/just/10-update.just
  The bazzite motd says use ujust
Yay
- yet another yogurt
- Paru team chiming in 🫡
bash

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.
- 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.
  
  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.
Who the fuck still uses PPA?
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.
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
Do you actually need - Syyu or is - Syu fine? I have only really used the latter.
- 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.
yay
- yes | yay
Y u no pipe yes into apt 🙃

38 comments