Add -o Acquire::ForceIPv4=true
when running apt-get
.
If you want to make the setting persistent just create /etc/apt/apt.conf.d/99force-ipv4 and put Acquire::ForceIPv4 "true";
in it:
echo 'Acquire::ForceIPv4 "true";' | sudo tee /etc/apt/apt.conf.d/99force-ipv4
Config options Acquire::ForceIPv4
and Acquire::ForceIPv6
were added to version 0.9.7.9~exp1 (see bug 611891) which is available since Ubuntu Saucy (released in October 2013) and Debian Jessie (released in April 2015).
If you have customized the package/software at all, either by editing the config files directly, or via a GUI, you may want to keep your customizations. Usually in Unix/Linux systems, configurations are saved in text files, even if the configuration/customization is done via the GUI.
Each Debian binary deb package has a list of files which it identifies as config files. dpkg
, and thus apt
honor this identification when removing packages, and also on upgrades. By default apt/dpkg
will not remove config files on package removal. You have to request a purge. On upgrade it will ask you to choose between the current version and the new version (if they differ) before overwriting config files. Even in that case, it saves a copy of the original file. Here Debian is trying to help you, based on the assumption that your config files may contain valuable information.
So, if you have not configured the package, or you don't want to keep your configurations, you can use apt-get purge
.
If you do keep the config files, then if/when you reinstall the package, Debian will attempt to reuse the saved configuration information. If the version of the package you are trying to (re)install has config files that conflict with the configuration files that are already installed, it will again ask you before overwriting, as it does on upgrade.
Minor comment: If you have removed the package and later want to remove the config files,it used to be the case that apt
would not remove the config files if the package was not installed. However, for some years now, running apt-get purge
will remove config files even if the package is no longer installed.
This was fixed in the 0.8.0~pre1
version of apt, released on Fri, 13 Aug 2010, or possibly in the 0.8.15~exp1
version of apt, released Fri, 10 Jun 2011. See Debian Bug Report: apt-get --purge does not work as expected, dated 24th June 2002.
Best Answer
apt
is the recommended command for interactive use by administrators, not for use in shell scripts.This is addressed to a large extent in the
apt
manpage:Thus:
apt
doesn’t have a stable CLI interface to allow breaking changes, if they’re deemed beneficial.You can’t, the tool is explicitly not designed for this.
Use
apt-get
orapt-cache
in your scripts to avoid the error message.