Many server environments are "headless" systems without need for an X-server. The current ebuilds for heartbeat IMO incorrectly force a pygtk dependency when the "management" USE flag is enabled. The "management" use flag is used to pass the "--enable-mgmtd" flag to configure when building the heartbeat package. This instructs the build to add the "mgmtd" program, which lets the server be administered (remotely with headless systems) with the haclient.py GUI (which is also built). However, on a headless system, because of the forced dependency, the emerge adds 32 unnecessary packages, and ultimately fails with errors about package dependencies not being built with the "X" use flag. The pygtk dependency is completely unnecessary for the mgmtd program to be added to the server, and removing it from the ebuild allows the emerge to complete without any unnecessary packages, or compile failures! I believe the ebuild designer has incorrectly assumed that anyone who wants to run the GUI will only run it on the server being administered. The pygtk dependency is indeed required for the GUI (but not for the server-side mgmtd!). I cannot speak for others, but this is the second cluster environment I've built, which is headless and administered remotely, and has run afoul of this issue. I can only assume that there are other server administrators who also run "headless" servers, who could also benefit from the following proposed fix: I believe all ebuilds should be modified to remove the ">=dev-python/pygtk-2.4" dependency for the "management" USE flag (the build proceeds just fine without these dependencies). Then a new USE flag (perhaps "management-gui"?) be added for the sole purpose of forcing the pygtk dependency to allow the GUI to be run locally. The ebuild could then emit a warning when built with "management" and without "management-gui" that "management-gui" is required to run the GUI locally. One other minor nit: the "management" flag should also force the addition of the "haclient" group. The GUI fails to connect to the server unless the user is a member of the "haclient" group.
Something required for properly working application is not "incorrectly forcing a dependency." Fixing summary accordingly.
I don't agree. I've got to go modify the ebuild and remove the dependency to be able to build a "properly working application", and I doubt others will know they can do this. Unfortunately, the heartbeat developer has decided to put both the GUI and the management daemon under the same configure option, so we really don't have any way of "making the management GUI optional". I think your title change and priority adjustments relegate this bug to something that cannot and will not get done. If you don't think my bug report is valid, or of any use to others, just delete it.
Jerry, I'll try to update my 2.1.3 ebuild at http://overlays.gentoo.org/dev/wschlich/browser/testing/sys-cluster/heartbeat in order to reflect the change you proposed. Thanks!
(In reply to comment #3) > Jerry, I'll try to update my 2.1.3 ebuild at > http://overlays.gentoo.org/dev/wschlich/browser/testing/sys-cluster/heartbeat > in order to reflect the change you proposed. Thanks! > Wolfram, Thanks for looking at this. I'm all set - I just hack the ebuild for my use - but maybe your changes will help someone else out. I hope so!
Created attachment 150957 [details, diff] Patch with the changes proposed in the bug report; update for new gentoo bindnow-flags methodology
(In reply to comment #5) > Created an attachment (id=150957) Hello, if I understand aright, on "real" cluster nodes I install with "+management -management-gui". On a X-workstation I must have "sys-cluster/heartbeat -management +management-gui" without a relevant 'ha.cf'?
+ 18 Oct 2011; Kacper Kowalik <xarthisius@gentoo.org> -heartbeat-1.2.5.ebuild, + -heartbeat-1.2.5-r1.ebuild, -heartbeat-2.0.7-r2.ebuild, + -files/heartbeat-2.0.7-update-resources-failcount.patch, + -heartbeat-2.0.8.ebuild, -files/heartbeat-2.0.8-asneeded.patch, + -files/heartbeat-2.0.8-crm-assert.patch, + -files/heartbeat-2.0.8-crm-leaks.patch, -files/heartbeat-2.0.8-delay.patch, + -files/heartbeat-2.0.8-glibc.patch, -files/heartbeat-2.0.8-install_fix.patch, + -heartbeat-3.0.4-r1.ebuild: + Drop ancient and unusable versions of heartbeat-{1,2} since we have + heartbeat-3 stable
