[Bug 1001780] Re: apt-get update size is too big

[John S. Gruber]

@zpletan, touching them stops them from being downloaded. You should
only touch the files that haven't changed since you downloaded them. By
appropriate files I'm speaking of the files that were frozen at the
release of the release you are running (those are the ones giving people
trouble until the bug is fixed). You shouldn't use the touch command on
any others, or against Quantal--its main and universe repos are active.

In this case touching a file just says it was current at the time you
run the touch command (it makes the last modification time the current
time).

There's detail in: http://askubuntu.com/questions/135818/the-apt-get-
update-cache-size-is-too-big

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1001780

Title:
  apt-get update size is too big

Status in Launchpad itself:
  Invalid
Status in “apt” package in Ubuntu:
  Confirmed

Bug description:
  I ran a clean install to Ubuntu 12.04 and so far everything has been
  working well. I especially commend the Ubuntu team for this release.

  I only noticed that the size of repository update is now about ~13MB.
  Normally, it is about this size for the first time you run apt-get
  update after a clean install and then ~ 23kb - 1300kb for subsequent
  updates.  However now it looks like it gets 13MB and bigger every now
  and then.

  Using us.archive.ubuntu.com archive, I see that the Universe Package
  files are being recreated a couple of times an hour, but contain the
  same content. The file modification date and expiration date, and in
  particular, the etag, are changing each time causing apt-get update to
  reload the Package file again even though it hasn't changed.

  Launchpad shouldn't recreating the Package files when no changes have
  been made to the contained packages.

  #http://askubuntu.com/questions/135818/the-apt-get-update-cache-size-
  is-too-big

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1001780/+subscriptions