I’m in the process of building the latest release candidate for BackupPC-4.4.1 on a RL10 VM. I had just done this for the current BackupPC-4.4.0 release a month ago on this same VM w/o issue. The process requires BackupPC-XS to be built and then installed in the mock environment first. Then you run mock --noclean BackupPC-4.4.1rc1<blah>src.rpm . This now fails with the statement that you have to define a new “Results” path. This won’t work because the new Results folder is where the chroot environment is built and it will not contain the dependency it needs.
Any thoughts?
I can, as root, delete the buildlock file, I haven’t tried it yet but this isn’t how it should work.
This issue is due to user typo “–noclean” should be “–no-clean”.