https://bugzilla.redhat.com/show_bug.cgi?id=1055378 --- Comment #27 from Michael Friedrich <michael.friedrich@xxxxxxxxx> --- (In reply to Michael Scherer from comment #26) > - Why is there gui and gui-config, if there is only 1 single gui-config > package, couldn't they be merged to simplify packaging ? Icinga 2 ships its own configuration required for Icinga Classic UI (standalone installation) [0]. Therefore it was reasonable to split the configuration, and let 2 packages provide it - icinga-gui-config and icinga2-classicui-config. The latter is provided by Icinga 2 (upstream only, there's a pending review request for fedora too). Icinga 2.0.0 Beta 1 will be released tomorrow [1] btw. If Fedora decides to solve that in a different manner, it's totally fine. Community members are just using Classic UI or Web 1.x with Icinga 1.x and 2.x, but long-term the in-development Icinga Web 2 shall be used with Icinga 2. > - Could upstream be notified for the config.guess / config.sub issue ( so we > can drop the explicit requires on libtool ) ? Which issue exactly (didn't find it in the history)? And yes, notifying upstream is very easy. Either create a new issue at https://dev.icinga.org or tell Shawn or Sam to do so ;-) [0] https://github.com/Icinga/icinga2/blob/next/icinga2.spec#L207 [1] https://dev.icinga.org/projects/i2/roadmap -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review