NEWS 3.9 KB

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