stow was identified as a package possibly needing maintainer attention due to the F-20 unversioned doc dir change. The identification is not foolproof, it is basically this grep: grep -E "(/doc|_docdir|_defaultdocdir).+version" *.spec Please review your package and make the appropriate changes, if any. A good starting point is checking the lines output by the above grep for your specfile. For the vast majority of packages, after the changes, the expected outcome is that documentation dirs in /usr/share/doc should no longer contain the package version. More information and tips: https://fedoraproject.org/wiki/Changes/UnversionedDocdirs http://thread.gmane.org/gmane.linux.redhat.fedora.devel/183942/focus=183943 http://thread.gmane.org/gmane.linux.redhat.fedora.devel/183942/focus=183973
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
Requested for co-maintainership on https://admin.fedoraproject.org/pkgdb/acls/name/stow
ping assignee
stow-2.2.0-6.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/stow-2.2.0-6.fc20
(In reply to Robin Lee from comment #2) > Requested for co-maintainership on > https://admin.fedoraproject.org/pkgdb/acls/name/stow Added - thanks for the kind offer! Stow is generally unexciting to maintain (and that's a good thing!) - so the changelogs are dominated by spec bumps due to mass rebuilds; as such, when porting changes to older releases or EPEL, please use cherry-pick -x so the originating commit ID is identified. Should we branch for EPEL 7 too? not sure if it has stow as part of the base OS or not
(In reply to Michel Alexandre Salim from comment #5) > (In reply to Robin Lee from comment #2) > > Requested for co-maintainership on > > https://admin.fedoraproject.org/pkgdb/acls/name/stow > > Added - thanks for the kind offer! > > Stow is generally unexciting to maintain (and that's a good thing!) - so the > changelogs are dominated by spec bumps due to mass rebuilds; as such, when > porting changes to older releases or EPEL, please use cherry-pick -x so the > originating commit ID is identified. I usually do merge. > > Should we branch for EPEL 7 too? not sure if it has stow as part of the base > OS or not According to https://fedoraproject.org/wiki/EPEL/epel7, no. After all, I want to back port a patch to the Fedora version: http://git.savannah.gnu.org/cgit/stow.git/patch/?id=67936bd7de13713a38d11880f685f6187c408dc4 to fix a bug when an error messages going to be printed.
Package stow-2.2.0-6.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing stow-2.2.0-6.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-5257/stow-2.2.0-6.fc20 then log in and leave karma (feedback).
stow-2.2.0-6.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.