As in subject.
Stopped for file collision in file
Steps to Reproduce:
verified at update of app-vim/gtk-syntax-20091024
Created attachment 295001 [details]
logs and info
Do you know which package did that previously belong to ?
Otherwise it's unlikely to be fixed.
(I've seen that warning too, but without 'strict' in FEATURES it merged fine, as it was checked as previously unowned.)
No package claimed the file.
(In reply to comment #3)
> No package claimed the file.
Well, the little catch here is that while the above is true, it bit too much of coincidence, that I've seen the same warning.
I have supposed the question obvious. The file c.vim will be automatically created by vim-plugin.
Seem to be an "inconsistent" implementation of the vim-plugin.
The files created by it are treated as all the files in the packages.
Say "without 'strict' work" will never be an acceptable solution.
We haven't been able to identify which package or eclass this file belongs to. If you find out, feel free to reopen this bug report.