7913 2015-06-20 15:44:28 +0000 tar now being grumpy about -ps options incorrectly used with -c 2015-09-09 11:32:18 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified x86 Multiple VERIFIED INVALID Medium major 1.9 1 chrisc chrisc bogdanx.a.voiculescu meta.mr.watcher meta.watcher poky.bs.watcher poky.watcher richard.purdie ross.burton bogdanx.a.voiculescu --- --- No (bug/feature does not impact docs) oldest_to_newest 51835 0 chrisc 2015-06-20 15:44:28 +0000 Files effected: meta/classes/staging.bbclass bitbake/lib/bb/fetch2/__init__.py meta/lib/oe/path.py meta/lib/oe/path.pyc meta/classes/package.bbclass meta/classes/libc-package.bbclass Description of error: Newer versions of tar will complain (fail) if the -ps options are used in conjunction with the -c (create) option. The -ps options seem to belong in the -x (extraction) phase. Example: tar -cf - -C "$src" -ps . | tar -xf - -C "$dest" becomes tar -cf - -C "$src" . | tar -xpsf - -C "$dest" Behaviour: DEBUG: Executing python function sstate_task_prefunc DEBUG: Python function sstate_task_prefunc finished DEBUG: Executing python function do_populate_sysroot DEBUG: Executing shell function sysroot_stage_all tar: --same-order option cannot be used with -c Try 'tar --help' or 'tar --usage' for more information. tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors DEBUG: Python function do_populate_sysroot finished ERROR: Function failed: sysroot_stage_all (see /u/work/yoctoProject/raspberryPiB uild/tmp/work/x86_64-linux/quilt-native/0.60-r0/temp/log.do_populate_sysroot.171 88 for further information) 51925 1 richard.purdie 2015-06-25 14:38:01 +0000 Which release are you seeing this with? This was fixed in master and at least a couple of releases back if I recall correctly? 51926 2 richard.purdie 2015-06-25 14:39:55 +0000 Please let us know which release this was with. 51928 3 ross.burton 2015-06-25 14:46:45 +0000 The error includes the path quilt-0.60. This was removed in commit 7579e19: commit 7579e19c2b67819a6b5b1324567564d1e4125bdc Author: Chong Lu <Chong.Lu@windriver.com> Date: Fri Dec 27 18:17:40 2013 +0800 quilt: upgrade to 0.61 So what releases did that come from: $ git tag --contains 7579e19c2b67819a6b5b1324567564d1e4125bdc|grep yocto- yocto-1.6 yocto-1.6.1 yocto-1.6.2 yocto-1.6.3 yocto-1.7 yocto-1.7.1 yocto-1.7.2 yocto-1.8 I'm guessing the reporter is using 1.5, which is "quite" old now. 51930 4 ross.burton 2015-06-25 14:49:43 +0000 Fixed in oe-core 3d5a6d0a480a0fa98260a3b3ffc71b8d9e3e58af: Date: Fri Oct 11 23:01:54 2013 +0100 classes: tar 1.27 fixes tar version 1.27 returns: tar: --same-order option cannot be used with -c with the commandlines we have been using. We can remove the -s option (which is --same-order) to remove the error. 51940 5 chrisc 2015-06-25 15:51:19 +0000 Great question. I utilized: git clone git://git.yoctoproject.org/poky yoctoProject to retrieve the project instead of a tarball. I found __version__=1.17.0 in the bitbake script and 1.9x in the Bitbake ChangeLog. What would be the best method of determining the projects version? 51941 6 ross.burton 2015-06-25 15:54:53 +0000 Then "git show" will tell you what commit you're using, and we can use that to determine what release. But the fact remains that your build is using quilt 0.60, which was removed in 2013, so you're not using master, or 1.8, or 1.7, or 1.6. Did you switch to a branch after cloning? 51971 7 chrisc 2015-06-26 21:50:21 +0000 Gad's, was just following the authors instructions without understanding git. I jumped back to commit 4a36a32567ecfbc7ce7b967803e6e23314953ef5 I thought I was helping by identifying the issue and files involved. I did not know I was utilizing ancient code. Thanks for the rapid response. RESOLVED, FIXED (Long ago) 51977 8 ross.burton 2015-06-27 22:26:50 +0000 No problem - always good to file an issue! Thanks for being responsive and getting this closed smoothly. Also that oe-core commit is *old*, looks like it was part of 1.4.1. You might want to find newer instructions, or just attempt what you're doing with the latest releases. 53872 9 bogdanx.a.voiculescu 2015-09-09 11:21:10 +0000 this was a bug fixed "RESOLVED, FIXED (Long ago)" so it was not a regression, because the reporter used an older git.