https://bugzilla.suse.com/show_bug.cgi?id=1183711
https://bugzilla.suse.com/show_bug.cgi?id=1183711#c20
Michael Andres
I'm not sure which solution to pick, which one is OK for libzypp. If we do not know than the safe option is to revert the cache patches completely.
Don't touch the cache of loaded repos. Unload all repos from the pool, close the target - then moving the repo cache data should be possible. Regarding the symlinks: zypp cache is directory based. If caches are updated we exchange directories. Symlinking individual files may not have the effect you want. BTW - did you consider to unload all repos/target, move the cache to /mnt/..., call ZConfig::setRepoCachePath("/mnt/...") and load the stuff again? And keep in mind that we build and re-build our caches as we need it. The fact that your workflow today does not experience a cache action does not mean it will nnever happen. Load a new libzypp via a DUD and all your symlinking may be obsolete. You can not control when and why a cache rebuild will be necessary. -- You are receiving this mail because: You are on the CC list for the bug.