]> git.saurik.com Git - apt.git/blob - debian/NEWS
http: skip connection cleanup if we close it anyhow
[apt.git] / debian / NEWS
1 apt (1.2~exp1) experimental; urgency=medium
2
3 [ Automatic removal of debs after install ]
4 After packages are successfully installed by apt(8),
5 the corresponding .deb package files will be
6 removed from the /var/cache/apt/archives cache directory.
7
8 This can be changed by setting the apt configuration option
9 "Binary::apt::APT::Keep-Downloaded-Packages" to "true". E.g:
10
11 # echo 'Binary::apt::APT::Keep-Downloaded-Packages "true";' \
12 > /etc/apt/apt.conf.d/01keep-debs
13
14 Please note that the behavior of apt-get is unchanged. The
15 downloaded debs will be kept in the cache directory after they
16 are installed. To enable the behavior for other tools, you can set
17 "APT::Keep-Downloaded-Packages" to false.
18
19 [ Compressed indices ]
20 If you use Acquire::gzipIndexes, or any other compressed index targets,
21 those will now be compressed with the fastest supported algorithm,
22 currently lz4.
23
24 -- Michael Vogt <mvo@debian.org> Tue, 05 Jan 2016 19:22:16 +0100
25
26 apt (1.1~exp9) experimental; urgency=medium
27
28 A new algorithm for pinning has been implemented, it now assigns a
29 pin priority to a version instead of assigning a pin to a package.
30
31 This might break existing corner cases of pinning, if they use multiple
32 pins involving the same package name or patterns matching the same
33 package name, but should overall lead to pinning that actually works
34 as intended and documented.
35
36 -- Julian Andres Klode <jak@debian.org> Mon, 17 Aug 2015 14:45:17 +0200
37
38 apt (0.8.11) unstable; urgency=low
39
40 * apt-get install pkg/experimental will now not only switch the
41 candidate of package pkg to the version from the release experimental
42 but also of all dependencies of pkg if the current candidate can't
43 satisfy a versioned dependency.
44
45 -- David Kalnischkies <kalnischkies@gmail.com> Fri, 03 Dec 2010 14:09:12 +0100
46
47 apt (0.7.26~exp3) experimental; urgency=low
48
49 * apt-ftparchive now reads the standard configuration files in
50 /etc/apt/apt.conf and /etc/apt/apt.conf.d.
51
52 -- Julian Andres Klode <jak@debian.org> Fri, 26 Mar 2010 15:34:16 +0100
53
54 apt (0.7.24) unstable; urgency=low
55
56 * Already included in the last version but now with better documentation
57 is the possibility to add/prefer different compression types while
58 downloading archive information, which can decrease the time needed for
59 update on slow machines. See apt.conf (5) manpage for details.
60 * APT manages his manpage translations now with po4a, thanks to Nicolas
61 François and Kurasawa Nozomu, who also provide the ja translation.
62 Thanks to Christian Perrier we have already a fr translation and
63 a few more are hopefully added in the near future.
64 * This version also introduces some _experimental_ configuration options
65 to make more aggressive use of dpkg's triggers. If you want to help
66 testing these _experimental_ options see apt.conf (5) manpage.
67
68 -- David Kalnischkies <kalnischkies@gmail.com> Thu, 24 Sep 2009 15:13:16 +0200
69
70 apt (0.7.23) unstable; urgency=low
71
72 * Code that determines which proxy to use was changed. Now
73 'Acquire::{http,ftp}::Proxy[::<host>]' options have the highest priority,
74 and '{http,ftp}_proxy' environment variables are used only if options
75 mentioned above are not specified.
76
77 -- Eugene V. Lyubimkin <jackyf.devel@gmail.com> Thu, 19 Aug 2009 11:26:16 +0200
78
79 apt (0.6.44) unstable; urgency=low
80
81 * apt-ftparchive --db now uses Berkeley DB_BTREE instead of DB_HASH.
82 If you use a database created by an older version of apt, delete
83 it and allow it to be recreated the next time.
84
85 -- Michael Vogt <mvo@debian.org> Wed, 26 Apr 2006 12:57:53 +0200
86
87 apt (0.5.25) unstable; urgency=low
88
89 * apt-ftparchive --db now uses Berkeley DB version 4.2. If used with a
90 database created by an older version of apt, an attempt will be made
91 to upgrade the database, but this may not work in all cases. If your
92 database is not automatically upgraded, delete it and allow it to be
93 recreated the next time.
94
95 -- Matt Zimmerman <mdz@debian.org> Sat, 8 May 2004 12:38:07 -0700
96