5508 2013-11-07 20:01:05 +0000 build for machine imx28evk is failing 2013-11-22 13:18:39 +0000 1 1 7 Build System, Metadata & Runtime OE-Core graphics unspecified Other Multiple RESOLVED FIXED autobuilder Medium normal 1.6 1 nitin.a.kamble richard.purdie jessica.zhang meta.mr.watcher meta.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 38672 0 nitin.a.kamble 2013-11-07 20:01:05 +0000 Error log link: http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm/builds/326/steps/Building%20Toolchain%20Images_1/logs/stdio Build Configuration: BB_VERSION = "1.21.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "RedHatEnterpriseServer-6.4" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "imx53qsb" DISTRO = "poky" DISTRO_VERSION = "1.5+snapshot-20131106" TUNE_FEATURES = "armv7a vfp neon" TARGET_FPU = "vfp-neon" meta meta-yocto meta-yocto-bsp = "master:d6cc7c8ed76c8b1117cf03c7bd4b0742f98f79b3" meta-fsl-arm = "master:b91173244b4b7a3d5e90ea21e67db18640358d1b" meta-qt3 = "master:b73552fb998fd30a01dbee5a172e432a16078222" ... | Processing files: nativesdk-libxcb-xinerama0-1.9.1-r0.x86_64_nativesdk | error: File not found: /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-fsl-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-libxcb/1.9.1-r0/package/DEBIAN | | | RPM build errors: | File not found: /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-fsl-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-libxcb/1.9.1-r0/package/DEBIAN | WARNING: /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-fsl-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-libxcb/1.9.1-r0/temp/run.BUILDSPEC.10603:1 exit 1 from | rpmbuild --nodeps --short-circuit --target x86_64_nativesdk-pokysdk-linux --buildroot /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-fsl-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-libxcb/1.9.1-r0/package --define '_topdir /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-fsl-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-libxcb/1.9.1-r0' --define '_rpmdir /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-fsl-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-libxcb/1.9.1-r0/deploy-rpms/x86_64_nativesdk' --define '_build_name_fmt %%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm' --define '_use_internal_dependency_generator 0' --define '__find_requires %{nil}' --define '__find_provides %{nil}' --define '_unpackaged_files_terminate_build 0' --define 'debug_package %{nil}' --define '_rpmfc_magic_path /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-fsl-arm/build/build/tmp/sysroots/x86_64-linux/usr/share/misc/magic.mgc' --define '_tmppath /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-fsl-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-libxcb/1.9.1-r0' -bb /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-fsl-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-libxcb/1.9.1-r0/libxcb.spec | DEBUG: Python function do_package_rpm finished | DEBUG: Python function do_package_write_rpm finished | ERROR: Function failed: BUILDSPEC (log file is located at /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-fsl-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-libxcb/1.9.1-r0/temp/log.do_package_write_rpm.10603) NOTE: recipe nativesdk-libxcb-1.9.1-r0: task do_package_write_rpm: Failed 38781 1 richard.purdie 2013-11-14 15:39:10 +0000 This is just after the package race fixes. Which should have avoided these kind of errors :( 38828 2 richard.purdie 2013-11-15 14:29:43 +0000 libxcb.spec contains: %files -n nativesdk-libxcb-xinerama0 %defattr(-,-,-,-) %dir "/opt" "/DEBIAN" %dir "/opt/poky" %dir "/opt/poky/1.5+snapshot" %dir "/opt/poky/1.5+snapshot/sysroot The only way /DEBIAN can have got there is from walk_files() in package_rpm.bbclass having had file == "DEBIAN" at some point. Since this is a directory, its hard to understand what is going on :( 39029 3 richard.purdie 2013-11-22 13:18:39 +0000 We're not seeing this on the autobuilders so I'm going to mark this as resolved as I believe the changes did go in to fix this. It could have been due to the various fetch related issues on the autobuilder. We can reopen if we see the problem again.