On 06/09/2017 10:34 PM, Peter Kjellerstedt wrote:
During the transition to rpm4, rpmdeps-oecore was replaced with the standard rpmdeps. However, what no one noticed was that unless rpmdeps is given options, e.g., -P or -R, to tell it what it should output, it will not output anything. Thus, it would do all the work to determine the requirements, but would keep silent about it. And since no output from rpmdeps is expected unless there are requirements, there were no warnings indicating that everything was not working as expected.
Apologies for that, however, this is not tested in any of our autobuilder scenarios or otherwise, and if it's not tested, then it's not broken. :-)
I would recommend you add some kind of test to this patchset to make sure it doesn't happen again (for example, when I would update rpm to a new upstream release).
Alex -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
