[dev.icinga.com #3968] RPM issue with Amazon #1099
Comments
Updated by maxhyjalsoul on 2013-04-16 02:26:21 +00:00 When I tried to build icinga-web rpm using the spec file provided under httpd 2.4, I had to change, rpmbuild complained about %{phpname} too. I had to change them to php54/php53 to be able to continue the build process. |
Updated by maxhyjalsoul on 2013-04-17 01:23:01 +00:00 spec file failed on some OS (possibly different rpmdevtools version?) please fix a major issue in icinga-web.spec: |
Updated by mfrosch on 2013-04-17 08:22:00 +00:00
|
Updated by mfrosch on 2013-04-17 08:23:55 +00:00
Could you please share us the whole spec file that worked for you? Which vendor tag does Amazon use? "amazon"? |
Updated by maxhyjalsoul on 2013-04-18 23:16:29 +00:00
I believe "Amazon Linux AMI" is the tag they use: I'll attach the .spec file I hacked and used, but I had to comment out lines that have anything to do with Suse to get it work besides fixing the missing quotes, not sure why... |
Updated by mfriedrich on 2013-04-19 09:46:56 +00:00
removing the release target, requires more feedback and tests. |
Updated by mfrosch on 2013-10-02 08:45:13 +00:00
If someone could supply a fixed and tested version of our current Spec for Amazon Linux, I'm happy to include it. Until then: stalled |
Updated by mfriedrich on 2015-03-12 19:43:30 +00:00
|
Updated by mfriedrich on 2015-04-26 08:59:53 +00:00
|
Updated by berk on 2015-05-18 12:17:43 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/3968
Created by maxhyjalsoul on 2013-04-16 02:22:30 +00:00
Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-05-18 12:17:43 +00:00 (in Redmine)
Icinga-web 1.8.3 rpm build failed with error:
/bin/sh: line 0: printf: `{': invalid format character
Please check the new Apache2 configuration (/home/makerpm/rpmbuild/BUILDROOT/icinga-web-1.8.3-1.amzn1.x86_64make: ***** [install-done] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.gZ64YZ (%install)
it didn't happen in the environment with httpd 2.2
I prefer using httpd2.4 unless icinga-web won't support httpd 2.2 for now...
Attachments
The text was updated successfully, but these errors were encountered: