this post was submitted on 08 Feb 2025
388 points (97.1% liked)

linuxmemes

22397 readers
2170 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] superkret@feddit.org 37 points 3 days ago (3 children)

    It does it automatically.
    But make sure to read the Arch news before every update, especially when it's a lot of packages. Something big like a new KDE Release might require minor manual intervention.

    [–] BuboScandiacus@mander.xyz 37 points 3 days ago* (last edited 3 days ago) (2 children)

    I'm more of an "update first, care later" type of person

    And it works great, 100% recommended to newbies

    Oh and make a separate home partition, just in case

    [–] acockworkorange@mander.xyz 5 points 3 days ago

    Live fast and die young 🀘

    [–] Petter1@lemm.ee 1 points 2 days ago (2 children)

    No separate home needed, just save important files in your nextcloud server

    [–] bestboyfriendintheworld@sh.itjust.works 1 points 1 day ago (1 children)

    A separate harddrive for backups is lost technology apparently.

    [–] Petter1@lemm.ee 1 points 18 hours ago
    [–] BuboScandiacus@mander.xyz 2 points 2 days ago

    The server runs arch too x)

    [–] omgitsaheadcrab@sh.itjust.works 15 points 3 days ago (1 children)

    I've literally only read the news the 1 or 2 times there was a breaking change during an update. Blindly updating (non-AUR) has served me fine for over 10 years

    [–] somenonewho@feddit.org 2 points 3 days ago (1 children)

    Well everyone's milage may vary. I have set up informant some time ago so I'm forced to read the news on updates. But much more importantly I've ignored .pacnew files for years till it bit me in the ass when a Pam config file change broke my login so now I'm not ignoring.pacnew but merging them every update.

    [–] Kyouki@lemmy.world 1 points 3 days ago (2 children)

    Oh.. Ohno

    How safe is merging them?

    [–] somenonewho@feddit.org 2 points 2 days ago (1 children)

    As the other commenter said I use a diff tool (I use vimdiff but meld probably works easiest if your not used to vim). I do a pacdiff after every upgrade that will prompt you for all the changed files (most of the times there are none or the changes are minor) and let you compare your version and the .pacnew file. If anything changes in the syntax in a major way (which it almost never does) you will should spot these differences and be able to amend any changes you made in that way.

    The example I gave was when some pam config file syntax changed and since I had a custom pam config (because of an encrypted home) it didn't update the syntax (creating a pacnew file) then I couldn't login after reboot.

    [–] Kyouki@lemmy.world 1 points 2 days ago
    [–] kuberoot@discuss.tchncs.de 3 points 3 days ago (1 children)

    I would recommend doing it manually - you can get a GUI diff tool (I like Meld), run it with both the normal file and pacnew, and merge every change from the pacnew into the main file.

    [–] Kyouki@lemmy.world 1 points 3 days ago

    I've been using topgrade as of late and was worried it would break my files. Have to check what it changes specifically.

    Always when it prompt me, been ignoring it for now as one of the files is my rc files that gets changed.

    Thank you

    [–] Petter1@lemm.ee 1 points 2 days ago

    I just update, never had an issue.

    Just read the output of yay/pacman and you’ll be fine.