[dev.icinga.com #8128] Icinga 2.2.2 build fails on SLES11SP3 because of changed boost dependency

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/8128

Created by theh on 2014-12-19 12:30:54 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2015-02-05 09:18:33 +00:00)
Target Version: 2.2.4
Last Update: 2015-02-05 09:18:33 +00:00 (in Redmine)

Icinga Version: 2.2.2
Backport?: Already backported

---

Icinga 2.2.2 couldn't be built with the additional boost-library anymore on SLES11SP3 since the dependency was changed: https://build.opensuse.org/package/show/server:monitoring:icinga2/icinga2

I think it would be best to just use "BuildRequires: boost-devel >= 1.41" for all SUSE distributions instead of requiring one specific version.

Changesets

2014-12-19 13:06:09 +00:00 by theh dfc90ab

Require boost-devel >= 1.41 for all SUSE distributions

Instead of requiring one specific boost version the minimal build
requirement is used on SUSE distributions for the boost library.

This fixes building on SLES11SP3.

refs #8128

2015-02-05 09:16:05 +00:00 by (unknown) 090aae0

Use the %build_icinga_org RPM macro for package dependencies which are specific to build.icinga.org

fixes #8128

2015-02-05 09:17:34 +00:00 by (unknown) 007fa8a

Use the %build_icinga_org RPM macro for package dependencies which are specific to build.icinga.org

fixes #8128

[icinga-migration]

Updated by gbeutner on 2014-12-19 16:20:31 +00:00

• Status changed from New to Feedback

We have to build our own boost packages for packages.icinga.org because the upstream package in SLES 11 SP3 is too old (1.36). Our own package has a different name (boost153) and installs in /usr/lib/boost153 and /usr/include/boost153 so that it doesn't conflict with the upstream package.

I'm open to suggestions how we can improve this.

[icinga-migration]

Updated by gbeutner on 2014-12-19 20:22:58 +00:00

 shroud: patching only our file would be Ok, but this would be the second change and I like having an upstream spec :)
 what's the other change?
 i guess one thing we could do is to introduce an rpm macro which hides all the boost153 crap - and is only set for our packages.icinga.org builds
 shroud: the other change is our different icinga-gui path
 shroud: a macro would be good idea, we use a similar thing for icinga1, nagios and so on.

[icinga-migration]

Updated by mfriedrich on 2015-01-09 10:58:25 +00:00

• Target Version changed from 2.2.3 to 2.2.4

[icinga-migration]

Updated by mfriedrich on 2015-01-23 09:44:55 +00:00

• Status changed from Feedback to New
• Assigned to deleted theh

[icinga-migration]

Updated by gbeutner on 2015-02-05 09:17:55 +00:00

• Status changed from New to Assigned
• Assigned to set to gbeutner

[icinga-migration]

Updated by gbeutner on 2015-02-05 09:18:04 +00:00

• Backport? changed from __ to Yes

[icinga-migration]

Updated by Anonymous on 2015-02-05 09:18:33 +00:00

• Status changed from Assigned to Resolved
• Done % changed from 0 to 100

Applied in changeset 090aae0.