Activity log for bug #1087543

Date Who What changed Old value New value Message
2012-12-07 03:17:39 Thomas Bushnell, BSG bug added bug
2012-12-07 03:17:39 Thomas Bushnell, BSG attachment added enable apt to keep https connections alive for reuse https://bugs.launchpad.net/bugs/1087543/+attachment/3453573/+files/apt-fix-keep-alive.txt
2012-12-07 03:18:02 Thomas Bushnell, BSG bug added subscriber Goobuntu Team
2012-12-07 04:18:27 Ubuntu Foundations Team Bug Bot tags patch
2012-12-07 04:18:34 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Review Team
2013-01-09 09:56:36 Michael Vogt apt (Ubuntu): status New In Progress
2013-01-09 09:56:38 Michael Vogt apt (Ubuntu): importance Undecided Medium
2013-01-31 05:53:52 Launchpad Janitor branch linked lp:~mvo/apt/source-hashes
2013-04-26 00:05:26 Brian Murray apt (Ubuntu): assignee Michael Vogt (mvo)
2013-07-08 21:24:34 Chris J Arges bug added subscriber Sustaining Engineering
2013-07-10 20:07:55 Launchpad Janitor apt (Ubuntu): status In Progress Fix Released
2013-07-10 20:07:55 Launchpad Janitor bug watch added http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666772
2013-07-10 20:07:55 Launchpad Janitor cve linked 2013-1051
2013-07-12 18:00:23 Dave Chiluk attachment added Debdiff of tbushnell's patch https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1087543/+attachment/3734702/+files/apt-fix-keep-alive.debdiff
2013-07-12 18:06:22 Dave Chiluk branch linked lp:~chiluk/ubuntu/precise/apt/reuse_https
2013-07-12 18:17:16 Dave Chiluk description When using an https: connection, apt-get does not properly reuse connections. Because https setup costs can be quite high, this can cause much slowdown when, for example, many different distributions on the same server need to be checked. I believe the attached patch addresses the difficulty. [Impact] * Apt does not re-use https connections. This results in a significant performance hit. * Additionally the hosts of mirrors are experiencing unnecessarily high load due to this [Test Case] * Run apt-get -update using https connections. It will be noticably slower in comparison to after this change [Regression Potential] * This fixes apt, by changing the way it uses curl, such that only problematic error codes cause failure. * Might result in zero length files, or updates not being downloaded. * https connections hanging in the event that the above logic does not correctly handle error cases. [Other Info] * This is already in Saucy. * This is not imperative to be pulled into precise, but it would be nice. * This is really more of an enhancement than a bug fix. * I have been using this patch for over 5 months now with no negative side affects. * I have been told that this patch has been deployed in a large (multi-thousand install base) organization with no negative side affects as well. When using an https: connection, apt-get does not properly reuse connections. Because https setup costs can be quite high, this can cause much slowdown when, for example, many different distributions on the same server need to be checked. I believe the attached patch addresses the difficulty.
2013-07-12 18:17:41 Dave Chiluk bug added subscriber Ubuntu Stable Release Updates Team
2013-07-12 20:16:48 Dave Chiluk tags patch patch precise
2013-07-12 22:14:49 Dave Chiluk description [Impact] * Apt does not re-use https connections. This results in a significant performance hit. * Additionally the hosts of mirrors are experiencing unnecessarily high load due to this [Test Case] * Run apt-get -update using https connections. It will be noticably slower in comparison to after this change [Regression Potential] * This fixes apt, by changing the way it uses curl, such that only problematic error codes cause failure. * Might result in zero length files, or updates not being downloaded. * https connections hanging in the event that the above logic does not correctly handle error cases. [Other Info] * This is already in Saucy. * This is not imperative to be pulled into precise, but it would be nice. * This is really more of an enhancement than a bug fix. * I have been using this patch for over 5 months now with no negative side affects. * I have been told that this patch has been deployed in a large (multi-thousand install base) organization with no negative side affects as well. When using an https: connection, apt-get does not properly reuse connections. Because https setup costs can be quite high, this can cause much slowdown when, for example, many different distributions on the same server need to be checked. I believe the attached patch addresses the difficulty. [Impact]  * Apt does not re-use https connections. This results in a significant performance hit.  * Additionally the hosts of mirrors are experiencing unnecessarily high load due to this [Test Case]  * Run apt-get -update using https connections. It will be noticably slower in comparison to after this change [Regression Potential]  * This fixes apt, by changing the way it uses curl, such that only problematic error codes cause failure. But this may only happen if the user is using https, http is not affected by this patch.  * Might result in zero length files, or updates not being downloaded over https connectiosn.  * https connections hanging in the event that the above logic does not correctly handle error cases. [Other Info] * There's only a slight chance to hit any regressions, as the above is mostly just thinking well outside of the box.  * This is already in Saucy.  * This is not imperative to be pulled into precise, but it would be nice.  * This is really more of an enhancement than a bug fix.  * I have been using this patch for over 5 months now with no negative side affects.  * I have been told that this patch has been deployed in a large (multi-thousand install base) organization with no negative side affects as well. -------------------------------------------------------------------------------- When using an https: connection, apt-get does not properly reuse connections. Because https setup costs can be quite high, this can cause much slowdown when, for example, many different distributions on the same server need to be checked. I believe the attached patch addresses the difficulty.
2013-07-15 16:42:49 Brian Murray nominated for series Ubuntu Precise
2013-07-15 16:42:49 Brian Murray bug task added apt (Ubuntu Precise)
2013-07-15 16:44:09 Brian Murray apt (Ubuntu Precise): status New Triaged
2013-07-15 16:44:11 Brian Murray apt (Ubuntu Precise): importance Undecided Low
2013-07-15 21:30:41 Launchpad Janitor branch linked lp:~ubuntu-core-dev/apt/precise
2013-07-16 12:34:25 Nobuto Murata bug added subscriber Nobuto MURATA
2013-07-16 17:56:09 Adam Conrad apt (Ubuntu Precise): status Triaged Fix Committed
2013-07-16 17:56:13 Adam Conrad bug added subscriber SRU Verification
2013-07-16 17:56:15 Adam Conrad tags patch precise patch precise verification-needed
2013-07-16 18:13:29 Launchpad Janitor branch linked lp:ubuntu/precise-proposed/apt
2013-07-29 18:28:20 Dave Chiluk tags patch precise verification-needed patch precise verification-done
2013-07-29 20:29:36 Mark Russell bug added subscriber Mark Russell
2013-08-01 16:56:31 Launchpad Janitor apt (Ubuntu Precise): status Fix Committed Fix Released
2013-08-01 16:56:36 Colin Watson removed subscriber Ubuntu Stable Release Updates Team
2014-02-07 17:14:17 Curtis Hovey removed subscriber Registry Administrators