New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial

Bug #1702326 reported by Julian Andres Klode on 2017-07-04
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt (Debian)
Fix Released
Unknown
apt (Ubuntu)
Medium
Unassigned
Xenial
Medium
Unassigned
Zesty
Medium
Unassigned

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 <email address hidden> 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.

Julian Andres Klode (juliank) wrote :

I might be re-using this bug for the matching changes in xenial and yakkety, unless these are subsets.

Changed in apt (Ubuntu):
status: New → Invalid
Changed in apt (Ubuntu Zesty):
status: New → Triaged
importance: Undecided → Medium
Julian Andres Klode (juliank) wrote :

Added link to the Debian stretch-pu bug.

Changed in apt (Debian):
status: Unknown → New
Changed in apt (Debian):
status: New → Incomplete
Changed in apt (Debian):
status: Incomplete → New
Changed in apt (Debian):
status: New → Confirmed
Changed in apt (Debian):
status: Confirmed → Fix Committed
Changed in apt (Debian):
status: Fix Committed → Fix Released
Changed in apt (Ubuntu Xenial):
status: New → Triaged
summary: - New microrelease 1.4.7 for zesty
+ New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial
Changed in apt (Ubuntu Zesty):
status: Triaged → In Progress
status: In Progress → Fix Committed
Changed in apt (Ubuntu Xenial):
status: Triaged → In Progress
Julian Andres Klode (juliank) wrote :

Sorry for the status noise, I sometimes keep forgetting that statuses have a very different meaning for SRUs than for normal uploads.

Changed in apt (Ubuntu Zesty):
status: Fix Committed → In Progress
status: In Progress → Triaged
Changed in apt (Ubuntu Xenial):
status: In Progress → Triaged
Changed in apt (Ubuntu):
importance: Undecided → Medium
Changed in apt (Ubuntu Xenial):
importance: Undecided → Medium
Changed in apt (Ubuntu Zesty):
status: Triaged → In Progress
description: updated

Hello Julian, or anyone else affected,

Accepted apt into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.4.8 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-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. 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!

Changed in apt (Ubuntu Zesty):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-zesty
Changed in apt (Ubuntu Xenial):
status: Triaged → Fix Committed
tags: added: verification-needed-xenial
Timo Aaltonen (tjaalton) wrote :

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!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.