NEWS 4.0 KB

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