You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was using aconfmgr to apply my system configuration to another machine and ran into the problem that a package from another repository couldn't be found. This occurs because I also do a CopyFile /etc/pacman.conf, which happens right before in the "Installing priority files" step and adds a new repository. But the package database is not updated afterwards, so that pacman cannot find the package.
I fixed the problem by doing a pacman --sync --refresh after the installation of the priority files. If you like, I can create a PR.
The text was updated successfully, but these errors were encountered:
See #23 (comment) for some discussion on aconfmgr automatically updating package repositories.
I think prompting the user whether they'd like to sync repositories if the pacman configuration was updated (ideally, specifically, the list of repositories) would be a good change.
New features can be added to aconfmgr as soon as either someone contributes a pull request or when I'm able to allocate a time window to work on aconfmgr enhancements (which can be many months apart - I have a lot of projects + a job + other hobbies, sorry!)
I was using aconfmgr to apply my system configuration to another machine and ran into the problem that a package from another repository couldn't be found. This occurs because I also do a
CopyFile /etc/pacman.conf
, which happens right before in the "Installing priority files" step and adds a new repository. But the package database is not updated afterwards, so that pacman cannot find the package.I fixed the problem by doing a
pacman --sync --refresh
after the installation of the priority files. If you like, I can create a PR.The text was updated successfully, but these errors were encountered: