Description of problem: asciidoc is written in python2, which become deprecated in near future. This package should be python3 compatible.
asciidoc-8.6.10-0.1.20180605git986f99d.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-9d3309122b
asciidoc-8.6.10-0.1.20180605git986f99d.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-245bdb7431
asciidoc-8.6.10-0.1.20180605git986f99d.fc27 has been pushed to the Fedora 27 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-2018-9d3309122b
asciidoc-8.6.10-0.1.20180605git986f99d.fc28 has been pushed to the Fedora 28 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-2018-245bdb7431
I'm not so sure these changes should be applied stable releases. Anyone using the asciidoc API from python2 will find this support suddenly removed after these packages reach the stable repository. This seems like something that should be in rawhide for f29 and later, IMO. The changes look good and in a little testing the output hasn't changed in any significant way while building the git documentation, so that's reassuring. Thanks for working on this Josef.
With 8.6.10 snapshots in updates testing for f27/f28, if it is agreed that dropping the python2 API is not suitable for stable releases, our options are to add an epoch or to update to the official 8.6.10 release, which still uses python2. The latter seems like a better choice, though I haven't looked closely at 8.6.10 to see if there are any changes which would be a concern. I made the changes needed on the f27/f28 branches of https://src.fedoraproject.org/fork/tmz/rpms/asciidoc. (There are a few rpmlint errors and warnings I'm working on cleaning up now as well.)
There's a bug with the use of str.decode() which doesn't exist in 3.6. The error is around line 263 where it attempts to decode a string based on the xml encoding. I was able to trigger the bug using xhtml as the output format.
Thanks for reporting that issue here and upstream Lee! (The upstream report is here: https://github.com/asciidoc/asciidoc-py3/issues/16) That is further support for _not_ pushing the python3 changes to the stable f27/f28 releases. I filed https://src.fedoraproject.org/rpms/asciidoc/pull-request/2 with a few changes on top of master to use the upstream tarball rather than downloading an manually renaming it) as well as fixing most of the rpmlint issues. Then I merged that down to the f28/f28 branches in my fork and added a commit on top which updates those branches to the official 8.6.10 release (the python2 version). That will allow a clean update path for users of the current packages in updates-testing. (It does leave a minor issue with rawhide having an older NEVRA, so we might need to adjust the release tag to ensure a clean upgrade from f27/f28 to f29.) That change is here: https://src.fedoraproject.org/fork/tmz/rpms/asciidoc/c/54f93fe. Thoughts and comments?
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
asciidoc-8.6.10-0.1.20180605git986f99d.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.