Accepted neovim 0.2.1-3 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 12 Nov 2017 21:47:38 -0500
Source: neovim
Binary: neovim neovim-runtime
Architecture: source
Version: 0.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Vim Maintainers <pkg-vim-maintainers@lists.alioth.debian.org>
Changed-By: James McCoy <jamessan@debian.org>
Description:
neovim - heavily refactored vim fork
neovim-runtime - heavily refactored vim fork (runtime files)
Changes:
neovim (0.2.1-3) unstable; urgency=medium
.
* Add .nvimlog to debian/clean
* Switch back to Lua on mips64el, since there are sporadic test failures
with LuaJIT
* Set R³ to no
* Switch lua-nvim Build-Depends to an architecture blacklist, since it's
currently available everywhere other than powerpcspe and hurd-i386.
* Cherry-pick cf75de710, 0407ddb36, and b63cde97f from upstream to fix test
failures seen on the buildds
Checksums-Sha1:
7fbebdc1f7e72b49471cfb6bad03b1be32c42f45 2701 neovim_0.2.1-3.dsc
478d3aa5737c85321f9dbbd005879ad3c9242a3f 13368 neovim_0.2.1-3.debian.tar.xz
a0c98c78815b3eca962cb3e4d136267824a41ca5 8055 neovim_0.2.1-3_amd64.buildinfo
Checksums-Sha256:
68f50ed2a017f8067fc6f9c083de4ed8c1aa60ece0f2eb0cce47064a61d70950 2701 neovim_0.2.1-3.dsc
eb1dfcf0afe6ec74f99d48e1de0af7316637e9043a9b88e18dbdecf0add8bfda 13368 neovim_0.2.1-3.debian.tar.xz
66a9345f573f3024b045bc16f5263353c0a76254b14c65186334a0a6a8244f15 8055 neovim_0.2.1-3_amd64.buildinfo
Files:
13b9cb44ceceeaa9abbf6b0f236091d4 2701 editors optional neovim_0.2.1-3.dsc
70a6894596db2ac4fe7a00a1c44d4185 13368 editors optional neovim_0.2.1-3.debian.tar.xz
d407302ae2035616d41b18297863b442 8055 editors optional neovim_0.2.1-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAloJCbhfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx
QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIACgkQ3+aRrjMb
o9vwTg/9GDPR5f88exYcDUMsCHU8zKkSNSfFmZAUbOunJX49+UyuScB2AsJ4Ti+q
5uAVCGjS2HO31PHhZtzaDQMresBNpwIeVwbo97nVE5NGQVCn1CihDo6+j+4ewb4L
1ANDRQEtKn0QswRPeFP9fdN8NteZY7cNCYkXq6RhS4C8x68GsfZzNCYa0qSCFVYs
T90cpYf3BDgf8ASm0MSYe1dklXqtKu/8Z7O1vx3tRXOjkhr/iVlWR7OFcmcAQ7/n
4djVxfIaN9+ZMIMQi4IdTsq2uX9waBHgzHnXQvwcD5LEM2DMKoNztAnvvvcF/w7V
ydXOtg4vo1V4mOVKG7IZcOF1DOpFoBDxnjjEKNS4i0/f6I2UYPTgX+wbnBPExMfP
lbwBKI+lbmdpIChZRTUg64SwieJqaxy5KrCD9mE09EEif9RJonMEAJxm6DOcbOm+
s+fhQ0xqZ4U8eoDhsYgJaM8fyspVck+FCeP2ycNFXfBTJ+bb9Fa3UNwvf81L4nTO
SiPxDOY+g4qZw1Mq06rGe/erha1xFIDQTp1RjuWhyQdZbrsTY5UJQIuiXlQ9zlGH
c5mGIu1WR0GtbfdhYjITzjFsUPrbNmQ3Lui7Jw5+GaDOUMk4gjQGPMX4IUNPk8EY
OnOQ7M5pvjlOyFvYGZNO54RN5w6Z8Zcx6CSwaBGyuLfk6tfhMuQ=
=8J4T
-----END PGP SIGNATURE-----
Reply to: