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 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 this issue.
> 
> Sorry to have bothered you,
> 
> Nicholas
> 
> P.S. It seems to be an interaction either with having multiple version of
> childprocess or maybe just childprocess > 0.5.9.

ok, that helps. I realized that there is still something wrong with
rbnacl-libsodium, though. I can list it, but can't really use it.

~$ gem list rbnacl-libsodium

*** LOCAL GEMS ***

rbnacl-libsodium (1.0.16)
~$ ruby -e 'gem "rbnacl-libsodium"'
Traceback (most recent call last):
3: from -e:1:in `'
2: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:65:in `gem'
1: from /usr/lib/ruby/2.5.0/rubygems/dependency.rb:322:in `to_spec'
/usr/lib/ruby/2.5.0/rubygems/dependency.rb:310:in `to_specs': Could not find 
'rbnacl-libsodium' (>= 0) among 227 total gem(s) (Gem::MissingSpecError)
Checked in 
'GEM_PATH=/home/terceiro/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all',
 execute `gem env` for more information


signature.asc
Description: PGP signature

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 this issue.

Sorry to have bothered you,

Nicholas

P.S. It seems to be an interaction either with having multiple version of
childprocess or maybe just childprocess > 0.5.9.

On Wed, Apr 4, 2018 at 2:23 PM Antonio Terceiro  wrote:

> 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 complete.
> >
> > ```
> > $ vagrant status
> > Invalid gemspec in
> [/usr/share/rubygems-integration/all/specifications/rbnacl-
> > libsodium.gemspec]: stack level too deep
> > ```
> >
> > At one point I typed Ctrl+C quickly and got this (possibly related) stack
> > trace:
> >
> > ```
> > $ vagrant status
> > Invalid gemspec in
> [/usr/share/rubygems-integration/all/specifications/rbnacl-
> > libsodium.gemspec]: stack level too deep
> > [...]
> > ```
>
> I can't reproduce this on my system, nor in a clean system with only
> vagrant installed.
>
> > I have tried removing `ruby-rbnacl` (which removes `vagrant`) and
> reinstalling,
> > but the issue persists.
> > ```
> > $ sudo apt autoremove --purge ruby-rbnacl
> [...]
> > $ sudo apt install vagrant
> > $ vagrant status
> > Invalid gemspec in
> [/usr/share/rubygems-integration/all/specifications/rbnacl-
> > libsodium.gemspec]: stack level too deep
> > ^C
> > ```
> >
> > I do not beleive I have any gems installed (other than what comes from
> apt),
> > but here is the list just in case:
> >
> > ```
> > sudo gem list
> [...]
> > ```
>
> I need more than that. please share the output of:
>
> find /var/lib/gems
> gem list rbnacl-libsodium
> ruby -e 'gem "rbnacl-libsodium"'
>
> also, do you have vagrant plugins installed from outside of Debian?
>

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 complete.
> 
> ```
> $ vagrant status
> Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl-
> libsodium.gemspec]: stack level too deep
> ```
> 
> At one point I typed Ctrl+C quickly and got this (possibly related) stack
> trace:
> 
> ```
> $ vagrant status
> Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl-
> libsodium.gemspec]: stack level too deep
> [...]
> ```

I can't reproduce this on my system, nor in a clean system with only
vagrant installed.

> I have tried removing `ruby-rbnacl` (which removes `vagrant`) and 
> reinstalling,
> but the issue persists.
> ```
> $ sudo apt autoremove --purge ruby-rbnacl
[...]
> $ sudo apt install vagrant
> $ vagrant status
> Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl-
> libsodium.gemspec]: stack level too deep
> ^C
> ```
> 
> I do not beleive I have any gems installed (other than what comes from apt),
> but here is the list just in case:
> 
> ```
> sudo gem list
[...]
> ```

I need more than that. please share the output of:

find /var/lib/gems
gem list rbnacl-libsodium
ruby -e 'gem "rbnacl-libsodium"'

also, do you have vagrant plugins installed from outside of Debian?


signature.asc
Description: PGP signature

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-
libsodium.gemspec]: stack level too deep
```

At one point I typed Ctrl+C quickly and got this (possibly related) stack
trace:

```
$ vagrant status
Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl-
libsodium.gemspec]: stack level too deep
^CTraceback (most recent call last):
998: from /usr/bin/vagrant:23:in `'
997: from /usr/lib/ruby/2.5.0/rubygems.rb:309:in `activate_bin_path'
996: from /usr/lib/ruby/2.5.0/rubygems.rb:309:in `synchronize'
995: from /usr/lib/ruby/2.5.0/rubygems.rb:311:in `block in
activate_bin_path'
994: from /usr/lib/ruby/2.5.0/rubygems.rb:239:in `finish_resolve'
993: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:68:in
`require'
992: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1084:in
`find_active_stub_by_path'
991: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:850:in `stubs'
990: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:782:in
`installed_stubs'
989: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in
`map_stubs'
988: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in
`flat_map'
987: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in `each'
986: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:793:in `block
in map_stubs'
985: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:768:in
`gemspec_stubs_in'
984: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:768:in `select'
983: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:208:in
`valid?'
982: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:139:in
`data'
981: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:197:in
`to_spec'
980: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1194:in `load'
979: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1194:in `eval'
[ elided many copies of the same stack]
 34: from /usr/share/rubygems-integration/all/specifications/rbnacl-
libsodium.gemspec:2:in `load'
 33: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:68:in
`require'
 32: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1084:in
`find_active_stub_by_path'
 31: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:850:in `stubs'
 30: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:782:in
`installed_stubs'
 29: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in
`map_stubs'
 28: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in
`flat_map'
 27: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in `each'
 26: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:793:in `block
in map_stubs'
 25: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:768:in
`gemspec_stubs_in'
 24: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:768:in `select'
 23: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:208:in
`valid?'
 22: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:139:in
`data'
 21: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:197:in
`to_spec'
 20: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1194:in `load'
 19: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1194:in `eval'
 18: from /usr/share/rubygems-integration/all/specifications/rbnacl-
libsodium.gemspec:2:in `load'
 17: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:68:in
`require'
 16: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1084:in
`find_active_stub_by_path'
 15: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:850:in `stubs'
 14: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:782:in
`installed_stubs'
 13: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in
`map_stubs'
 12: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in
`flat_map'
 11: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in `each'
 10: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:793:in `block
in map_stubs'
  9: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:768:in
`gemspec_stubs_in'
  8: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:768:in `select'
  7: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:208:in
`valid?'
  6: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:118:in
`data'
  5: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:118:in
`open'
  4: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:129:in
`block in data'
  3: from