Author: Richard Language: text
Description: Arch Update Catch-Up Tips Timestamp: 2019-12-04 18:58:43 +0000
View raw paste Reply
  1. I'm a few episodes behind, but in 327 was a rant about Arch being hard to upgrade if not kept up with.   There is a pretty safe, but long way to bring Arch up to speed using short incremental upgrades based on dates.
  3. You can slowly apply back patches to Arch Linux and not apply months worth at a single time.  You can edit the Repo's to specific dates, say 2 weeks out from last time you updated:
  5. Example:
  7. $ sudo cp /etc/pacman.conf /etc/pacman.conf.bak
  8. $ sudo vi /etc/pacman.conf
  9. Replace the existing contents with the following lines:
  11. [core]
  12. SigLevel = PackageRequired
  13. Server=$repo/os/$arch
  15. [extra]
  16. SigLevel = PackageRequired
  17. Server=$repo/os/$arch
  19. [community]
  20. SigLevel = PackageRequired
  21. Server=$repo/os/$arch
  24. Save & Exit.   Update system via pacman as usual to apply upgrades, reboot, test. When ready progress another 2 weeks.  If it goes smooth try 1 month out.  Find a problem go back 1 week.   If you get stuck, should be to google the message / change you are stuck on.
  26. Once you are caught up, you can restore the pacman.conf file back to normal.  If you are not sure when pacman was last run, just look at the timestamp of the log file:
  28. $ ls -l /var/log/pacman.log
  29. -rw-r--r-- 1 root root 3214658 Nov 30 10:40 /var/log/pacman.log
  32. Also for the nervous updater: the program "informant" in AUR prevents you from upgrading if there is fresh Arch News that you have not read since the last update ran.
  34. My base arch is still Antergos back from your Arch challenge, and I waited a while before attempting it.
  36. $ sudo tune2fs -l /dev/sda3 | grep 'Filesystem created'
  37. Filesystem created:       Tue Mar 29 15:19:02 2016
View raw paste Reply