Package Details: deoplete-git r2057.4e91c4d-1

Git Clone URL: (read-only, click to copy)
Package Base: deoplete-git
Description: deoplete completion plugin for neovim
Upstream URL:
Licenses: MIT
Conflicts: deoplete
Provides: deoplete
Submitter: Trent
Maintainer: Trent
Last Packager: Trent
Votes: 0
Popularity: 0.000000
First Submitted: 2018-01-02 10:21 (UTC)
Last Updated: 2022-11-20 20:29 (UTC)

Required by (2)

Sources (1)

Latest Comments

Freso commented on 2021-04-26 07:58 (UTC)

Once again, please don’t push updates to the PKGBUILD just to bump $pkgver if no other changes are needed.

Freso commented on 2021-02-11 01:12 (UTC)

Hello again. Please, please don’t update the PKGBUILD just because there are a few new commits in upstream repository. It is unnecessarily spammy. This is what the pkgver() function in the PKGBUILD is for.

Freso commented on 2020-05-13 10:09 (UTC)

Hi. You don’t need to update the PKGBUILD with simple version bumps. The pkgver() will do that automatically for whomever builds it at the time of building.

Trent commented on 2020-03-13 01:30 (UTC) (edited on 2020-03-13 01:30 (UTC) by Trent)

update no longer requires python-msgpack>=1.0.0

Trent commented on 2020-02-20 00:09 (UTC)

dependency added for python-msgpack>=1.0.0, which as of Feb 19, is not available as an Arch Package, relevant github issues deoplete issue 1072 deoplete issue 1071

One solution is to switch from deoplete-git to deoplete.

It's also trivial to upgrade python-msgpack by building an Arch Package. You can see the current PKGBUILD. So then to build i.e. just the python3 version, you would edit the version number, edit the md5sum, and strip out the python2-specific build instructions and you would end up with a PKGBUILD like this. And then cd to the directory where you have your PKGBUILD and makepkg -si to build and install.