Comment 36 for bug 932088

On Tue, 24 Apr 2012, Deepti B. Kalakeri wrote:

> According to the comments in the bug above we have been able to resolve the 404 Not Found error and HashSum issue by using the following 2 things.
> 1) sudo sed -i.dist 's,archive.ubuntu.com,archive.ubuntu.com.s3.amazonaws.com,g' /etc/apt/sources.list
> 2) echo "Acquire::http::Pipeline-Depth 0;" | sudo tee /etc/apt/apt.conf.d/99no-pipelining
>
> I see on ci.linaro.org init for precise instance ami-b5ea34dc has been updated to use all the above.
> But, even after applying those changes I still I got the 404 file not found, though not the HashSum mismatch errors this morning continuously.
> With this the builds started to be queue in for longer time.
> Finally I had to change the ami instance used from beta2 ami-b5ea34dc instance to beta1 ami-2061b349 instance and was able to proceed with the builds.

I can't come up with an explanation for this.
This doesn't really make any sense to me.

I just launched an instance of ami-b5ea34dc, and ran the same 2 commands
above and cannot replicate the issues. After doing so, I also did:
  apt-get dist-upgrade
which downloaded 86M in 142 packages, and then
  apt-get --download-only --assume-yes install ubuntu-desktop^
which downloaded 454M in 1009 packages

> Also, I see the following http URL in the error slave logs:
> W: Failed to fetch http://us-east-1.ec2.us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise-updates/universe/binary-i386/Packages 404 Not Found

This is a very confusing error indeed. The fact is that 'Packages', as
opposed to Packages.gz or Packages.bz2 does not really exist anywhere.
The error you're seeing is because the apt did not like the content it
got for Packages.gz or Packages.bz2 (likely both of them) , and fell back
to trying Packages, which resulted in a 404.

Its annoying that apt basically hides the original error.