Log Detective

Trying to improve RPM packaging experience by analyzing build logs and explaining the failure in simple words.

About the project

Debugging failed builds is hard
Each build produces thousands of lines of output split among multiple log files. And the relevant error message can be anywhere. It's just like a needle in a haystack.
Does it matter?
Veteran packagers have an intuition where the error message will most likely be, but the process is tedious regardless. Newbies are often overwhelmed by the complexity and miss the error message completely.
What is our goal?
Training an AI model to understand RPM build logs and explain the failure in simple words, with recommendations how to fix it. You won't need to open the logs at all.