Advertisement
ftab

most is trying to install files that already exist?

Jun 25th, 2017
194
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.27 KB | None | 0 0
  1. ERROR: most-0.1-r0 do_package_write_rpm: The recipe most is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
  2. /home/build/agl/build-qemu/tmp/deploy/rpm/qemux86_64/kernel-module-mostcore-0.1-r0.qemux86_64.rpm
  3. Matched in b'manifest-qemux86_64-mostcore.package_write_rpm'
  4. /home/build/agl/build-qemu/tmp/deploy/rpm/qemux86_64/kernel-module-aim-network-0.1-r0.qemux86_64.rpm
  5. Matched in b'manifest-qemux86_64-aim-network.package_write_rpm'
  6. /home/build/agl/build-qemu/tmp/deploy/rpm/qemux86_64/kernel-module-hdm-usb-0.1-r0.qemux86_64.rpm
  7. Matched in b'manifest-qemux86_64-hdm-usb.package_write_rpm'
  8. /home/build/agl/build-qemu/tmp/deploy/rpm/qemux86_64/kernel-module-aim-sound-0.1-r0.qemux86_64.rpm
  9. Matched in b'manifest-qemux86_64-aim-sound.package_write_rpm'
  10. /home/build/agl/build-qemu/tmp/deploy/rpm/qemux86_64/kernel-module-aim-v4l2-0.1-r0.qemux86_64.rpm
  11. Matched in b'manifest-qemux86_64-aim-v4l2.package_write_rpm'
  12. /home/build/agl/build-qemu/tmp/deploy/rpm/qemux86_64/kernel-module-hdm-dim2-0.1-r0.qemux86_64.rpm
  13. Matched in b'manifest-qemux86_64-hdm-dim2.package_write_rpm'
  14. /home/build/agl/build-qemu/tmp/deploy/rpm/qemux86_64/kernel-module-hdm-i2c-0.1-r0.qemux86_64.rpm
  15. Matched in b'manifest-qemux86_64-hdm-i2c.package_write_rpm'
  16. /home/build/agl/build-qemu/tmp/deploy/rpm/qemux86_64/kernel-module-aim-cdev-0.1-r0.qemux86_64.rpm
  17. Matched in b'manifest-qemux86_64-aim-cdev.package_write_rpm'
  18. Please verify which recipe should provide the above files.
  19. The build has stopped as continuing in this scenario WILL break things, if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error however switching DISTRO_FEATURES on an existing build directory is not supported, you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above.
  20. ERROR: most-0.1-r0 do_package_write_rpm: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases.
  21. ERROR: most-0.1-r0 do_package_write_rpm: Function failed: sstate_task_postfunc
  22. ERROR: Logfile of failure stored in: /home/build/agl/build-qemu/tmp/work/qemux86_64-agl-linux/most/0.1-r0/temp/log.do_package_write_rpm.30015
  23. ERROR: Task (/home/build/agl/meta-agl-demo/recipes-kernel/most/most.bb:do_package_write_rpm) failed with exit code '1'
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement