./build_image --noenable_rootfs_verification dev

gistfile1.txt

coreos-init-0.0.1-r66:  * Press Ctrl-C to Stop
coreos-init-0.0.1-r66:  *
coreos-init-0.0.1-r66:  * coreos-base/coreos-cloudinit-0.1.2-r3:0::coreos
coreos-init-0.0.1-r66:  * 	/mnt/host/source/src/build/images/amd64-generic/260.0.0+2014-03-18-2313-a1/rootfs/usr/lib/systemd/system/coreos-cloudinit-oem.service
coreos-init-0.0.1-r66:  *
coreos-init-0.0.1-r66:  * Package 'coreos-base/coreos-init-0.0.1-r66' NOT merged due to file
coreos-init-0.0.1-r66:  * collisions. If necessary, refer to your elog messages for the whole
coreos-init-0.0.1-r66:  * content of the above message.
coreos-init-0.0.1-r66: >>> Failed to install coreos-base/coreos-init-0.0.1-r66 to /mnt/host/source/src/build/images/amd64-generic/260.0.0+2014-03-18-2313-a1/rootfs/, Log file:
coreos-init-0.0.1-r66: >>>  '/build/amd64-generic/tmp/portage/logs/coreos-base:coreos-init-0.0.1-r66:20140318-231940.log'
coreos-init-0.0.1-r66:
coreos-init-0.0.1-r66:  * Messages for package coreos-base/coreos-init-0.0.1-r66 merged to /mnt/host/source/src/build/images/amd64-generic/260.0.0+2014-03-18-2313-a1/rootfs/:
coreos-init-0.0.1-r66:
coreos-init-0.0.1-r66:  * This package will overwrite one or more files that may belong to other
coreos-init-0.0.1-r66:  * packages (see list below). You can use a command such as `portageq
coreos-init-0.0.1-r66:  * owners / <filename>` to identify the installed package that owns a
coreos-init-0.0.1-r66:  * file. If portageq reports that only one package owns a file then do
coreos-init-0.0.1-r66:  * NOT file a bug report. A bug report is only useful if it identifies at
coreos-init-0.0.1-r66:  * least two or more packages that are known to install the same file(s).
coreos-init-0.0.1-r66:  * If a collision occurs and you can not explain where the file came from
coreos-init-0.0.1-r66:  * then you should simply ignore the collision since there is not enough
coreos-init-0.0.1-r66:  * information to determine if a real problem exists. Please do NOT file
coreos-init-0.0.1-r66:  * a bug report at http://bugs.gentoo.org unless you report exactly which
coreos-init-0.0.1-r66:  * two packages install the same file(s). Once again, please do NOT file
coreos-init-0.0.1-r66:  * a bug report unless you have completely understood the above message.
coreos-init-0.0.1-r66:  *
coreos-init-0.0.1-r66:  * Detected file collision(s):
coreos-init-0.0.1-r66:  *
coreos-init-0.0.1-r66:  * 	/mnt/host/source/src/build/images/amd64-generic/260.0.0+2014-03-18-2313-a1/rootfs/usr/lib/systemd/system/coreos-cloudinit-oem.service
coreos-init-0.0.1-r66:  *
coreos-init-0.0.1-r66:  * Searching all installed packages for file collisions...
coreos-init-0.0.1-r66:  *
coreos-init-0.0.1-r66:  * Press Ctrl-C to Stop
coreos-init-0.0.1-r66:  *
coreos-init-0.0.1-r66:  * coreos-base/coreos-cloudinit-0.1.2-r3:0::coreos
coreos-init-0.0.1-r66:  * 	/mnt/host/source/src/build/images/amd64-generic/260.0.0+2014-03-18-2313-a1/rootfs/usr/lib/systemd/system/coreos-cloudinit-oem.service
coreos-init-0.0.1-r66:  *
coreos-init-0.0.1-r66:  * Package 'coreos-base/coreos-init-0.0.1-r66' NOT merged due to file
coreos-init-0.0.1-r66:  * collisions. If necessary, refer to your elog messages for the whole
coreos-init-0.0.1-r66:  * content of the above message.
=== Complete: job coreos-init-0.0.1-r66 (0m1.4s) ===
Failed coreos-base/coreos-init-0.0.1-r66 (in 0m1.4s). Your build has failed.
Pending 2/123, [Time 6m6.8s Load 1.15 0.87 0.49]
Cleaning up mounts
An error occurred in your build so your latest output directory is invalid.
Would you like to delete the output directory (y/N)?