There are multiple problems with copy-jdk-configs package including: - case where c-j-c gets into very first transaction is not handled properly [1], (dependence on programs/dirs, which may not exist, silent failures in anaconda) - unnecessary dependence on external programs from lua in general - hardcoded file lists - misleading error messages are sometimes printed by rpm [2] (probably related to deletion of empty directories) - weird corner cases in past [3] Goals: - use defensive programming approach: test that expected conditions are met (required dirs exist etc.), before taking any action - print meaningful messages warning/error messages when something goes wrong - get rid of dependence on external programs (from lua), use lua posix bindings instead [4] - expect that c-j-c package may get into very first transaction (in anaconda, root is empty when pretrans is ran), c-j-c should not do any actions then.. - change in list of config files of java packages should not require change in c-j-c package, nor should it require any weird hacks - rpm should not print any misleading messages caused by c-j-c's actions [2]. Even when content of any java package changes, modification to c-j-c package should not be necessary. - pay attention to corner cases - maintain backward compatibility with exiting java packages [1] https://bugzilla.redhat.com/show_bug.cgi?id=1620053 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1643469 [3] https://bugzilla.redhat.com/show_bug.cgi?id=1573163 [4] https://luaposix.github.io/luaposix/modules/posix.html
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.