Resolve config conflicts

System maintenance > Resolve config conflicts

Configuration file conflicts

The system may notify you of conflicting configuration files during or after an update.

It is highly recommended to resolve these conflicts ASAP. Misconfigured or conflicting configs can prevent programs from running properly, and may worsen if left unaddressed.

 # example messages
 warning: /etc/pacman.d/xyz installed as /etc/pacman.d/xyz.pacnew
 
 warning: /etc/pacman.d/abc installed as /etc/pacman.d/abc.pacsave

The eos-pacdiff script is used to resolve these conflicts. It utilizes both the pacdiff utility and meld GUI tools.

Using eos-pacdiff

1. Open a terminal and run:

    $ eos-pacdiff

2. Select V(iew) to compare the config files side-by-side.

3. Review the files for significant changes.

4. R(emove), O(verwrite), or M(erge) the differing lines as necessary.

Tip

It is good practice to create backups of both the original and modified .pacnew and .pacsave files.

FAQs

How does eos-pacdiff work?

eos-pacdiff creates backups for all modes, warns the user not to make rash changes, and calls the below tools to assist the user resolve conflicts:

• pacdiff - A utility tool that allows users to view and merge any changes between the original and .pacnew/.pacsave files.

• meld - A GUI tool that helps users view the comparisons between config files

To run the same process manually, use:

 $ DIFFPROG=meld pacdiff -s

Caution

Do not run this with root permissions! This is a powerful tool that can cause serious damage to system files if used incorrectly.

Refrain from modifying key system files such as /etc/passwd, /etc/group, and /etc/shadow, otherwise you may lock yourself out of your system.

---

Here is an example of how a file comparison looks like in meld:

Image credit: LinuxOpSys - How to use Meld diff tool in Linux

Note

See: pacdiff manpage, diff manpage, meld manpage

---

What are .pacnew and .pacsave files?

These are configuration files that are generated when pacman creates copies of config files and prevents overwrite by appending .pacsave or .pacnew to the filename.

• .pacnew is created during an upgrade to avoid overwriting the existing config file.

• .pacsave is created during package removal (or an upgrade that first requires removal) and the system indicates that it should also be backed up.

Note

See: Pacnew and Pacsave wiki