Can't install bundle - endless error message - bundle

This is what I'm using: Windows 8. Cygwin32. Rvm version 1.25.27. Ruby version 2.1.2p95. Gem version 2.3.0. Drush version 5.9.
I'm totally new to all this so it's very possible that the explanation is something really simple.
I tried to use "drush omega-guard" from my drupal theme folder but got an error saying I had to install Bundler version 1.2 or newer. This is all fine since I hadn't installed bundle. But when I try to use the command "bundle install" I get this:
$ bundle install
-bash: bundle: kommandot finns inte
(Kommandot finns inte = Command not found.)
When I try using "gem bundler install" I get this:
$ gem bundler install
ERROR: While executing gem ... (Gem::CommandLineError)
Unknown command bundler
I also tried "gem bundle install":
$ gem bundle install
ERROR: While executing gem ... (Gem::CommandLineError)
Unknown command bundle
So I used "which bundle" and then used cd to get to that folder.
$ which bundle
I tried the same commands again, but from the other folder, and ended up with this:
I#I ~/.rvm/gems/ruby-2.1.2/bin
$ gem install bundler
ERROR: While executing gem ... (TypeError)
no implicit conversion of nil into String
I#I ~/.rvm/gems/ruby-2.1.2/bin
$ gem install bundle
ERROR: While executing gem ... (TypeError)
no implicit conversion of nil into String
I#I ~/.rvm/gems/ruby-2.1.2/bin
$ bundle install
/home/I/.rvm/rubies/ruby-2.1.2/lib/ruby/site_ruby/2.1.0/rubygems/dependency.rb:313:in `to_specs': Could not find 'bundler' (>= 0) among 13 total gem(s) (Gem::LoadError)
Checked in 'GEM_PATH=/home/I/.rvm/gems/ruby-2.1.2:/home/I/.rvm/gems/ruby-2.1.2#global', execute `gem env` for more information
from /home/I/.rvm/rubies/ruby-2.1.2/lib/ruby/site_ruby/2.1.0/rubygems/dependency.rb:322:in `to_spec'
from /home/I/.rvm/rubies/ruby-2.1.2/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_gem.rb:53:in `gem'
from /home/I/.rvm/gems/ruby-2.1.2/bin/bundle:22:in `<main>'
When I use command "gem list" bundle isn't listed:
$ gem list
*** LOCAL GEMS ***
bigdecimal (1.2.5, 1.2.4)
io-console (0.4.2)
json (1.8.1)
minitest (5.3.5, 4.7.5)
psych (2.0.5)
rake (10.3.2, 10.1.0)
rdoc (4.1.1, 4.1.0)
test-unit (2.5.5,
What am I missing or doing wrong? I have been following this tutorial and everything has worked fine up until this point:
EDIT: Since I asked this question I tried reinstalling ruby 2.1.2. The installation stuck on "#importing gemset" and after about 36 hours my computer was turned of due to a blackout. I therefore don't know if the reinstallation was completed or not. After that I also changed my gem version to 2.1.2 to match the ruby version. Theese things seemed to help and afterwards I could run both "gem install bundler" and "bundle install". My gemlist now looks like this:
$ gem list
*** LOCAL GEMS ***
addressable (2.3.6)
bigdecimal (1.2.5, 1.2.4)
breakpoint (2.0.7)
bundle (0.0.1)
bundler (1.6.3)
celluloid (0.15.2)
chunky_png (1.3.1)
coderay (1.1.0)
color-schemer (0.2.8)
compass (0.12.6)
compass-blend-modes (0.0.2)
compass-normalize (1.5)
compass-rgbapng (0.2.1)
compass-validator (3.0.1)
css_parser (1.3.5)
dash (0.4.0)
fssm (0.2.10)
io-console (0.4.2)
json (1.8.1)
minitest (5.3.5, 4.7.5)
psych (2.0.5)
rake (10.3.2, 10.1.0)
rdoc (4.1.1, 4.1.0)
sass (3.2.19)
test-unit (2.5.5,
timers (1.1.0)
But a new problem occur when I try running "drush omega-guard":
$ drush omega-guard
Which theme do you want to run Guard for?
[0] : Cancel
[1] : Ohm (Subtheme of Omega) - Omega based demonstration theme. Serves as a
best-practice reference for the Omega documentation. Ohm will be
constantly updated as best practice evolves so shouldn't be used in
[2] : Omega - A powerful HTML5 base theme framework utilizing tools like
Sass, Compass, Grunt, Bower, Ruby Version Manager, Bundler and more.
[3] : Design (Subtheme of Omega) - Please provide a description for
your theme.
There was a problem with your setup: [error]
Resolving dependencies...
Bundler can't satisfy your Gemfile's dependencies.
Install missing gems with `bundle install`.
So I try using the command "bundle install" again but end up with an endless error message:
$ bundle install
Fetching gem metadata from
Fetching additional metadata from
Resolving dependencies...
Using addressable 2.3.6
Using chunky_png 1.3.1
Using fssm 0.2.10
Using sass 3.2.19
Using compass 0.12.6
Using breakpoint 2.0.7
Using timers 1.1.0
Using celluloid 0.15.2
Using coderay 1.1.0
Using compass-blend-modes 0.0.2
Using color-schemer 0.2.8
Using compass-normalize 1.5
Using compass-rgbapng 0.2.1
Using compass-validator 3.0.1
Using css_parser 1.3.5
0 [main] ruby 15100 child_info_fork::abort: address space needed by '' (0x620000) is already occupied
0 [main] ruby 11364 child_info_fork::abort: address space needed by '' (0x620000) is already occupied
1 [main] ruby 14584 child_info_fork::abort: address space needed by '' (0x620000) is already occupied
The last three lines keep on repeating forever but with different numbers. So what is the problem this time?

Drush is a PHP app, not an Ruby one.
You need a PHP work environment (at first an PHP cli) to work with drush.


Puppet install gem fails but gem is installed anyways

I have a Puppet manifest that installs the Zurb Foundation gem:
class compass {
package { ["rubygems"]:
ensure => 'installed'
package { ['zurb-foundation']:
ensure => '3.0.6',
provider => 'gem',
require => Package['rubygems']
This causes the following error when running puppet apply:
err: /Stage[main]/Compass/Package[zurb-foundation]/ensure: change from absent to 3.0.6 failed: Could not update: Execution of '/usr/bin/gem install -v 3.0.6 --include-dependencies --no-rdoc --no-ri zurb-foundation' returned 1: INFO: `gem install -y` is now default and will be removed
INFO: use --ignore-dependencies to install only the gems you list
Building native extensions. This could take a while...
ERROR: Error installing zurb-foundation:
ERROR: Failed to build gem native extension.
/usr/bin/ruby1.9.1 extconf.rb
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from extconf.rb:4:in `<main>'
Gem files will remain installed in /var/lib/gems/1.9.1/gems/ffi-1.9.0 for inspection.
Results logged to /var/lib/gems/1.9.1/gems/ffi-1.9.0/ext/ffi_c/gem_make.out
at /etc/puppet/manifests/classes/compass.pp:25
However, doing a gem list yields the following results:
# gem list
*** LOCAL GEMS ***
chunky_png (1.2.8)
compass (0.12.2)
fssm (0.2.10)
rake (10.1.0)
rb-fsevent (0.9.3)
sass (3.2.0.alpha.277)
zurb-foundation (3.0.6)
The error causes puppet apply to not complete properly, since a lot of items are skipped because of failed dependencies. What can I do?
I think that the problem is that you don't have the ruby dev kit installed for you ruby (that's what's used to build native extensions).
You'll want to add something like (it may be different depending on your version of ruby):
package { 'ruby-dev':
ensure => installed,
before => Package['zurb-foundation'],
This should allow the gem to be built properly and let your puppet run finish too.

Build phoenix app from master

I am trying to create a new phoenix app using the current github phoenix master version.
I was trying to follow the Generating a Phoenix project from unreleased versions guide, but have been having difficulty.
This is what I have tried.
mix archive.uninstall phx_new
This command works as expected
git clone && cd phoenix
mix do deps.get, compile
I've tried with and without running this command
cd installer && mix dev_app --dev
Creates the expected mix.exs file as described in the guide
cd dev_app && mix deps.get
This last command can't resolve the dependencies successfully.
I've tried adding override: true to all of the deps.
I've tried running mix deps.update and mix deps.unlock
From both within my dev_app and phoenix clone
I can't seem to get around the following errors:
Failed to use "cowboy" (versions 1.0.0 to 1.1.2) because
/Users/samhouston/proj/phoenix/mix.exs requires ~> 2.1
mix.exs specifies ~> 1.0
** (Mix) Hex dependency resolution failed, change the version requirements of your dependencies or unlock them (by using mix deps.update or mix deps.unlock). If you are unable to resolve the conflicts you can try overriding with {:dependency, "~> 1.0", override: true}
When I change my mix.exs file to use :cowboy, "~> 2.1" and run mix deps.get I then get the error:
Failed to use "plug" (version 1.5.0-rc.0) because
/Users/samhouston/proj/phoenix/mix.exs requires ~> 1.5.0-rc.0
phoenix_ecto (versions 3.2.0 to 3.3.0) requires ~> 1.0 *
I have not been able to get past this dependency conflict

Build Atom Error: 'Cannot replace with lazy function because the supplied node does not belongto an assignment expression…'

Building atom from source did yield the following error, which has been reported before (see this), but as far as i can tell it has neither been resolved, nor been asked here: 'Cannot replace with lazy function because the supplied node does not belong to an assignment expression or a variable declaration!' [...]
How to recreate / explanation of issue:
git clone atom repository
open repository
(changed two lines of code according to this post on how to get transparent atom)
following official build guide
open atom repository
./script/bootstrap works
./script/build yields error: 'Cannot replace with lazy function because the supplied node does not belong to an assignment expression or a variable declaration!' [...]
Some remarks before there is the long full error: I'm using ubuntu 17.10. There can not be an issue with other packages in my opinion, as i wiped and reinstalled ubuntu to get this done (before had error in bootstrapping atom). Started with the nvm install nodejs, but now have gone through pretty much any nodejs version i could possibly find. Finally, i should probably just 'get good' and use vim anyway, which works in transparent terminal. Still want to know, what the issue might be. Full error:
Node: v9.3.0
Npm: v5.3.0
Installing script dependencies
Installing apm
apm 1.18.12
npm 3.10.10
node 6.9.5 x64
atom unknown
python 2.7.14
git 2.14.1
Installing modules ✓
Wrote Dependencies Fingerprint: /home/ljks/Documents/atom/node_modules/.dependencies-fingerprint e2bd05a8a4fc26a113cf6d4b5358994762853696
Cleaning /home/ljks/Documents/atom/out
Copying assets to /home/ljks/Documents/atom/out/app
Transpiling packages with custom transpiler configurations in /home/ljks/Documents/atom/out/app
transpiling for package github
Installing modules ✓
Transpiling Babel paths in /home/ljks/Documents/atom/out/app
Transpiling CoffeeScript paths in /home/ljks/Documents/atom/out/app
Transpiling CSON paths in /home/ljks/Documents/atom/out/app
Transpiling PEG.js paths in /home/ljks/Documents/atom/out/app
Generating module cache for /home/ljks/Documents/atom/out/app
Generating pre-built less cache in /home/ljks/Documents/atom/out/app/less-compile-cache
Generating metadata for /home/ljks/Documents/atom/out/app/package.json
Generating API docs at /home/ljks/Documents/atom/docs/output/atom-api.json
Dumping symbols in /home/ljks/Documents/atom/out/symbols
Running electron-packager on /home/ljks/Documents/atom/out/app with app name "atom"
Packaging app for platform linux x64 using electron v1.6.15
Changing permissions for node files in /home/ljks/Documents/atom/out/atom-1.25.0-dev-48dfffda6-amd64
Copying non-ASAR resources to /home/ljks/Documents/atom/out/atom-1.25.0-dev-48dfffda6-amd64/resources
Writing to /home/ljks/Documents/atom/out/atom-1.25.0-dev-48dfffda6-amd64/resources
Application bundle created at /home/ljks/Documents/atom/out/atom-1.25.0-dev-48dfffda6-amd64
Generating snapshot script at "/home/ljks/Documents/atom/out/startup.js" (6)Unable to transform source code for module /home/ljks/Documents/atom/out/app/node_modules/ls-archive/node_modules/decompress-zip/lib/decompress-zip.js.
Error: /home/ljks/Documents/atom/out/app/node_modules/ls-archive/node_modules/decompress-zip/lib/decompress-zip.js
Cannot replace with lazy function because the supplied node does not belong to an assignment expression or a variable declaration!
at FileRequireTransform.replaceAssignmentOrDeclarationWithLazyFunction (/home/ljks/Documents/atom/script/node_modules/electron-link/lib/file-require-transform.js:180:11)
at Context.visitIdentifier (/home/ljks/Documents/atom/script/node_modules/electron-link/lib/file-require-transform.js:72:18)
at Context.invokeVisitorMethod (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:344:49)
at Visitor.PVp.visitWithoutReset (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:196:32)
at visitChildren (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25)
at Visitor.PVp.visitWithoutReset (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20)
at visitChildren (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25)
at Visitor.PVp.visitWithoutReset (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20)
at visitChildren (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25)
at Visitor.PVp.visitWithoutReset (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20)
at NodePath.each (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path.js:101:26)
at visitChildren (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:219:18)
at Visitor.PVp.visitWithoutReset (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20)
at visitChildren (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25)
at Visitor.PVp.visitWithoutReset (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20)
at visitChildren (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25)
at Visitor.PVp.visitWithoutReset (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20)
at Visitor.PVp.visit (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:133:29)
at Object.visit (/home/ljks/Documents/atom/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:101:55)
at FileRequireTransform.replaceDeferredRequiresWithLazyFunctions (/home/ljks/Documents/atom/script/node_modules/electron-link/lib/file-require-transform.js:68:20)
at FileRequireTransform.apply (/home/ljks/Documents/atom/script/node_modules/electron-link/lib/file-require-transform.js:25:10)
at /home/ljks/Documents/atom/script/node_modules/electron-link/lib/generate-snapshot-script.js:53:56
at (<anonymous>:null:null)
at step (/home/ljks/Documents/atom/script/node_modules/electron-link/lib/generate-snapshot-script.js:3:191)
at /home/ljks/Documents/atom/script/node_modules/electron-link/lib/generate-snapshot-script.js:3:361
at <anonymous>:null:null

Runtime Error: Cannot find module “leaflet.awesome-markers” Ionic 3

I'm adding Font Awesome markers to an Ionic 3 application using Leaflet that can successfully display Leaflet's built-in markers, but when I attempt to import the leaflet.awesome-markers module, ionic serve reports a runtime error saying it cannot find the module leaflet.awesome-markers.
One suggestion I've followed is to remove the node_modules directory and let npm re-install everything. This didn't change the results.
Output of ionic info:
cli packages: (/home/jett/git/mobiLoc/node_modules)
#ionic/cli-plugin-cordova : 1.6.2
#ionic/cli-plugin-ionic-angular : 1.4.1
#ionic/cli-utils : 1.7.0
ionic (Ionic CLI) : 3.7.0
global packages:
Cordova CLI : 7.0.1
local packages:
#ionic/app-scripts : 1.3.7
Cordova Platforms : android 6.2.3 ios 4.4.0
Ionic Framework : ionic-angular 3.2.1
Android SDK Tools : 26.0.2
Node : v7.10.0
OS : Linux 4.4
npm : 4.2.0
From package.json:
"#types/leaflet": "^1.2.0",
"#types/leaflet.awesome-markers": "^2.0.4",
"leaflet": "^1.2.0",
"leaflet.awesome-markers": "^2.0.4",
"typescript": "2.3.4"
Relevant code:
import * as L from "leaflet";
import "leaflet.awesome-markers";
private issueIcon: L.AwesomeMarkers.Icon;
this.issueIcon = L.AwesomeMarkers.icon({
icon: 'heart-broken', /* Heart with a crack */
markerColor: 'red',
prefix: "fa"
I'm new to both 1) Type Script and 2) debugging imports of 3rd-party modules that rely on type definitions. However, this doesn't appear to be a problem with resolving types -- my IDE is able to recognize the types defined within the leaflet.awesome-markers file. No compile/transpile errors/warnings either.
Because there are no compile-time problems, this appears to rule out a permissions problem on that module, but I've checked that all node_modules are installed local to the project and have the same permissions throughout the directory.
Interested in other approaches to debugging this.
I don't fully understand how npm or my IDE is resolving imports, but I did stumble across a command that provided far more detail regarding the attempt to resolve the import. To get the extra detail, I used
npm run build
instead of
ionic serve
The npm run build command provided details of the various paths and extensions it was trying to use when resolving this line:
import "leaflet.awesome-markers";
I found the build was able to resolve this file once I changed the import statement to the location of the actual .js file:
import "leaflet.awesome-markers/dist/leaflet.awesome-markers";

django-autocomplete-light and get_widgets_dict

First I'd like to say that I think the autocomplete_light package is a nice, well maintained package but I am having some issues with it as a relative novice.
I upgraded my version of autocomplete_light using 'pip install django-autocomplete-light'.
As far as I was aware this shouldn't install v2 or the dev version of the project - reading from this link.
Checking the site-packages dir in my Virtual Env I've installed the following:
Is there an alternative to check the version? For example can I do something like this?
python shell
import autocomplete_light
print autocomplete_light.VERSION
(which doesn't work)
My main problem is that after the upgrade I'm seeing the following error message in my django project:
'module' object has no attribute 'get_widgets_dict'
My looks like this:
from django.db import models
from django import forms
from django.forms import ModelForm
import autocomplete_light
from vehicle_admin_ac3.models import mycar
class mycarForm(autocomplete_light.ModelForm):
year = forms.DateField(widget=forms.TextInput(attrs=
class Meta:
widgets = autocomplete_light.get_widgets_dict(mycar)
model = mycar
exclude = ['owner', 'uploaded']
I looked on the documentation which mentions why you should not use widget directly anymore but I didn't see a clear explanation how to fix my problem
I decided to download and install what I thought was the latest v2 test_project using the following commands:
rm -rf autocomplete_light_env/
virtualenv autocomplete_light_env
source autocomplete_light_env/bin/activate
pip install -e git+git://$AUTOCOMPLETE_LIGHT_VERSION#egg=autocomplete_light
cd autocomplete_light_env/src/autocomplete-light/test_project
pip install -r requirements.txt
./ runserver
The example at /non_admin/widget/add/ does what I want but when I check for this exmaple it uses the same approach that I used previously.
from django import forms
import autocomplete_light
from models import Widget
# in the case of this example, we could just have:
# WidgetForm = autocomplete_light.modelform_factory(Widget)
# but we'll not use this shortcut
class WidgetForm(forms.ModelForm):
class Meta:
widgets = autocomplete_light.get_widgets_dict(Widget)
model = Widget
I'm quite confused now where I need to go to fix my code or to get a simple example for what I want to do. I'd appreciate any information or guidance.
pip install django-autocomplete-light doesn't install v2
Just try on a fresh virtualenv and you'll see that pip doesn't install alphas (all released v2s are alphas) by default:
[env] 16/01 2014 01:37:11 jpic#etta /tmp
$ virtualenv foo
Using real prefix '/usr'
New python executable in foo/bin/python
Installing Setuptools..............................................................................................................................................................................................................................done.
Installing Pip.....................................................................................................................................................................................................................................................................................................................................done.
[env] 16/01 2014 01:37:17 jpic#etta /tmp
$ cd foo/
[foo] 16/01 2014 01:37:20 jpic#etta /tmp/foo
$ pip install django-autocomplete-light
Downloading/unpacking django-autocomplete-light
Downloading django-autocomplete-light-1.4.12.tar.gz (52kB): 52kB downloaded
Running egg_info for package django-autocomplete-light
warning: no files found matching '*.mo' under directory 'autocomplete_light'
Installing collected packages: django-autocomplete-light
Running install for django-autocomplete-light
warning: no files found matching '*.mo' under directory 'autocomplete_light'
Successfully installed django-autocomplete-light
Cleaning up...
[foo] 16/01 2014 01:37:36 jpic#etta /tmp/foo
$ pip install -U django-autocomplete-light
Requirement already up-to-date: django-autocomplete-light in ./lib/python2.7/site-packages
Cleaning up...
You can import autocomplete_light; print autocomplete_light.__path__ to check where python loads it from.
Upgrading to v2
get_widgets_dict was indeed removed from v2 because v2 has a better design which makes uses of form fields.
You're extending autocomplete_light.ModelForm, you don't need anything else. Now you could set Meta.autocomplete_excludes, Meta.autocomplete_fields, Meta.autocomplete_names if you wanted to override autocomplete_light.ModelForm's default behaviour.
FTR, upgrade docs are here:
You're picking examples from v1 and trying to apply them on v2 !
I can garantee that no example in the test_project of the v2 branch uses get_widgets_dict, it's been completely removed in favor of form fields which allow better validation flow and performance.
Your problem is already solved
I bet that you have solved your problem by yourself, removing the call to get_widgets_dict by now. Particularely since it's in bold in the README:
I'm sorry, I didn't think it would be so hard for users to follow... oh well I guess I'm still learning ;)