Bug#847068: vim-command-t: too strict dependency on libruby2.3

On Tue, 2016-12-06 at 00:14 +0100, Christian Hofstaedtler wrote: > * Sam Morris [161205 20:16]: > > Upstream introduced the strict ruby version check to reduce the number > > of crashes experienced by users. See the issue above for the details. > > The discussions upstream

Bug#847068: vim-command-t: too strict dependency on libruby2.3

* Sam Morris [161205 20:16]: > Upstream introduced the strict ruby version check to reduce the number > of crashes experienced by users. See the issue above for the details. The discussions upstream has linked are from dire times - 1.8 and 1.9, which indeed broke binary

Bug#847068: vim-command-t: too strict dependency on libruby2.3

forwarded 847068 https://github.com/wincent/command-t/issues/192 thanks On Mon, 2016-12-05 at 11:28 +0100, Christian Hofstaedtler wrote: > Package: vim-command-t > > Hi, > > your package vim-command-t has a libruby2.3 < 2.3.x.y dependency, > but there is little documentation on reasons for it.

Bug#847068: vim-command-t: too strict dependency on libruby2.3

Package: vim-command-t Hi, your package vim-command-t has a libruby2.3 < 2.3.x.y dependency, but there is little documentation on reasons for it. To the best of my knowledge, all other packages depending on librubyX.Y manage without a less-than versioning. Please drop this at your earliest