1:0.55ubuntu4.1 timestamps are ahead of the repository
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt-setup (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
On 12.04.5 64 bit Server, install apt-get is having issues. A search for "ubuntu 12.04.5 hash sum mismatch" will show that I'm not alone with this.
Issue: If you do an apt-get update after a fresh install you'll get
W: Failed to fetch bzip2:/
W: Failed to fetch bzip2:/
<sniped 11 more>
This problem is caused by the time stamps in the apt-setup_
ls -al apt-setup/
-rw-r--r-- 1 root root 5922 Jun 23 2014 Release
-rw-r--r-- 1 root root 198 Jun 23 2014 Release.gpg
But the contents of the Release file shows a date of Thu, 13 Oct 2011 16:32:27 UTC
But on http://
Release 25-Apr-2012 22:49 48K
Release.gpg 25-Apr-2012 22:49 198
When the ubuntu installer does an apt-get update, it does not use the one on the Ubuntu Repo (Apr-2012) because it thinks the one supplied by apt-setup(Jun 2014) is more upto date. Release and Release.gpg are shown as "hit" rather than "get". So apt uses the outdated ones from Apr 2012.
From /var/log/
Mar 20 19:54:14 in-target: Hit http://
Mar 20 19:54:14 in-target: Get:1 http://
Mar 20 19:54:14 in-target: Get:2 http://
Mar 20 19:54:14 in-target: Hit http://
Mar 20 19:54:14 in-target: Get:3 http://
Mar 20 19:54:15 in-target: Get:4 http://
Because Release is out of date, it break apt-gets update on the 12.04.5 Server and Alternate installs.
Someone just needs to update the dates for Release and Release.gpg in dists/precise.
The dates for Release and Release gpg for precise-backports, precise-proposed, precise-security and,precise-updates are all in 2015.