The cache mechanism is not working with apt for more then a week old packages

[mickours]

When I try to run a recipe with the cache enable, the packages are expired for apt:

Step 8 : bootstrap/install_requirements/apt_install
--> Running the step...
Starting process: "ssh -F /debian_home/mercierm/Projects/stimergy/stimergy-recipe/build/prod-admin-server/ssh_config prod-admin-server -t /bin/bash"
[out] The out_context has been initialized
[out] Get:1 http://ftp.debian.org jessie InRelease [191 kB]
[out] E: Release file for http://ftp.debian.org/debian/dists/jessie/InRelease is expired (invalid since 8d 21h 54min 13s). Updates for this repository will not be applied.

The cache mechanism should restore the date of the first build to avoid this kind of error.

As a workaround you can use interactive mode to enter the running context and set a date before the cache has expired like this: date --set 2014/12/10 and run the step again.

[SalemHarrache]

We have already noticed this problem with @camilo1729.

We wanted to save the date of each context with the cache, when creating the cache. Kameleon will only have to change the date when initializing contexts.

I don't know what you've done at this level @camilo1729 ?

[mickours]

This also can be avoided by using this APT option:
apt-get -o Acquire::Check-Valid-Until=false update
Since the problem was found only with APT maybe a good way to fix it is just to add the option for each apt-get update.
What do you think?

[mickours]

In the absence of a reply, I choose to upgrade the kameleon-recipes repository and add the -o Acquire::Check-Valid-Until=false for each apt-get update.

[mickours]

this is still an open question and set the time in context may be a solution.