Created attachment 1471305 [details] cms-autotest diff see attached diff - i won't care that much about whitespaces and rewrite test-hashes but detsroy a simple url-param 4 by spit out 3.3333333 in teh cleand HTML is unacceptable since i have no time and energy i will simply build our for 10 years slef maintained php-stack with bundeled library and i am dune
f**ck there is no bundeled libtidy in the php source tree, so going to simply rebuild the F27 src.prm This is the test message -- configure: WARNING: PHP is going to be linked with an external PCRE, --with-pcre-valgrind has no effect configure: WARNING: APCu has access to native rwlocks configure: WARNING: Phar: sha256/sha512 signature support disabled if ext/hash is built shared configure: error: Cannot find libtidy Fehler: Fehler-Status beim Beenden von /var/tmp/rpm-tmp.IdIuu9 (%build)
here you go: https://bugzilla.redhat.com/show_bug.cgi?id=1537853 tidy 6.5 is simply broken crap - it's that easy
Essentially a dup of bug #1537853
not really the main difference is that this did not made it to stable repos but now in f28 the damage is done - and converting integer params of an url to an arbitrary float is also new imagine the damage when you use libtidy to cleanup wysiwyg html code within a content management system at save - with that version fixing a simple typo may render the whole content broken
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.