[opensuse-buildservice] Need help with build failure
Hi, I could use some help with a build failure: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=cloudstack&project=Virtualization%3ACloud%3ACloudStack%3ATesting&repository=SLE_11_SP2 The problem occurs after the built rpms have been installed. After this step some checks are running. The end of the build log shows the following: cloud-usage-3.0.1-5.1 ... running 01-check-debuginfo ... testing for empty debuginfo packages ... running 02-check-gcc-output ... testing for serious compiler warnings (using /usr/lib/build/checks-data/check_gcc_output) (using //.build.log) ... running 03-check-binary-kernel-log ... running 04-check-filelist ... checking filelist cloud-client: "/etc/sysconfig/cloud-management" is not allowed anymore in SuSE Linux. chown: missing operand after `/' Try `chown --help' for more information. [ 221.744172] System halted. I have no idea what do to with the chown error. There is a "chown" call in one of the initscripts in the packages, but the %post scripts that activate the initscripts are are disabled with %if ! 0%{?opensuse_bs} ... %endif Help is appreciated. Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-----Original Message----- From: Robert Schweikert [mailto:rjschwei@suse.com] Sent: Thursday, April 26, 2012 1:50 PM To: obs Subject: [opensuse-buildservice] Need help with build failure [...} cloud-usage-3.0.1-5.1 ... running 01-check-debuginfo ... testing for empty debuginfo packages ... running 02-check-gcc-output ... testing for serious compiler warnings (using /usr/lib/build/checks-data/check_gcc_output) (using //.build.log) ... running 03-check-binary-kernel-log ... running 04-check-filelist ... checking filelist cloud-client: "/etc/sysconfig/cloud-management" is not allowed anymore in SuSE Linux. chown: missing operand after `/' Try `chown --help' for more information. [ 221.744172] System halted.
I have no idea what do to with the chown error. There is a "chown" call in one of the initscripts in the packages, but the %post scripts that activate the initscripts are are disabled with
I'm not sure where the chown error comes from but it seems to be harmless, since I have that in almost all my OBS buildlogs, including successful ones. The REAL error message is the line above: cloud-client: "/etc/sysconfig/cloud-management" is not allowed anymore in SuSE Linux. That is what causes the build to fail. Gruesse, Frank -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Apr 26, 2012 at 01:14:24PM +0100, Frank Lichtenheld wrote:
I'm not sure where the chown error comes from but it seems to be harmless, since I have that in almost all my OBS buildlogs, including successful ones. The REAL error message is the line above: cloud-client: "/etc/sysconfig/cloud-management" is not allowed anymore in SuSE Linux. That is what causes the build to fail.
Yes, the "chown" error is a glitch in the build script, I just fixed it. Please simply ignore the line unless the fix is deployed. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 04/26/2012 08:57 AM, Michael Schroeder wrote:
On Thu, Apr 26, 2012 at 01:14:24PM +0100, Frank Lichtenheld wrote:
I'm not sure where the chown error comes from but it seems to be harmless, since I have that in almost all my OBS buildlogs, including successful ones. The REAL error message is the line above: cloud-client: "/etc/sysconfig/cloud-management" is not allowed anymore in SuSE Linux. That is what causes the build to fail.
Yes, the "chown" error is a glitch in the build script, I just fixed it. Please simply ignore the line unless the fix is deployed.
OK, so how do I deal with cloud-client: "/etc/sysconfig/cloud-management" is not allowed anymore in SuSE Linux. The upstream code still uses the sysconfig location. Where should this be moved to? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-----Original Message----- From: Robert Schweikert [mailto:rjschwei@suse.com] Sent: Thursday, April 26, 2012 3:20 PM To: obs Subject: Re: [opensuse-buildservice] Need help with build failure
On 04/26/2012 08:57 AM, Michael Schroeder wrote:
On Thu, Apr 26, 2012 at 01:14:24PM +0100, Frank Lichtenheld wrote:
I'm not sure where the chown error comes from but it seems to be harmless, since I have that in almost all my OBS buildlogs, including successful ones. The REAL error message is the line above: cloud-client: "/etc/sysconfig/cloud-management" is not allowed anymore in SuSE Linux. That is what causes the build to fail.
Yes, the "chown" error is a glitch in the build script, I just fixed it. Please simply ignore the line unless the fix is deployed.
OK, so how do I deal with
cloud-client: "/etc/sysconfig/cloud-management" is not allowed anymore in SuSE Linux.
The upstream code still uses the sysconfig location. Where should this be moved to?
You probably need to use fillup. See e.g. http://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#.25fillup_a... (couldn't find a better documentation) Gruesse, Frank -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Frank Lichtenheld -
Michael Schroeder -
Robert Schweikert