627032 – app-vim/vim-tmux-3.0.0 collides with app-misc/tmux-2.5-r1, breaking upgrade path

Bug 627032 - app-vim/vim-tmux-3.0.0 collides with app-misc/tmux-2.5-r1, breaking upgrade path

Summary: app-vim/vim-tmux-3.0.0 collides with app-misc/tmux-2.5-r1, breaking upgrade path

Status:	RESOLVED DUPLICATE of bug 603526

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Vim Maintainers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2017-08-04 06:55 UTC by Michał Górny
Modified:	2017-08-05 07:13 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michał Górny archtester

2017-08-04 06:55:12 UTC

* package app-vim/vim-tmux-3.0.0 NOT merged
 *
 * Detected file collision(s):
 *
 *      /usr/share/vim/vimfiles/ftdetect/tmux.vim
 *
 * Searching all installed packages for file collisions...
 *
 * Press Ctrl-C to Stop
 *
 * app-misc/tmux-2.5-r1:0::gentoo
 *      /usr/share/vim/vimfiles/ftdetect/tmux.vim

Comment 1 zlg (RETIRED) gentoo-dev

2017-08-04 07:45:15 UTC

commit cbb3db4674e91663aad123b5f4e6a1521c9da163 (HEAD -> master, origin/master, origin/HEAD)
Author: Daniel Campbell <zlg@gentoo.org>
Date:   Fri Aug 4 00:31:09 2017 -0700

    app-misc/tmux: block app-vim/vim-tmux in 2.5-r1
    
    Fixes file collision bug already fixed in 2.5-r2 (bug 603526)
    
    Bug: 627032
    Bug-URL: https://bugs.gentoo.org/627032
    
    See-Also: https://bugs.gentoo.org/603526
    Package-Manager: Portage-2.3.6, Repoman-2.3.3

Comment 2 Michał Górny archtester

2017-08-05 07:11:37 UTC

This is not fixed. -r2 is just a meaningless revbump without the blocker.

Comment 3 Michał Górny archtester

2017-08-05 07:13:24 UTC

Oh wait, the blocker doesn't belong here anyway. What kind of insanity are you guys doing there?! Let's move this back to the original misfix.

*** This bug has been marked as a duplicate of bug 603526 ***