[Bug 1702326] Please test proposed package

[Timo Aaltonen]

Hello Julian, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.25 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1702326

Title:
  New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Zesty:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  This is a new upstream micro release for the first point release of Debian stretch. Some of the changes are in 1.2.25 as well, but 1.2.25 also includes changes from 1.4.8 which have their own LP bugs.

  apt (1.4.7) stretch; urgency=medium

    [ Robert Luberda ]
    * fix a "critical" typo in old changelog entry (Closes: 866358)
  => Remove a letter, and fixes some tool

    [ David Kalnischkies ]
    * use port from SRV record instead of initial port
  => Might have picked the wrong port

    [ Julian Andres Klode ]
    * Reset failure reason when connection was successful
  => Some failures were only treated as warnings, not errors

    * debian/gbp.conf: Set debian-branch to 1.4.y
  => Building ...

    * http: A response with Content-Length: 0 has no content

  => Downloading failed if server responded with Content-Length: 0, as
     APT was waiting for content to read.

   -- Julian Andres Klode <jak at debian.org>  Tue, 04 Jul 2017 17:11:59
  +0200

  [Test case]
  We don't really have any yet, they require DNS servers and http servers, so it's not really easy to test.

  [Regression potential]
  We basically changed just the code used in the http method, and the changes are both very obvious and very small. I reproduced the http change with the tls support from 1.5, because launchpad was causing issues with that.

  With the failure reason reset, some errors might not be wrongly
  considered as transient connection errors and now cause scripts to
  fail. But that's how it should be, really.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1702326/+subscriptions