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.

234 lines
9.8 KiB

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