Hi Kevin, Am 08.03.22 um 01:33 schrieb Kevin Kofler via devel:
There is actually a "mock shell" command that opens a shell inside the mock chroot. You can also run arbitrary shell commands (including scripts that you have previously manually copied in using the "copyin" command) in it.
I knew "mock shell" (via "fedpkg mockbuild --shell") but that only gave me a shell at the very beginning of the build process while (ideally) I wanted to set a kind of "breakpoint"+gdb/pdb at an arbitrary point in the build process. (For example most of the build process works just fine so I want all the %prep/%build steps to run automatically while only fiddling around inside %check.)
After reading your answer + mock manpages I discovered mock's "--no-cleanup-after" which could help inspecting the state after a failed run. That should be pretty helpful, I'll try that next time I need to figure out why some test suite is failing. :-)
Felix _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
