Hi Rex, That's me again. Thanks for your help. Do you mind requesting the branches and building tidy? If you fork it from src.fedoraproject.org it will be built right away, no issues, I just tested. Thank you very much. - Breno
@Breno tidy is already available in epel-playground (version 5.6.0-5.epel8.playground) @Rex this playground is probably going to be a nightmare, as all packages using it will have to also be in playground.... And for ex php-extras have some dependencies in epel, some in epel-playground... :(
I didn't build it, it was done by others for plasma-related stuff also in playground. will need to rethink it, probably to move out of playground.
I was the person who built it in playground. It was because I needed it for the KDE build. Playground packages can use regular EPEL packages, they don't *all* have to be in playground. If the regular maintainer wants to build it in regular EPEL8, that is fine. I will take it out of -playground. Just let me know what you want to do.
OK, move it to epel8 then, thanks. (or let me know how to do it, and I can... otherwise, I'll probably figure it out from what you commit. :) )
FEDORA-EPEL-2019-8bcf2e0971 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-8bcf2e0971
Since I am not the main maintainer of the package, I grabbed the package from the latest stable fedora release, in this case, F30. I knew that it builds and runs fine without any changes to the spec file. fedpkg clone tidy cd tidy fedpkg switch-branch f30 fedpkg switch-branch epel8 git merge f30 fedpkg push fedpkg build
tidy-5.6.0-5.el8 has been pushed to the Fedora EPEL 8 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-EPEL-2019-8bcf2e0971
tidy-5.6.0-5.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report.