I've talked about this with Robie Basak before.
For cloud-images building, it seems like it makes sense to clear out apt cache
for updates and security. In the best case scenario, those files are up to
date and apt wont re-download. That lasts only until the next SRU or security
update, so it is not a long term win.
So it seems to make good sense to just clean those out, leaving only release
files.
That will fix this problem for all stable releases where the release pocket is
frozen. The problem will still exist during the development cycle of a
release, but that seems much less impact.
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
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/1685399
Title:
[2.2] MAAS should delete cached apt lists before running apt update
Status in APT:
New
Status in cloud-images:
New
Status in MAAS:
Won't Fix
Status in apt package in Ubuntu:
New
Bug description:
I have a local Ubuntu mirror that sometimes lags slightly behind the
official mirror.
Thus, if I commission a MAAS node while the local mirror is lagging
behind the images synced to MAAS (which are expecting the current
packages), "apt-get update" does not overwrite the local apt lists,
prints errors about hash mismatches, and later may fail to download
packages which are more up to date in the main archive than the local
mirror.
There is a way to prevent this issue: the first thing we should always
do, before performing any actions with 'apt', is:
rm -rf /var/cache/apt/lists/*
apt-get update
To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1685399/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
