[Rpm-maint] [rpm-software-management/rpm] Moving unnecessary notice about empty rpm packages to debug message. (#615)

[Panu Matilainen]

Like said, this is a generic problem in rpm where diagnostic messages are dumped on stdout. Other similar examples include (but not limited to):
```
[pmatilai at sopuli ~]$ rpm -q --whatprovides bar
no package provides bar
[pmatilai at sopuli ~]$ touch foo
[pmatilai at sopuli ~]$ rpm -qf foo
file /home/pmatilai/foo is not owned by any package
```
All spewed into stdout against core unix principles. But the world is full of scripts that grep specifically for these messages because they've always been there. And so there are scripts that test for empty packages by grepping specifically for that "(contains no files)" message, and changing it would break those scripts. Ditto for all the other similar cases. And that's exactly why we need to address the generic problem rather than individual messages so we can do a clean break that people can also then adjust to, once.

I fully agree the rpm behavior is in error, but this is not the right fix to the overall problem. NAK.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/615#issuecomment-450869382
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20190102/808b7b79/attachment.html>