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

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

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

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

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

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.

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

** 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:

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

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

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

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: */"

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

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

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

** 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

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

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

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

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

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

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

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

** 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

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

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:

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

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

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

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

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

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

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

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

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

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

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

** 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