app-editors/vim-7.2 installs files without writing that to /var/db/pkg/app-editors/CONTENTS. It makes it hard to find out where some files with slightly ambiguous names come from, and also creates a file collision error when re-emerging vim. Reproducible: Always Steps to Reproduce: 1. emerge vim 2. check CONTENTS: $ cat /var/db/pkg/app-editors/vim-7.2/CONTENTS dir /usr dir /usr/bin obj /usr/bin/vim e7df3c7540abc52a37f0b9fea09fd769 1234004522 sym /usr/bin/rvim -> vim 1234004524 sym /usr/bin/vimdiff -> vim 1234004524 sym /usr/bin/rview -> vim 1234004524 dir /usr/share dir /usr/share/bash-completion obj /usr/share/bash-completion/vim 87fe7821e180647f3bf48ed099a22b83 1234004521 dir /usr/lib dir /usr/lib/debug dir /usr/lib/debug/usr dir /usr/lib/debug/usr/bin obj /usr/lib/debug/usr/bin/vim.debug c9b9f0d77cb78dbfdb9311cb78e71d72 1234004522 $ ls -l /usr/bin/view lrwxrwxrwx 1 root root 13 Oct 6 23:21 /usr/bin/view -> //usr/bin/vim $ man -k vim evim (1) - easy Vim, edit a file with Vim and setup for modeless editing vim (1) - Vi IMproved, a programmers text editor vimdiff (1) - edit two or three versions of a file with Vim and show differences vimdiff (1) - edit two, three or four versions of a file with Vim and show differences vimtutor (1) - the Vim tutor 3. emerge -C vim && emerge vim Actual Results: * package app-editors/vim-7.2 NOT merged * * Detected file collision(s): * * /usr/bin/vim * /usr/bin/rvim * /usr/bin/vimdiff * /usr/bin/rview * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). Expected Results: All installed files are added to the vdb.
The four files portage complained about are all present in the CONTENTS you showed. The only files installed without the package manager knowing are the symlinks created and managed by eselect vi, and those are not specific to vim so they shouldn't be in vim's CONTENTS. What was the output of emerge -C vim? Did it show any reason why it did not remove the files? Please also provide the output of emerge --info.
Created attachment 181271 [details] emerge --info > The four files portage complained about are all present in the CONTENTS you > showed. The only files installed without the package manager knowing are the > symlinks created and managed by eselect vi, and those are not specific to vim > so they shouldn't be in vim's CONTENTS. Oh, okay, thanks for explaining that. It might be good if, when emerge -C vim calls 'eselect vi update', it properly cleans up the files it created. > What was the output of emerge -C vim? # emerge -C vim app-editors/vim selected: 7.2 protected: none omitted: none >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging app-editors/vim-7.2... * Updating documentation tags in //usr/share/vim/vim72 * Calling eselect vi update... * GNU info directory index is up-to-date.(In reply to comment #1) > Did it show any reason why it did not remove the files? Not that I can see... > Please also provide the output of emerge --info. Attached it. Thanks for your help.
(In reply to comment #2) > Oh, okay, thanks for explaining that. It might be good if, when emerge -C vim > calls 'eselect vi update', it properly cleans up the files it created. Yes, that would be good, and it normally does that already. However, if /usr/bin/vim is not removed, eselect vi does not know that anything needs to be updated. Assigning to the vim team.
Can't reproduce with newest stable version of vim, so closing as FIXED.
