Description of problem:
rpm -qpi should ignore specspo
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum install specspo
1. get (for example pm-utils) SRPM, change description, build
2. rpm -qpi RPM
IMHO if used on locally stored RPMs with the -p switch it should show what is exactly in the RPM.
NAK. One of the important uses of specspo is to allow non-English speakers to get a clue about the packages they're about to install, and this would make specspo even more useless than it is now. Also this behavior is actually intentional part of specspo "design": it avoids breaking all translations when somebody fixes a typo or such in the actual package description.
The flip-side of course is the confusing behavior you're seeing (you're certainly not the first one to complain about this). In RHEL-6 specspo lookups are done directly on the actual string from the package (instead of going through name(tag) C-locale lookup first) so when the strings in package change, that's what you get... at the cost of breaking all translations.
It would be possible to change RHEL-5 to use direct lookups too, which would fix this issue but OTOH cause unknown amount of translation regressions unless specspo gets a major update too. I dont think its worth the trouble messing with it for RHEL-5, packagers are best off just doing 'rpm -e specspo' to get it out of the way.