This repository has been archived by the owner on Dec 5, 2022. It is now read-only.
apt_lists have wrong dates on Windows Hosts #106
Labels
Milestone
Comments
chrisvire
added a commit
to sillsdev/wesay
that referenced
this issue
May 21, 2014
There is a bug in the Windows version so that the apt_lists are saved with the date of the cache file creation instead of the date they were fetched from the repo. So you can't update packages. I have submitted an issue to the vagrant-cachier repo. fgrehm/vagrant-cachier#106 Make the use of vagrant-cachier optional so that that vagrant creation of VMs on Windows can get updates from the APT repos. Change-Id: I14f05527852ba60c54df4e8caebd6a4b396ccba6
|
I don't have a windows machine to try things out and I have no idea how VBox shared folders behaves over there :-( We might be able to force that bucket to be "force-disabled" on windows hosts, but before going that direction, would you be able to give a shot at turning off automatic cache bucket detection and enabling buckets one by one so that we can figure out which ones are broken? Thanks in advance. |
This was referenced Jul 17, 2014
|
Ok, let's make that bucket disabled by default on windows hosts. Tagged as an enhancement |
|
Is there an open enhancement to correctly share the apt_lists on Windows hosts? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a Ubuntu VM that I am using with Vagrant. If I use it with a Ubuntu host, then the dates on the /tmp/vagrant-cache/apt_lists files older file dates (where do these files come from?). If use it with a Windows host, then the dates on the files are basically the current date. So when I do "sudo apt-get update" in the guest when used on a Windows host, then there are no updates to be found.
The Vagrant file is at: http://github.com/sillsdev/wesay/vagrant/Vagrantfile (which include the urls to the box files stored on google drive).
The text was updated successfully, but these errors were encountered: