New/strange (mis)hehaviour in 6.5?

[lejeczek]

Hi guys.
This works with 6.4:

-> $ mock -r centos-stream+epel-9-x86_64 --rootdir=/devs/var/mock --resultdir=/00-REPOs/dnf.repo/repo/"{{dist}}"/"{{target_arch}}" --spec ~/rpmbuild/SPECS/python3.9.spec --sources=~/rpmbuild/SOURCES/ | tee ~/rpmbuild/_logs/last_mock_build.log

but with 6.5:

ERROR: Cannot find/open srpm: /00-REPOs/dnf.repo/repo/el9/x86_64/python3.9-3.9.23-2.el9.src.rpm. Error: [Errno 2] No such file or directory: '/00-REPOs/dnf.repo/repo/el9/x86_64/python3.9-3.9.23-2.el9.src.rpm'

Seems that --resultdir fails this, add some suffix to the path, eg.: ...."{{target_arch}}"/package and mock is happy to go.

Am I missing something with this 6.5 version?
thanks, L.

[lejeczek]

Nothing to do with mock - I'll leave it here as a note for potential users of fs watchers & what those you want to do with --resultdir
To devel here - it would be great if perhaps future mocks enhance to add options like, eg. --result-logs --result-srmp or however devel would name it - I'd hope naming explains meant functions in this example.
thanks, L.