aconfmgr Sync package DB after updating pacman.conf

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.

Dec 14 '18 15:12 Nils-TUD

See https://github.com/CyberShadow/aconfmgr/issues/23#issuecomment-356178109 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.

Dec 14 '18 15:12 CyberShadow

Any progress on this? Would love to see this, currently I just rerun aconfmgr after an -Syu

Mar 20 '22 15:03 MenacingPerson

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!)

Mar 22 '22 21:03 CyberShadow

I have a lot of projects + a job + other hobbies, sorry!)

Understandable. I would have contributed if I could understand the codebase (It's a big project!)

Mar 23 '22 03:03 MenacingPerson