Red Hat Bugzilla – Bug 233529
root cache file should be considered stale once .cfg has a newer timestamp
Last modified: 2013-01-09 23:13:40 EST
Description of problem:
If a mock root is cached, any changs to the cfg file that would change the
composition of that root file are ignored. For example, if you change repo
configuration, the next run using autocache will ignore those changes and use
whatever is in the root cache.
Specifically, I tested this by changing:
config_opts['chroot_setup_cmd'] = 'groupinstall build'
config_opts['chroot_setup_cmd'] = 'groupinstall build build-minimal'
New files that should have been in the root next time I ran with --autocache
were not there until I rebuilt the root cache.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run mock with --autocache, cache is created
2. change a cfg file used to build with, change something that would affect root
3. build with new cfg file (and --autocache), changes are not in affect as old
root is cached
automatically rebuild root cache when cfg file is newer than root cache, or at
least maybe an --ignorestale option.
Good point. I'll add some logic to the next release to check the timestamp of
the root cache versus the .cfg that controls it.
Seems like this already happens, not?
Latest version has code to check both the cfg file and the default.cfg file and
will rebuild the cache if either is newer than the cache file.