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.