You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

204 lines
8.5 KiB

  1. apt (1.8.0~alpha3) unstable; urgency=medium
  2. The PATH for running dpkg is now configured by the option DPkg::Path,
  3. and defaults to "/usr/sbin:/usr/bin:/sbin/:bin". Previous behavior of
  4. not changing PATH may be restored by setting the option to an empty string.
  5. Support for /etc/apt/auth.conf.d/ has been added, see apt_auth.conf(5).
  6. -- Julian Andres Klode <jak@debian.org> Tue, 18 Dec 2018 15:02:11 +0100
  7. apt (1.6~rc1) unstable; urgency=medium
  8. Seccomp sandboxing has been turned off by default for now. If it works
  9. for you, you are encouraged to re-enable it by setting APT::Sandbox::Seccomp
  10. to true.
  11. -- Julian Andres Klode <jak@debian.org> Fri, 06 Apr 2018 14:14:29 +0200
  12. apt (1.6~beta1) unstable; urgency=medium
  13. APT now verifies that the date of Release files is not in the future. By
  14. default, it may be 10 seconds in the future to allow for some clock drift.
  15. Two new configuration options can be used to tweak the behavior:
  16. Acquire::Check-Date
  17. Acquire::Max-DateFuture
  18. These can be overridden in sources.list entries using the check-date
  19. and date-future-max options. Note that disabling check-date also
  20. disables checks on valid-until: It is considered to mean that your
  21. machine's time is not reliable.
  22. -- Julian Andres Klode <jak@debian.org> Mon, 26 Feb 2018 13:14:13 +0100
  23. apt (1.6~alpha1) unstable; urgency=medium
  24. All methods provided by apt except for cdrom, gpgv, and rsh now
  25. use seccomp-BPF sandboxing to restrict the list of allowed system
  26. calls, and trap all others with a SIGSYS signal. Three options
  27. can be used to configure this further:
  28. APT::Sandbox::Seccomp is a boolean to turn it on/off
  29. APT::Sandbox::Seccomp::Trap is a list of names of more syscalls to trap
  30. APT::Sandbox::Seccomp::Allow is a list of names of more syscalls to allow
  31. Also, sandboxing is now enabled for the mirror method.
  32. -- Julian Andres Klode <jak@debian.org> Mon, 23 Oct 2017 01:58:18 +0200
  33. apt (1.5~beta1) unstable; urgency=medium
  34. [ New HTTPS method ]
  35. The default http method now supports HTTPS itself, including encrypted proxies
  36. and connecting to HTTPS sites via HTTPS proxies; and the apt-transport-https
  37. package only provides a "curl+https" method now as a fallback, but will be
  38. removed shortly. If TLS support is unwanted, it can be disabled overall by
  39. setting the option Acquire::AllowTLS to "false".
  40. As for backwards compatibility, the options IssuerCert and SslForceVersion
  41. are not supported anymore, and any specified certificate files must be in the
  42. PEM format (curl might have allowed DER files as well).
  43. [ Changes to unauthenticated repositories ]
  44. The security exception for apt-get to only raise warnings if it encounters
  45. unauthenticated repositories in the "update" command is gone now, so that it
  46. will raise errors just like apt and all other apt-based front-ends do since
  47. at least apt version 1.3.
  48. It is possible (but STRONGLY ADVISED AGAINST) to revert to the previous
  49. behaviour of apt-get by setting the option
  50. Binary::apt-get::Acquire::AllowInsecureRepositories "true";
  51. See apt-secure(8) manpage for configuration details.
  52. [ Release Info Changes ]
  53. If values like Origin, Label, and Codename change in a Release file,
  54. update fails, or asks a user (if interactive). Various
  55. --allow-releaseinfo-change are provided for non-interactive use.
  56. -- Julian Andres Klode <jak@debian.org> Mon, 03 Jul 2017 15:09:23 +0200
  57. apt (1.4.2) unstable; urgency=medium
  58. If periodic updates and unattended upgrades are enabled, the start of
  59. periodic updates are now distributed over 24 hour intervals (as in 1.2
  60. to 1.4), whereas starting unattended-upgrade has been restricted to a
  61. time between 6 and 7 am. This only affects systems using systemd, other
  62. systems still use the classical hourly cron job.
  63. -- Julian Andres Klode <jak@debian.org> Thu, 04 May 2017 22:54:02 +0200
  64. apt (1.4~beta1) unstable; urgency=medium
  65. Support for GPG signatures using the SHA1 or RIPE-MD/160 hash
  66. algorithms has been disabled. Repositories using Release files
  67. signed in such a way will stop working. This change has been made
  68. due to security considerations, especially with regards to possible
  69. further breakthroughs in SHA1 breaking during the lifetime
  70. of this APT release series.
  71. It is possible (but STRONGLY ADVISED AGAINST) to revert to the previous
  72. behaviour by setting the options
  73. APT::Hashes::SHA1::Weak "yes";
  74. APT::Hashes::RIPE-MD/160::Weak "yes";
  75. Note that setting these options only affects the verification of the overall
  76. repository signature.
  77. -- Julian Andres Klode <jak@debian.org> Fri, 25 Nov 2016 13:19:32 +0100
  78. apt (1.2~exp1) experimental; urgency=medium
  79. [ Automatic removal of debs after install ]
  80. After packages are successfully installed by apt(8),
  81. the corresponding .deb package files will be
  82. removed from the /var/cache/apt/archives cache directory.
  83. This can be changed by setting the apt configuration option
  84. "Binary::apt::APT::Keep-Downloaded-Packages" to "true". E.g:
  85. # echo 'Binary::apt::APT::Keep-Downloaded-Packages "true";' \
  86. > /etc/apt/apt.conf.d/01keep-debs
  87. Please note that the behavior of apt-get is unchanged. The
  88. downloaded debs will be kept in the cache directory after they
  89. are installed. To enable the behavior for other tools, you can set
  90. "APT::Keep-Downloaded-Packages" to false.
  91. [ Compressed indices ]
  92. If you use Acquire::gzipIndexes, or any other compressed index targets,
  93. those will now be compressed with the fastest supported algorithm,
  94. currently lz4.
  95. -- Michael Vogt <mvo@debian.org> Tue, 05 Jan 2016 19:22:16 +0100
  96. apt (1.1~exp9) experimental; urgency=medium
  97. A new algorithm for pinning has been implemented, it now assigns a
  98. pin priority to a version instead of assigning a pin to a package.
  99. This might break existing corner cases of pinning, if they use multiple
  100. pins involving the same package name or patterns matching the same
  101. package name, but should overall lead to pinning that actually works
  102. as intended and documented.
  103. -- Julian Andres Klode <jak@debian.org> Mon, 17 Aug 2015 14:45:17 +0200
  104. apt (0.8.11) unstable; urgency=low
  105. * apt-get install pkg/experimental will now not only switch the
  106. candidate of package pkg to the version from the release experimental
  107. but also of all dependencies of pkg if the current candidate can't
  108. satisfy a versioned dependency.
  109. -- David Kalnischkies <kalnischkies@gmail.com> Fri, 03 Dec 2010 14:09:12 +0100
  110. apt (0.7.26~exp3) experimental; urgency=low
  111. * apt-ftparchive now reads the standard configuration files in
  112. /etc/apt/apt.conf and /etc/apt/apt.conf.d.
  113. -- Julian Andres Klode <jak@debian.org> Fri, 26 Mar 2010 15:34:16 +0100
  114. apt (0.7.24) unstable; urgency=low
  115. * Already included in the last version but now with better documentation
  116. is the possibility to add/prefer different compression types while
  117. downloading archive information, which can decrease the time needed for
  118. update on slow machines. See apt.conf (5) manpage for details.
  119. * APT manages his manpage translations now with po4a, thanks to Nicolas
  120. Fran├žois and Kurasawa Nozomu, who also provide the ja translation.
  121. Thanks to Christian Perrier we have already a fr translation and
  122. a few more are hopefully added in the near future.
  123. * This version also introduces some _experimental_ configuration options
  124. to make more aggressive use of dpkg's triggers. If you want to help
  125. testing these _experimental_ options see apt.conf (5) manpage.
  126. -- David Kalnischkies <kalnischkies@gmail.com> Thu, 24 Sep 2009 15:13:16 +0200
  127. apt (0.7.23) unstable; urgency=low
  128. * Code that determines which proxy to use was changed. Now
  129. 'Acquire::{http,ftp}::Proxy[::<host>]' options have the highest priority,
  130. and '{http,ftp}_proxy' environment variables are used only if options
  131. mentioned above are not specified.
  132. -- Eugene V. Lyubimkin <jackyf.devel@gmail.com> Thu, 19 Aug 2009 11:26:16 +0200
  133. apt (0.6.44) unstable; urgency=low
  134. * apt-ftparchive --db now uses Berkeley DB_BTREE instead of DB_HASH.
  135. If you use a database created by an older version of apt, delete
  136. it and allow it to be recreated the next time.
  137. -- Michael Vogt <mvo@debian.org> Wed, 26 Apr 2006 12:57:53 +0200
  138. apt (0.5.25) unstable; urgency=low
  139. * apt-ftparchive --db now uses Berkeley DB version 4.2. If used with a
  140. database created by an older version of apt, an attempt will be made
  141. to upgrade the database, but this may not work in all cases. If your
  142. database is not automatically upgraded, delete it and allow it to be
  143. recreated the next time.
  144. -- Matt Zimmerman <mdz@debian.org> Sat, 8 May 2004 12:38:07 -0700