#108: rpmguard test for unexpanded macros in srpms -------------------------+-------------------------------------------------- Reporter: ajax | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: tests | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- Koji builds the SRPM in a fairly empty environment. Not all rpm macro definitions may be available at that time. The built SRPM should not contain unexpanded macros in any text field like %description.
#108: rpmguard: test for unexpanded macros in srpms --------------------------+------------------------------------------------- Reporter: ajax | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: tests | Version: 1.0 Resolution: | Keywords: rpmguard --------------------------+------------------------------------------------- Changes (by kparal):
* keywords: => rpmguard * summary: rpmguard test for unexpanded macros in srpms => rpmguard: test for unexpanded macros in srpms
Comment:
Thank you for providing an idea. I have only basic knowledge of building RPMs, so my question may be silly, but - is this something appropriate for comparative testing (comparing the old package to the new one, the rpmguard way) or is it rather package sanity testing (we don't need to compare with older packages, so it's more like rpmlint way)?
#108: rpmguard: test for unexpanded macros in srpms --------------------------+------------------------------------------------- Reporter: ajax | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: tests | Version: 1.0 Resolution: | Keywords: rpmguard --------------------------+------------------------------------------------- Comment (by wwoods):
As I understand it, this is more of an rpmlint-style test - no comparison with the previous version is needed.
#108: rpmguard: test for unexpanded macros in srpms --------------------------+------------------------------------------------- Reporter: ajax | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: tests | Version: 1.0 Resolution: | Keywords: rpmguard --------------------------+------------------------------------------------- Comment (by kparal):
So it would make more sense to move this ticket to rpmlint project? Or we can leave it here as a reminder to implement this as an another test for autoqa framework. What do you think, Will?
I would say this directly touches the RPM internals, so we could move this enhancement to rpmlint project.
#108: rpmguard: test for unexpanded macros in srpms --------------------------+------------------------------------------------- Reporter: ajax | Owner: Type: enhancement | Status: closed Priority: major | Milestone: Component: tests | Version: 1.0 Resolution: wontfix | Keywords: rpmguard --------------------------+------------------------------------------------- Changes (by kparal):
* status: new => closed * resolution: => wontfix
Comment:
I have re-reported this request to rpmlint tracker: https://bugzilla.redhat.com/show_bug.cgi?id=555284
autoqa-devel@lists.fedorahosted.org