"Fossies" - the Fresh Open Source Software Archive

Member "apt-1.8.2/debian/NEWS" (28 May 2019, 8748 Bytes) of package /linux/misc/apt-1.8.2.tar.gz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. See also the latest Fossies "Diffs" side-by-side code changes report for "NEWS": 1.8.1_vs_1.8.2.

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