I've noticed the same problem but I'm not sure it's about
the packages. It may be something to do with mock or the
kernel, possibly. Are you running Rawhide on the machine
where you're doing the mock builds?
I'm building for rawhide, but on my F32 desktop...
I most recently noticed
it when building lives with Python 3.9 for testing - that
should take less than an hour per image, it actually took
12+ hours per image. When I attach an strace to the dnf
process it seems like it doesn't really stick on any one
call for a *long* time, but it seems to do a lot of fsyncs,
and each one takes, like, a half second or so. I *think* the
slowness is the result of all those fsyncs piling up.
The actual package build time doesn't "feel" any
difference, but installing the dependencies definitely takes
much longer.
I've tried installing
nosync (both i686 and x86-64) on the host but it didn't seem
to make a difference, I didn't check for sure that it
actually kicked in. I'll try and do a bit more of a
systematic look at it tomorrow, since at least now I know
I'm not the only one...
I have nosync (both arches) installed as well...
Thanks,
Richard