The verification of the Stable Release Update for apt has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial
Status in apt package in Ubuntu:
Status in apt source package in Xenial:
Status in apt source package in Zesty:
Status in apt package in Debian:
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 <j...@debian.org> Tue, 04 Jul 2017 17:11:59
We don't really have any yet, they require DNS servers and http servers, so
it's not really easy to test.
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:
Mailing list: https://launchpad.net/~touch-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp