Our alacritty package currently contains alacritty's terminfo files (alacritty and alacritty-direct). Ncurses, however, has started packaging these independently, causing a file collision. Discussion with the maintainer on FreeNode (UndeadLeech on ##rust) suggest that alacritty should forgo packaging the terminfo files, in favor of ncurses.
It's know, I've been waiting for this. I'll add a blocker with new ncurses. for now just disable terminfo useflag to get it co-installed. I'll remove this flag comepletely.
Yep, that was my workaround, thanks Georgy!
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b42186b911830798e9ca1ef864dc3cff1701142a commit b42186b911830798e9ca1ef864dc3cff1701142a Author: Georgy Yakovlev <gyakovlev@gentoo.org> AuthorDate: 2019-07-16 23:20:39 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2019-07-17 00:09:08 +0000 x11-terms/alacritty: drop old Bug: https://bugs.gentoo.org/690030 Package-Manager: Portage-2.3.69, Repoman-2.3.16 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> x11-terms/alacritty/Manifest | 122 --------- x11-terms/alacritty/alacritty-0.3.2.ebuild | 387 ----------------------------- x11-terms/alacritty/alacritty-0.3.3.ebuild | 354 -------------------------- x11-terms/alacritty/metadata.xml | 3 - 4 files changed, 866 deletions(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=578d83a61b76332c9db2701bda956d51a7f38826 commit 578d83a61b76332c9db2701bda956d51a7f38826 Author: Georgy Yakovlev <gyakovlev@gentoo.org> AuthorDate: 2019-07-16 23:18:51 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2019-07-17 00:09:02 +0000 x11-terms/alacritty: revbump 0.3.3, remove terminfo useflag ncurses now ships with alacritty terminfo Bug: https://bugs.gentoo.org/690030 Package-Manager: Portage-2.3.69, Repoman-2.3.16 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> x11-terms/alacritty/alacritty-0.3.3-r1.ebuild | 348 ++++++++++++++++++++++++++ 1 file changed, 348 insertions(+)
0.3.3-r1 is stable and does not have terminfo flag anymore. alacritty is smart and will just use xterm-256color if alacritty definition is not found. leaving this bug open for visibility if someone bumps into this until dust settles down.
Thanks for the quick fix Georgy!
