Re: [cros-dev] File collisions when running build_img

[Mike Frysinger]

you can manually unmerge the vim packages and rerun build_packages to recover.

-mike

On Sat, May 7, 2022, 04:28 Jingwen Ye <jy...@cornell.edu> wrote:

>>> Extracting info

 * Package:    app-editors/vim-core-8.2.4586

 * Repository: portage-stable

 * USE:        elibc_glibc userland_GNU kernel_linux minimal amd64 abi_x86_64

 * FEATURES:   network-sandbox sandbox splitdebug userpriv usersandbox

 * Running stacked hooks for pre_pkg_setup

 *    sysroot_build_bin_dir ...

 [ ok ]

>>> Extracting app-editors/vim-core-8.2.4586

 * checking 357 files for package collisions

 * This package will overwrite one or more files that may belong to other

 * packages (see list below). You can use a command such as `portageq

 * owners / <filename>` to identify the installed package that owns a

 * file. If portageq reports that only one package owns a file then do

 * NOT file a bug report. A bug report is only useful if it identifies at

 * least two or more packages that are known to install the same file(s).

 * If a collision occurs and you can not explain where the file came from

 * then you should simply ignore the collision since there is not enough

 * information to determine if a real problem exists. Please do NOT file

 * a bug report at https://bugs.gentoo.org/ unless you report exactly

 * which two packages install the same file(s). See

 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how

 * to solve the problem. And once again, please do NOT file a bug report

 * unless you have completely understood the above message.

 *

 * Detected file collision(s):

 *

 *  /build/amd64-generic/usr/share/vim/vim82/defaults.vim

 *

 * Searching all installed packages for file collisions...

 *

 * Press Ctrl-C to Stop

 *

 * app-editors/vim-8.2.4328-r1:0::portage-stable

 *  /build/amd64-generic/usr/share/vim/vim82/defaults.vim

 *

 * Package 'app-editors/vim-core-8.2.4586' NOT merged due to file

 * collisions. If necessary, refer to your elog messages for the whole

 * content of the above message.

 *

 * When moving files between packages, you need to use blockers so portage can

 * cleanly & automatically migrate files between them. Missing blockers will

 * break developers & builders, so manually running `emerge -C` won't work.

 *

 * If you see this for packages you aren't working on, please file a new bug

 * at https://crbug.com/new so we can get the blockers added.

 *

 * Please see the documentation for more details:

 *   https://chromium.googlesource.com/chromiumos/docs/+/master/portage/ebuild_faq.md#How-do-I-handle-file-collision

It seems to be there is a collision between old version vim and new version vim. Can somebody give me a hint to solve this problem?

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-dev