diff options
Diffstat (limited to 'debian/NEWS')
| -rw-r--r-- | debian/NEWS | 96 |
1 files changed, 96 insertions, 0 deletions
diff --git a/debian/NEWS b/debian/NEWS new file mode 100644 index 000000000..934391456 --- /dev/null +++ b/debian/NEWS @@ -0,0 +1,96 @@ +apt (1.2~exp1) experimental; urgency=medium + + [ Automatic removal of debs after install ] + After packages are successfully installed by apt(8), + the corresponding .deb package files will be + removed from the /var/cache/apt/archives cache directory. + + This can be changed by setting the apt configuration option + "Binary::apt::APT::Keep-Downloaded-Packages" to "true". E.g: + + # echo 'Binary::apt::APT::Keep-Downloaded-Packages "true";' \ + > /etc/apt/apt.conf.d/01keep-debs + + Please note that the behavior of apt-get is unchanged. The + downloaded debs will be kept in the cache directory after they + are installed. To enable the behavior for other tools, you can set + "APT::Keep-Downloaded-Packages" to false. + + [ Compressed indices ] + If you use Acquire::gzipIndexes, or any other compressed index targets, + those will now be compressed with the fastest supported algorithm, + currently lz4. + + -- Michael Vogt <mvo@debian.org> Tue, 05 Jan 2016 19:22:16 +0100 + +apt (1.1~exp9) experimental; urgency=medium + + A new algorithm for pinning has been implemented, it now assigns a + pin priority to a version instead of assigning a pin to a package. + + This might break existing corner cases of pinning, if they use multiple + pins involving the same package name or patterns matching the same + package name, but should overall lead to pinning that actually works + as intended and documented. + + -- Julian Andres Klode <jak@debian.org> Mon, 17 Aug 2015 14:45:17 +0200 + +apt (0.8.11) unstable; urgency=low + + * apt-get install pkg/experimental will now not only switch the + candidate of package pkg to the version from the release experimental + but also of all dependencies of pkg if the current candidate can't + satisfy a versioned dependency. + + -- David Kalnischkies <kalnischkies@gmail.com> Fri, 03 Dec 2010 14:09:12 +0100 + +apt (0.7.26~exp3) experimental; urgency=low + + * apt-ftparchive now reads the standard configuration files in + /etc/apt/apt.conf and /etc/apt/apt.conf.d. + + -- Julian Andres Klode <jak@debian.org> Fri, 26 Mar 2010 15:34:16 +0100 + +apt (0.7.24) unstable; urgency=low + + * Already included in the last version but now with better documentation + is the possibility to add/prefer different compression types while + downloading archive information, which can decrease the time needed for + update on slow machines. See apt.conf (5) manpage for details. + * APT manages his manpage translations now with po4a, thanks to Nicolas + François and Kurasawa Nozomu, who also provide the ja translation. + Thanks to Christian Perrier we have already a fr translation and + a few more are hopefully added in the near future. + * This version also introduces some _experimental_ configuration options + to make more aggressive use of dpkg's triggers. If you want to help + testing these _experimental_ options see apt.conf (5) manpage. + + -- David Kalnischkies <kalnischkies@gmail.com> Thu, 24 Sep 2009 15:13:16 +0200 + +apt (0.7.23) unstable; urgency=low + + * Code that determines which proxy to use was changed. Now + 'Acquire::{http,ftp}::Proxy[::<host>]' options have the highest priority, + and '{http,ftp}_proxy' environment variables are used only if options + mentioned above are not specified. + + -- Eugene V. Lyubimkin <jackyf.devel@gmail.com> Thu, 19 Aug 2009 11:26:16 +0200 + +apt (0.6.44) unstable; urgency=low + + * apt-ftparchive --db now uses Berkeley DB_BTREE instead of DB_HASH. + If you use a database created by an older version of apt, delete + it and allow it to be recreated the next time. + + -- Michael Vogt <mvo@debian.org> Wed, 26 Apr 2006 12:57:53 +0200 + +apt (0.5.25) unstable; urgency=low + + * apt-ftparchive --db now uses Berkeley DB version 4.2. If used with a + database created by an older version of apt, an attempt will be made + to upgrade the database, but this may not work in all cases. If your + database is not automatically upgraded, delete it and allow it to be + recreated the next time. + + -- Matt Zimmerman <mdz@debian.org> Sat, 8 May 2004 12:38:07 -0700 + |