[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.2.20

---
apt (1.2.20) xenial; urgency=medium

  * Microrelease covering fixes of 1.4~rc2 (LP: #1668285)

  [ David Kalnischkies ]
  * don't install new deps of candidates for kept back pkgs
  * keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
  * reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
  * add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
  * let {dsc,tar,diff}-only implicitly enable download-only
  * don't show update stats if cache generation is disabled
  * don't lock dpkg in 'apt-get clean'
  * don't lock dpkg in update commands
  * avoid validate/delete/load race in cache generation
  * remove 'old' FAILED files in the next acquire call (Closes: 846476)
  * stop rred from leaking debug messages on recovered errors (Closes: #850759)

  [ Paul Wise ]
  * show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

  [ John R. Lenton ]
  * bash-completion: Only complete understood file paths for install
(LP: #1645815)

  [ Lukasz Kawczynski ]
  * Honour Acquire::ForceIPv4/6 in the https transport

  [ Julian Andres Klode ]
  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Do not package names representing .dsc/.deb/... files (Closes: #854794)
  * Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues

 -- Julian Andres Klode   Mon, 27 Feb 2017 15:29:18
+0100

** Changed in: apt (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Yakkety:
  Fix Released

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

  [Impact]
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.

  [Test Case]
  Run

  /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
  http://www.jak-software.de/lp1657567 ubuntu.iso

  Before:

  E: Failed to fetch http://www.jak-software.de/lp1657567  The HTTP
  server sent an invalid Content-Range header Bad header data

  After:

  Redirect is followed successfully and a zesty live image is being
  downloaded.

  [Regression Potential]
  None

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.3.5

---
apt (1.3.5) yakkety; urgency=medium

  * Microrelease covering important fixes of 1.4~rc2 (LP: #1668280)

  [ David Kalnischkies ]
  * don't install new deps of candidates for kept back pkgs
  * keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
  * reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
  * add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
  * react to trig-pend only if we have nothing else to do
  * correct cross & disappear progress detection
  * improve arch-unqualified dpkg-progress parsing
  * don't perform implicit crossgrades involving M-A:same
  * do not configure unconfigured to be removed packages
  * skip unconfigure for unconfigured to-be removed pkgs
  * get pdiff files from the same mirror as the index
  * let {dsc,tar,diff}-only implicitly enable download-only
  * ensure generation of valid EDSP error stanzas
  * fix minimum pkgs option for dpkg --recursive usage
  * don't show update stats if cache generation is disabled
  * don't lock dpkg in 'apt-get clean'
  * don't lock dpkg in update commands
  * avoid validate/delete/load race in cache generation
  * fix 'install --no-download' mode
  * remove 'old' FAILED files in the next acquire call (Closes: 846476)
  * stop rred from leaking debug messages on recovered errors (Closes: #850759)

  [ Edgar Fuß ]
  * http: clear content before reporting the failure (Closes: #465572)

  [ Paul Wise ]
  * show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

  [ John R. Lenton ]
  * bash-completion: Only complete understood file paths for install
(LP: #1645815)

  [ Lukasz Kawczynski ]
  * Honour Acquire::ForceIPv4/6 in the https transport

  [ Julian Andres Klode ]
  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Do not package names representing .dsc/.deb/... files (Closes: #854794)
  * Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
  * CMake: Install statvfs.h to include/sys, not just include/

 -- Julian Andres Klode   Mon, 27 Feb 2017 15:02:40
+0100

** Changed in: apt (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Released

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

  [Impact]
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.

  [Test Case]
  Run

  /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
  http://www.jak-software.de/lp1657567 ubuntu.iso

  Before:

  E: Failed to fetch http://www.jak-software.de/lp1657567  The HTTP
  server sent an invalid Content-Range header Bad header data

  After:

  Redirect is followed successfully and a zesty live image is being
  downloaded.

  [Regression Potential]
  None

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Julian Andres Klode]

Verified broken in 1.3.4, and fixed in 1.3.5.

** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

  [Impact]
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.

  [Test Case]
  Run

  /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
  http://www.jak-software.de/lp1657567 ubuntu.iso

  Before:

  E: Failed to fetch http://www.jak-software.de/lp1657567  The HTTP
  server sent an invalid Content-Range header Bad header data

  After:

  Redirect is followed successfully and a zesty live image is being
  downloaded.

  [Regression Potential]
  None

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Jon Grimm]

** Tags removed: verification-needed
** Tags added: verification-done-xenial verification-needed-yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

  [Impact]
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.

  [Test Case]
  Run

  /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
  http://www.jak-software.de/lp1657567 ubuntu.iso

  Before:

  E: Failed to fetch http://www.jak-software.de/lp1657567  The HTTP
  server sent an invalid Content-Range header Bad header data

  After:

  Redirect is followed successfully and a zesty live image is being
  downloaded.

  [Regression Potential]
  None

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Chris J Arges]

Hello Julian, or anyone else affected,

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

** Tags removed: verification-done

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

  [Impact]
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.

  [Test Case]
  Run

  /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
  http://www.jak-software.de/lp1657567 ubuntu.iso

  Before:

  E: Failed to fetch http://www.jak-software.de/lp1657567  The HTTP
  server sent an invalid Content-Range header Bad header data

  After:

  Redirect is followed successfully and a zesty live image is being
  downloaded.

  [Regression Potential]
  None

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Julian Andres Klode]

Verified in 1.2.20.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  In Progress

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

  [Impact]
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.

  [Test Case]
  Run

  /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
  http://www.jak-software.de/lp1657567 ubuntu.iso

  Before:

  E: Failed to fetch http://www.jak-software.de/lp1657567  The HTTP
  server sent an invalid Content-Range header Bad header data

  After:

  Redirect is followed successfully and a zesty live image is being
  downloaded.

  [Regression Potential]
  None

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Chris J Arges]

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.20 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  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 Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  In Progress

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

  [Impact]
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.

  [Test Case]
  Run

  /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
  http://www.jak-software.de/lp1657567 ubuntu.iso

  Before:

  E: Failed to fetch http://www.jak-software.de/lp1657567  The HTTP
  server sent an invalid Content-Range header Bad header data

  After:

  Redirect is followed successfully and a zesty live image is being
  downloaded.

  [Regression Potential]
  None

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Julian Andres Klode]

** Description changed:

  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.
  
  We should probably just accept and silently ignore that content-range
  field for other values.
  
- 
- [Impact] 
+ [Impact]
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.
  
  [Test Case]
- TODO.
+ Run
  
- [Regression Potential] 
+ /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
+ http://www.jak-software.de/lp1657567 ubuntu.iso
+ 
+ Before:
+ 
+ E: Failed to fetch http://www.jak-software.de/lp1657567  The HTTP server
+ sent an invalid Content-Range header Bad header data
+ 
+ After:
+ 
+ Redirect is followed successfully and a zesty live image is being
+ downloaded.
+ 
+ [Regression Potential]
  None

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Yakkety:
  In Progress

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

  [Impact]
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.

  [Test Case]
  Run

  /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
  http://www.jak-software.de/lp1657567 ubuntu.iso

  Before:

  E: Failed to fetch http://www.jak-software.de/lp1657567  The HTTP
  server sent an invalid Content-Range header Bad header data

  After:

  Redirect is followed successfully and a zesty live image is being
  downloaded.

  [Regression Potential]
  None

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Julian Andres Klode]

Seems like sourceforge is fixed now, so we need to come up with a new
test.

** Description changed:

  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.
  
  We should probably just accept and silently ignore that content-range
  field for other values.
+ 
+ 
+ [Impact] 
+ Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.
+ 
+ [Test Case]
+ TODO.
+ 
+ [Regression Potential] 
+ None

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Yakkety:
  In Progress

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

  
  [Impact] 
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.

  [Test Case]
  TODO.

  [Regression Potential] 
  None

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Julian Andres Klode]

Oh, sorry, did not notice that it did not have one.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Yakkety:
  In Progress

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Łukasz Zemczak]

Since this (and a few other) bug is mentioned in the SRU changelog,
please update the description to include the SRU template. There seems
to be a master bug for the SRU, but each bug should *at least* have a
clearly written test-case. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Yakkety:
  In Progress

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Julian Andres Klode]

** Changed in: apt (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: apt (Ubuntu Yakkety)
   Status: Triaged => In Progress

** Changed in: apt (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: apt (Ubuntu Yakkety)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Yakkety:
  In Progress

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Julian Andres Klode]

Queued for 1.2.20:

  https://github.com/Debian/apt/compare/1.2.19...julian-
klode:1.2.y?expand=1

Queued for 1.3.5:

  https://github.com/Debian/apt/compare/1.3.4...julian-
klode:1.3.y?expand=1


** Also affects: apt (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: apt (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: apt (Ubuntu Yakkety)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in apt source package in Yakkety:
  Triaged

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Travisgevans]

I thought it might be helpful to anyone still having this problem (where
the fix hasn't been backported yet) to mention that the workaround is
described in Bug #1607535 (essentially, delete the affected partial
download files in /var/lib/update-notifier/package-data-
downloads/partial/ and then try reinstalling again).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Julian Andres Klode]

It will come to (yakkety and) xenial eventually. But it's not urgent
enough to warrant a prioritised upload on its own IMO. There's some
other stuff I want to figure out first - like merging new translations,
and some other bug fixes from the 1.4 series.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[rpr nospam]

Please, backport this to xenial.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.4~beta4ubuntu1

---
apt (1.4~beta4ubuntu1) zesty; urgency=medium

  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Workaround debian/copyright symlink

 -- Julian Andres Klode   Wed, 25 Jan 2017 12:07:50
+0100

** Changed in: apt (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Julian Andres Klode]

Fix committed:

https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=4759a70

commit 4759a702081297bde66982efed8b2b7fd39ca27c
Author: Julian Andres Klode 
Date:   Wed Jan 18 20:39:27 2017 +0100

basehttp: Only read Content-Range on 416 and 206 responses

This fixes issues with sourceforge where the redirector includes
such a Content-Range in a 302 redirect. Since we do not really know
what file is meant in a redirect, let's just ignore it for all
responses other than 416 and 206.

Maybe we should also get rid of the other errors, and just ignore
the field in those cases as well?

LP: #1657567


** Changed in: apt (Ubuntu)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Triaged

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp