Opened 4 years ago
Last modified 11 months ago
#61361 closed defect
Getting Error: Failed to destroot vim: command execution failed when trying the Command sudo port install vim +python38 — at Version 1
Reported by: | ramukivars | Owned by: | raimue (Rainer Müller) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.3 |
Keywords: | Cc: | ||
Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Model: MacBook macOS Catalina 10.15.6
vim --version | grep python
It said "-python" and "-python3"
Hence installed Xcode and Macports.
Gave the Command sudo port install vim +python38
Getting Error:
Failed to destroot vim: command execution failed
Seen inside the Log File "/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_vim/vim/main.log"
failed to fetch vim-8.2.1719_0+huge+python38.darwin_19.x86_64.tbz2 from https://packages.macports.org/vim failed to fetch vim-8.2.1719_0+huge+python38.darwin_19.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/vim/vim failed to fetch vim-8.2.1719_0+huge+python38.darwin_19.x86_64.tbz2 from https://kmq.jp.packages.macports.org/vim
Went to the 3 Sites, there is no Package vim-8.2.1719_0+huge+python38.darwin_19.x86_64.tbz2.
Could see Files for only vim-8.1.1368_0+huge.darwin_19.x86_64.tbz2
Please give a Solution to install vim with python38 Support
Change History (1)
comment:1 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Milestone: | MacPorts Future |
Owner: | set to raimue |
Port: | vim added |
Status: | new → assigned |
Note: See
TracTickets for help on using
tickets.
That's correct. Packages are not necessarily always available, and that should never be a problem. In this case, it's because +python38 is not one of the default variants, and we only produce packages for default variants.
You should still be able to build the port from source. Presumably that is failing for you. Please attach the main.log file so that we can see why that happened.