Hide Forgot
Description of problem: At the moment, rpmlint will complain (display warning) about 'unversioned-explicit-provides' for a file with absolute path. If you try to fix this by adding the %{version}, then checking again with rpmlint will lead to an error: > specfile-error error: line 11: Versioned file name not permitted The logic of this does not make any sense, and it should be changed, either in the code, or preferably in some default configuration of rpmlint. rpmlint shouldnt warn that something is wrong when fix would cause an error instead... And before we get to the discussion that specfile should not contain the 'Provides' with absolute path, I need to tell you that for some packages this is necessary (and most likely always will be). I'm taking care of tcsh, which as a shell, was always placed as /bin/tcsh. This is no longer true because of UsrMove, but we need to keep that 'Provides' in the specfile because of backwards compatibility. As a result, I always see an unnecessary warning in Bodhi after dist.rpmlint check. Version-Release number of selected component (if applicable): rpmlint-1.9-3.fc24.noarch How reproducible: Always Steps to Reproduce: 1. Create a specfile containing 'Provides: /bin/tcsh = %{version}' 2. Run rplint on the specfile. Actual results: Misleading warning about 'unversioned-explicit-provides /bin/tcsh' Expected results: No warning about 'unversioned-explicit-provides /bin/tcsh'.
(In reply to David Kaspar [Dee'Kej] from comment #0) > [...] then checking again with rpmlint will > lead to an error: > > specfile-error error: line 11: Versioned file name not permitted FWIW this error comes from rpm. > rpmlint shouldnt warn that something is wrong when fix would cause an error > instead... Agreed, it's probably best to stop complaining about versioned absolute-path Provides in rpmlint. Would you mind filing an upstream issue about this? https://github.com/rpm-software-management/rpmlint
(In reply to Ville Skyttä from comment #1) > Agreed, it's probably best to stop complaining about versioned absolute-path > Provides in rpmlint. Would you mind filing an upstream issue about this? > https://github.com/rpm-software-management/rpmlint Done! :)
Upstream has fixed this issue: https://github.com/rpm-software-management/rpmlint/issues/90 They also mention that there's an option to add our own filters into the default Fedora config - 'addFilter' to filter which we do not want to see.
rpmlint-1.9-7.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f341bddc4e
rpmlint-1.9-7.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-11eb2e80ae
rpmlint-1.9-7.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-f341bddc4e
rpmlint-1.9-7.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-11eb2e80ae
rpmlint-1.9-7.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
rpmlint-1.9-7.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.