Skip to main content
added 1 character in body
Source Link
Rui F Ribeiro
  • 58k
  • 28
  • 156
  • 237

When upgrading packages in Debian, often when files were edited, the package manager creates extra files as in:

/etc/default/grub.ucfdpkg-dist  
/etc/mysql/my.cnf.dpkg-dist

More rarely, those files can create problems when upgrading production servers.

I do not feel that is a particular good solution deleting them by hand or using scripts. Is there any dpkg configuration where their creation can be forbidden?

When upgrading packages in Debian, often when files were edited, the package manager creates extra files as in:

/etc/default/grub.ucf-dist  
/etc/mysql/my.cnf.dpkg-dist

More rarely, those files can create problems when upgrading production servers.

I do not feel that is a particular good solution deleting them by hand or using scripts. Is there any dpkg configuration where their creation can be forbidden?

When upgrading packages in Debian, often when files were edited, the package manager creates extra files as in:

/etc/default/grub.dpkg-dist  
/etc/mysql/my.cnf.dpkg-dist

More rarely, those files can create problems when upgrading production servers.

I do not feel that is a particular good solution deleting them by hand or using scripts. Is there any dpkg configuration where their creation can be forbidden?

Source Link
Rui F Ribeiro
  • 58k
  • 28
  • 156
  • 237

debian dpkg-dist files after apt upgrade

When upgrading packages in Debian, often when files were edited, the package manager creates extra files as in:

/etc/default/grub.ucf-dist  
/etc/mysql/my.cnf.dpkg-dist

More rarely, those files can create problems when upgrading production servers.

I do not feel that is a particular good solution deleting them by hand or using scripts. Is there any dpkg configuration where their creation can be forbidden?