RPM error reporting does not report which exactly token produced problem in case
of processing autogenerated dependencies. In this case RPM already parsed spec
file and thus current line points behind last spec file line which makes
impossible to find out what happens without using RPM_SCRIPTS_DEBUG=1 and
carefully analyzing lots of debug output.
Created attachment 366 [details]
Include dependency token into reported error message
Created attachment 398 [details]
I'm about to apply this patch.
It works for me, please check whether it fits your requirements.
I think it is OK.
Fixed in rpm-4.0.4-alt37