Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 758209 - app-vim/vim-latex failed to emerge with Python 3.8
Summary: app-vim/vim-latex failed to emerge with Python 3.8
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Vim Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-03 10:27 UTC by Mike Limansky
Modified: 2020-12-03 11:15 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Limansky 2020-12-03 10:27:51 UTC
app-vim/vim-latex  failed to emerge after Python 3.8 became a default implementation. Moreover it blocked world update, so I had to unmerge it. It seems like python_single_target_python3_8 is missed for this package.

 The error I got is:

# emerge -pv vim-latex

These are the packages that would be merged, in order:

Calculating dependencies -

!!! Problem resolving dependencies for app-vim/vim-latex                                                                                                                                                                                                                        ... done!

!!! The ebuild selected to satisfy "vim-latex" has unmet requirements.
- app-vim/vim-latex-1.10.0-r2::x-portage USE="" ABI_X86="(64)" PYTHON_SINGLE_TARGET="-python3_6 -python3_7"

  The following REQUIRED_USE flag constraints are unsatisfied:
    exactly-one-of ( python_single_target_python3_6 python_single_target_python3_7 )
Comment 1 Sam James archtester gentoo-dev Security 2020-12-03 10:29:43 UTC
Unmerging is not the right fix (by the way: always depclean, not unmerge).

You need to set the target in package.use for now as a workaround until it’s added in the ebuild.
Comment 2 Sam James archtester gentoo-dev Security 2020-12-03 11:15:39 UTC
Hm. Wait.

The ebuild says:

>PYTHON_COMPAT=( python{3_6,3_7,3_8} )

What's going on here?