[DRE-maint] Bug#894754: vagrant: Invalid gemspec in rbnacl-libsodium stack level too deep

2018-04-05 Thread Antonio Terceiro
Control: reassign -1 ruby-rbnacl Control: retitle -1 ruby-rbnacl: doesn't really provide 'rbnacl-libsodium'? On Wed, Apr 04, 2018 at 11:13:57PM +, Nicholas Capo wrote: > I'm sorry. > It seems I did have additional gems installed. > > After removing all gems, and `ruby*` apt packages (and

[DRE-maint] Bug#894754: vagrant: Invalid gemspec in rbnacl-libsodium stack level too deep

2018-04-04 Thread Nicholas Capo
I'm sorry. It seems I did have additional gems installed. After removing all gems, and `ruby*` apt packages (and reinstalling vagrant), vagrant works again! When I then did `sudo gem install overcommit` which installed childprocess-0.9.0 as a dependency, vagrant broke again. Feel free to close

[DRE-maint] Bug#894754: vagrant: Invalid gemspec in rbnacl-libsodium stack level too deep

2018-04-04 Thread Antonio Terceiro
Control: tag -1 + moreinfo unreproducible On Tue, Apr 03, 2018 at 04:17:51PM -0500, Nicholas Capo wrote: > Package: vagrant > Version: 2.0.2+dfsg-3 > Severity: normal > > Dear Maintainer, > > When running any `vagrant` command the following is error appears and the > command seems to never

[DRE-maint] Bug#894754: vagrant: Invalid gemspec in rbnacl-libsodium stack level too deep

2018-04-03 Thread Nicholas Capo
Package: vagrant Version: 2.0.2+dfsg-3 Severity: normal Dear Maintainer, When running any `vagrant` command the following is error appears and the command seems to never complete. ``` $ vagrant status Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl-