You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I just received a warning that I am apparently running out of disc space on root I checked my disc usage and noticed that over the last couple of years mock had gained some significant weight, because I never cleaned any caches or anything myself.
According to the man page, --scrub can "Completely remove the specified chroot or cache dir or all of the chroot and cache.". Running mock --scrub=all removed some of the files, but a bunch still remain. It appears that mock only touches the files for the current running Fedora version.
The man page doesn't state this from what I can tell (and would also contrast "all of the chroot and cache"). Specifying an -r argument can alleviate this issue, however that is not feasible for files for which a mock-config no longer exists due to EOL removal, and would require passing each offending config manually, which would defeat the purpose of an "all" argument in my eyes.
Output of rpm -q mock
~ rpm -q mock
mock-5.5-1.fc39.noarch
Steps to reproduce issue
build a random assortment of RPMs in different Fedora versions
check /var/cache/mock and/or /var/lib/mock for content and/or size
run mock --scrub=all (also tested mock --scrub=cache)
Short description of the problem
When I just received a warning that I am apparently running out of disc space on root I checked my disc usage and noticed that over the last couple of years mock had gained some significant weight, because I never cleaned any caches or anything myself.
According to the man page,
--scrub
can "Completely remove the specified chroot or cache dir or all of the chroot and cache.". Runningmock --scrub=all
removed some of the files, but a bunch still remain. It appears that mock only touches the files for the current running Fedora version.The man page doesn't state this from what I can tell (and would also contrast "all of the chroot and cache"). Specifying an
-r
argument can alleviate this issue, however that is not feasible for files for which amock-config
no longer exists due to EOL removal, and would require passing each offending config manually, which would defeat the purpose of an "all" argument in my eyes.Output of
rpm -q mock
Steps to reproduce issue
/var/cache/mock
and/or/var/lib/mock
for content and/or sizemock --scrub=all
(also testedmock --scrub=cache
)/var/cache/mock
and/or/var/lib/mock
againAny additional notes
Output of `mock --debug-config`
Remaining files in my case:
Specifying
-r
:Possibly related to #521 ?
The text was updated successfully, but these errors were encountered: