> I've attached an example log, where the error pops up for multiple packages, and they all appear to be compared to one size (86464 bytes).
just for the record: This is a misunderstanding. If apt does pipelining it searches in the requests it made for the file this response is for. If no request matches the size the error shows the last tried size (aka of the last file in the queue). I wonder a bit why Filesize isn't included in the message as internally it is implemented as a (very weak) hash, but that might be due to the apt version… I am not remembering ATM how it worked back then. I am also a bit worried about the screenshot in the referred bugreport as that shows two different servers replying (Apache vs some python via a proxy). And last not least: The sizes given in the HTTP request logs for python3-zmq (which failed in that example) shown in /var/log/httpd/foreman_access.log and /var/log/messages do not match (254232 vs 254454). -- 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/1921626 Title: apt install - File has unexpected size - http pipeline Status in apt package in Ubuntu: Incomplete Bug description: 1) Ubuntu 18.04.5 LTS 2) apt 1.6.12ubuntu0.2 3) What you expected to happen I set a custom set of repositories in /etc/apt/sources.list and then I run "apt install <list of packages>". I expect the command to download and install the packages. 4) What happened instead "apt install ..." fails during the download phase with "File has unexpected size ...." 5) What I've established trying to debug the issue: - Disabling http pipelining resolves the issue: "apt -oAcquire::http::Pipeline-Depth=0 install ..." - All the packages, and repo metadata in the referenced repositories is correct - The issue is easily reproducible in my setup with different repositories - tcpdump shows that requests and responses are in the correct order, and contain the correct data More details about the issue: https://projects.theforeman.org/issues/32178 With all the above in mind, it appears that this must be a bug in apt's http pipeline handling. It seem that apt is trying to match a request to do wrong response, and size doesn't match. I've attached an example log, where the error pops up for multiple packages, and they all appear to be compared to one size (86464 bytes). That size is correct for one of the package being downloaded, but somehow apt is trying to match to multiple other packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1921626/+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