owncloud-csync 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
I am currently testing the RC version of the owncloud-csync with this bug corrected.
mirall-1.4.0-2.fc19,owncloud-csync-0.90.0-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mirall-1.4.0-2.fc19,owncloud-csync-0.90.0-1.fc19
owncloud-csync-0.90.0-1.fc20,mirall-1.4.0-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/owncloud-csync-0.90.0-1.fc20,mirall-1.4.0-2.fc20
Package mirall-1.4.0-2.fc19, owncloud-csync-0.90.0-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mirall-1.4.0-2.fc19 owncloud-csync-0.90.0-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-15831/mirall-1.4.0-2.fc19,owncloud-csync-0.90.0-1.fc19 then log in and leave karma (feedback).
mirall-1.4.0-2.fc19, owncloud-csync-0.90.0-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
owncloud-csync-0.90.0-1.fc20, mirall-1.4.0-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.