apt Conffile Conflict

Lifeboat uses the apt package manager to install and update software on the server. If a conffile conflict occurs, Lifeboat is unable to resolve it automatically. Manual intervention is required to prevent a malfunction.

When the conflict occurs Lifeboat exits and the apt process is interrupted. Lifeboat will be unable to operate apt until things are cleared up.

  1. Connect to the server with SSH
  2. Run the command sudo apt upgrade to perform updates

If apt was interrupted this message will appear:

E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

When this happens, repair the upgrade to correct the problem.

sudo dpkg --configure -a

In rare cases, this may not be necessary and the upgrade procedure will continue to the conflict.

When the upgrade procedure runs into the conffile conflict this message will appear:

Configuration file '{path/to/file}'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** {file} (Y/I/N/O/D/Z) [default=N] ? 

Press D then return / enter to review the differences if desired. Press N then return / enter to keep the current local version as-is. For most cases, this is the best solution.

When the upgrade procedure is complete, Lifeboat will be able to operate apt once again.

To ensure all software is installed, updated, and operating correctly Lifeboat should perform the install procedure again. To make Lifeboat perform the install procedure again, delete the LifeboatReport.sh file.

rm ~/.com.strawberrysw.Lifeboat/LifeboatReport.sh

Now connect with Lifeboat and perform the install procedure. Existing server configuration should be in place, and when Lifeboat completes the install process the problem is resolved.

Assistance is available for licensed users