From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1) Gecko/2008071615 Fedora/3.0.1-1.fc9 Firefox/3.0.1 Description of problem: rpmlint seems to be giving an invalid unversioned-explicit-obsoletes warning on my spec file. Version-Release number of selected component (if applicable): rpmlint-0.83-1.fc9.noarch How reproducible: Always Steps to Reproduce: 1.rpmlint eclipse-nls.spec Actual Results: I got the error "eclipse-nls.spec:36: W: unversioned-explicit-obsoletes \" Expected Results: No error message, at least for that line of the spec file. Additional info: The spec file line in question does contain a version: Obsoletes: eclipse-sdk-nls-%1 <= 3.2.1 \ The backslash at the end is there because this is part of a multi-line macro definition. See the attachment.
Created attachment 312747 [details] Example spec file which produces unversioned-explicit-obsoletes warning
rpmlint probably has quite a few other potential issues with multiline macro definitions, but I put a hack for this specific case upstream; this will probably be in the next upstream post 0.84 release: http://rpmlint.zarb.org/cgi-bin/trac.cgi/changeset/1447
rpmlint-0.85-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/rpmlint-0.85-1.fc9
rpmlint-0.85-1.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update rpmlint'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-9125
Looks good to me.
rpmlint-0.85-2.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
rpmlint-0.85-2.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/rpmlint-0.85-2.fc10
rpmlint-0.85-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.