Hide Forgot
Description of problem: # rpm -e redhat-lsb error: Failed dependencies: redhat-lsb is needed by (installed) tomcat6-0:6.0.24-35.el6_1.noarch /lib/lsb/init-functions is needed by (installed) tomcat6-0:6.0.24-35.el6_1.noarch Expected results: I'd rather not to install redhat-lsb and it's dependencies (foomatic, qt, cups, gstreamer, mesa, to name it few) all of those not really needed for tomcat operations.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: no tech note needed
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -no tech note needed+RHEL tomcat6 strives to have LSB compliant systemv init scripts. However, Java has been removed from the list of compliant binaries since 2011. Since tomcat runs in the JVM, there is little that can be done in addition to the init scrpt compliance. The redhat-lsb dependency can be removed with very little risk.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -RHEL tomcat6 strives to have LSB compliant systemv init scripts. However, Java has been removed from the list of compliant binaries since 2011. Since tomcat runs in the JVM, there is little that can be done in addition to the init scrpt compliance. The redhat-lsb dependency can be removed with very little risk.+RHEL tomcat6 strives to have LSB compliant systemv init scripts. However, Java was removed from the list of compliant binaries in 2011. Since Tomcat runs in the JVM, there is little that can be done in addition to init scrpt compliance. The redhat-lsb dependency can be removed with very little risk.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0945.html