| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| pacman [2022/07/20 16:58] – archlinux-keyring rjt | pacman [2024/09/15 19:54] (current) – [Maintenance] rjt |
|---|
| === .pacnew === | === .pacnew === |
| |
| There are tools to manage ''.pacnew'' files that are created when core config files are updated FIXME | There are tools to manage ''.pacnew'' files that are created when core config files are updated. |
| | |
| | * [[https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave#Managing_.pac*_files|Managing .pac* files]] |
| |
| I just use [[vim#vimdiff]] to check difference between the current and new files. You could also just use ''vim -d [file] [file]''. ''Ctrl+w [left or right arrow]'' to switch window, btw. | I just use [[vim#vimdiff]] to check difference between the current and new files. You could also just use ''vim -d [file] [file]''. ''Ctrl+w [left or right arrow]'' to switch window, btw. |
| |
| If you get errors about keys (and things like files being corrupt), try updating ''archlinux-keyring'' before doing a full update. EG: (''sudo pacman -Sy archlinux-keyring && sudo pacman -Su''. You might want to chuck that in an alias. | If you get errors about keys (and things like files being corrupt), try updating ''archlinux-keyring'' before doing a full update. EG: (''sudo pacman -Sy archlinux-keyring && sudo pacman -Su''. You might want to chuck that in an alias. |
| | |
| | nbjp [[https://monthly-reports.archlinux.page/2022/07/|Apparently Arch now updates the keyring weekly]]. |
| | |
| | I was getting this error: ''warning: Public keyring not found; have you run 'pacman-key --init'?'' which was mucking up the upgrade process. These steps fixed it: |
| | |
| | - ''sudo rm -r /etc/pacman.d/gnupg'' |
| | - ''sudo pacman-key --init'' |
| | - ''sudo pacman-key --populate archlinux'' |
| | - ''sudo pacman -S archlinux-keyring'' |
| |
| ==== AUR ==== | ==== AUR ==== |
