For this purpose, a repo is considered clean when its disk usage doesn't exceed 64KB (that is to account for directory entries and tiny metadata files such as "productid" that are never cleaned). As a convenience, if this command does not result in a completely empty cache due to the restrictions outlined at the beginning of this section, a message will be printed, saying how much disk space can be reclaimed by cleaning the remaining repos manually. This is most often useful if you are using a newer distribution release than is supported.
for the repository, to point to a working upstream. Contact the upstream for the repository and get them to fix the problem. There are a few ways to work 'fix' this: 1. Tell any enabled plugins to eliminate their cached data.ĭoes all of the above. At this point the only safe thing yum can do is fail. Using this option will force yum to download the sqlite metadata the next time it is run, or recreate the sqlite metadata if using an older repo.Įliminate any cached data from the local rpmdb. Using this option will force yum to download all the metadata the next time it is run.Įliminate the sqlite cache used for faster access to metadata. Note that packages are not automatically deleted after they are downloaded.Įliminate all of the header files, which old versions of yum used for dependency resolution.Įliminate all of the files which yum uses to determine the remote availability of packages. However if the cache is still valid, nothing significant was deleted.Įliminate any cached packages from the system. This means yum will revalidate the cache for each repo. Taken from "man yum" ?clean CLEAN OPTIONSĮliminate the local data saying when the metadata and mirrorlists were downloaded for each repo.
0 kommentar(er)
