Open penguinpee opened 2 months ago
Thank you for the report.
So, --scrub-all-chroots would need to look at the config_opts['root'] parameter for configs not managed by mock-core-configs.
Indeed, but this makes the process a bit more complicated. Help with this is welcome!
Short description of the problem
The new
--scrub-all-chroots
needs to be smarter with regards to user configs.Output of
rpm -q mock
mock-5.7-1.fc39.noarch
Steps to reproduce issue
mock --scrub-all-chroots
:All of the above are chroots created with output of
copr mock-config project chroot
redirected into~/.config/mock/${short_name}.cfg
and accessible by${short_name}
usingmock -r ${short_name}
orfedpkg mockbuild --root ${short_name}
.The issue is the chroot on disk does not correspond to the name of the config file. The first Unknown directory (which is misleading, since the directory does exist) corresponds to a configuration file called
dill.cfg
with the following content:So,
--scrub-all-chroots
would need to look at theconfig_opts['root']
parameter for configs not managed bymock-core-configs
.