The grub-install command you propose should be adequate for your needs;
It’s easy to make errors in judgement, especially in the wee hours; I’m sure nobody is exempt from that. Easier still, is to make an unprovoked personal attack such as you have now demonstrated; and in such a petty manner; however, I’m willing to overlook it.
As it happens, I am generally observant of indicators.
For example:
The removal of the community repo was documented in the respective Update Announcement at the time - so long ago, in fact, that it is no longer listed under recent announcements;
The community repository has been merged into extra and is now empty
The Arch git migration is now complete .
The [community] repository has been merged into [extra] and is now empty.
It may take a bit of time for mirrors to catch up (more details here).
Update your system and handle the pacman
sudo pacman -Syu "pacman>=6.0.2-11"
In order to remove the defunct [community] repo changes must be made to /etc/pacman.conf.
Changes will be provided in a file with the extension .pacnew.
Pacman provides the utility pacdiff to manage these files and will use vim -d for comparison if the environment variable DIFFPROG is not set.
pacdiff -s
If you would like to use a different comparison tool you may prepend the env var:
DIFFPROG=meld pacdiff -s
Then sync with the repositories again:
sudo pacman -Syu
And you can also remove the now unused repository.
sudo pacman -Sc
NOTE: Be aware that this last command will also remove all packages in the pacman cache that are not currently installed: in other words, backup copies of packages that you have uninstalled at some point will no longer be stored on your hard drive.
In most cases, this probably will not cause headaches. To prevent even minor aches and pains, see the Arch Wiki for information on cleaning the cache
As it happens this issue had a comparatively easy fix, which was provided via a pacnew file for you to carefully merge with the existing file.
- See System Maintenance for more information.
Failure to correct that issue could simply be an oversight, however, it can also be indicative of a disregard and/or ignorance of system maintenance.
This is common among (particularly newer) users who make an assumption that performing an update equates to system maintenance, and nothing else needs to be done; or, if they take an entitled stance that they should not have to do that !@#$%, which happens more often than one might reasonably expect.
Gladly. Though, to be clear, not because you so eloquently request it.